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.
git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS /tmp/skill-lifecycle-promotion && cp -r /tmp/skill-lifecycle-promotion/.agents/skills/skill-lifecycle-promotion ~/.claude/skills/skill-lifecycle-promotionSKILL.md
# 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.
Use when designing a new multi-agent team, visible agents folder, role boundaries, handoff flow, PM Soul, Memory Curator, Policy Gate, or evaluation role. Use for agent-team repo creation even when the user only says they want a meta-agent or agent operating system.
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
Use the Agentlas browser hardpoint for browser-required work.
Use when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.
Prepare explicitly named Agentlas Hub or Cloud agents.
Use when the user types /agentlas-cloud, /agentlas cloud, or /hep-cloud to staff only from the signed-in owner's private Cloud packages.
Connect Agentlas agents or teams to Telegram.
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.