skill-lifecycle-promotion
Use when adding or auditing Agentlas skill lifecycle metadata, skill-registry.json, trial evidence, Curator promotion decisions, or first-class skill promotion gates.
npx skills add agentlas-ai/Agentlas-OS --skill skill-lifecycle-promotion --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Skill Lifecycle Promotion Use this skill when a generated or packaged Agentlas repo needs governed skill promotion metadata. ## Procedure 1. Add `.agentlas/skill-registry.json` as an export-only candidate registry. 2. Add empty `.agentlas/skill-trials.jsonl` and `.agentlas/curator-decisions.jsonl`. 3. Keep every skill at `tier: candidate` on export. 4. Keep `runtimeFirstClassRecallEnabled: false` unless a local Curator later approves promotion. 5. Add success predicates and situation tags for every skill. 6. Separate `## Memory Events` from `## Skill Trial Events`. 7. Treat LLM rubric review as weak evidence only. 8. Block promotion when authority separation, sealed holdouts, replayability, or rollback evidence is missing. 9. Include false-accept, blind-spot, and drift terms in any durable-error budget. ## Output Return: - registry files added or checked; - promotion tier status; - evidence gaps; - rollback/quarantine status; - residual risks.
- Procedure
- Output
What does the skill-lifecycle-promotion skill do?
Use when adding or auditing Agentlas skill lifecycle metadata, skill-registry.json, trial evidence, Curator promotion decisions, or first-class skill promotion gates.
How do I install it?
Run `npx skills add agentlas-ai/Agentlas-OS --skill skill-lifecycle-promotion --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agentlas-ai/Agentlas-OS, a repository with 1,165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.