skill-lifecycle-promotion

$npx mdskill add agentlas-ai/Agentlas-OS/skill-lifecycle-promotion

Governs skill promotion metadata and lifecycle gates for Agentlas repos.

  • Adds or audits skill-registry.json and trial evidence files.
  • Depends on .agentlas directory, JSONL files, and Curator decisions.
  • Blocks promotion when authority separation or rollback evidence is missing.
  • Returns registry status, tier, evidence gaps, and residual risks.

SKILL.md

.github/skills/skill-lifecycle-promotionView on GitHub ↗
---
name: 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.

More from agentlas-ai/Agentlas-OS

SkillDescription
agent-team-designUse 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.
agentlas-auto-activationUse when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
agentlas-core-engine-meta-agentUse 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.
agentlas-packagingUse when converting, repairing, or packaging an existing local or external agent/team into Agentlas architecture for local install, Agentlas import, Codex plugin use, Claude adapter use, or open-source release.
agentlas-security-scanUse when an agent folder must pass the Agentlas Cloud 2-stage security scan (static rules + BYOK LLM judgment) before private sync or public publish, or when asked to run/interpret `hephaestus security scan`.
clarify-question-loopUse when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt without one to five targeted questions.
hephaestus-buildUse 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.
hephaestus-cloudUse 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.
hephaestus-networkUse when the user types /hep-network, mentions @Hephaestus, or asks Agentlas to staff a task from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM is the temporary orchestrator.
hephaestus-stormUse 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 work packet as a verifier-first hardened loop that does not stall, run away, or claim false success. Use it for loop-worthy work — apps, sites, agents, automations, debugging, multi-step research, data/report generation. Trivial questions are answered directly, not stormed.