/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 -y skills add agentlas-ai/Agentlas-OS --skill skill-lifecycle-promotion --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/skill-lifecycle-promotion
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when adding or auditing Agentlas skill lifecycle metadata, skill-registry.json, trial evidence, Curator promotion decisions, or first-class skill promotion gates.
SKILL.md
skill-lifecycle-promotion.SKILL.mdname: skill-lifecycle-promotion description: "Use when adding or auditing Agentlas skill lifecycle metadata, skill-registry.json, trial evidence, Curator promotion decisions, or first-class skill promotion gates."
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.
Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.
Other skills on agentlas-os.
- /agentlas-core-engine-meta-agent
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.
Open skill - /hephaestus-build
Use when the user types /prompts:hep-build, mentions @Hephaestus for build work, asks to create a single Agentlas agent, create a multi-agent team, or package an existing local/external agent into Agentlas architecture.
Open skill - /hephaestus-cloud
Use when the user types /hep-cloud or asks to staff from THEIR OWN Agentlas cloud packages only. Cloud is one exact source scope; Network means Local + owner Cloud + public Hub.
Open skill - /hephaestus-network
Use when the user types $hephaestus-network or /hep-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM staffs each turn; the exact roster remains goal-bound until
Open skill - /hephaestus-storm
Use when the user types /hep-storm, says @Hephaestus storm <goal>, or asks to drive a goal to verified completion through a force-robust Stormbreaker loop. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs each
Open skill - /hephaestus-upload
Use when the user types $hephaestus-upload or /hep-upload, or asks to upload, publish, or list an Agentlas agent or team. Ask Cloud (private) vs Agentlas Hub (public) FIRST, then publish through the bundled Hephaestus gate.
Open skill