Export Skill

Overview

Checks a completed skill against the agentskills.io export gate, writes its context snippet and updates the managed section in CLAUDE.md, AGENTS.md or .cursorrules. It is the sole publishing gate: create-skill and update-skill produce drafts, and only export writes the context files and records the skill in .export-manifest.json.

Conventions

• Bare paths (e.g. references/<name>.md) resolve from the skill root.
• Module-level path exception: bare paths beginning with knowledge/ or shared/ resolve from the SKF module root ({project-root}/_bmad/skf/ installed, src/ in dev), not the skill root; for example knowledge/version-paths.md and shared/health-check.md.
• Sibling skills: a path that names another SKF skill's folder (skf-<name>/...) resolves from the SKF module root, and that skill must be installed with this one.
• references/ holds the workflow stages, chained by frontmatter nextStepFile; the files a stage loads when it needs them (load-skill.md loads multi-skill-mode.md and preflight-snippet-root-probe.md, update-context.md loads orphan-context-detection.md, orphan-row-detection.md and manifest-rebuild.md); and the headless contract (invocation-contract.md, result-envelope.md). assets/ holds the snippet and managed-section templates.
• {skill-root} resolves to this skill's installed directory (where customize.toml lives, if present).
• {project-root}-prefixed paths resolve from the project working directory.
• {skill-name} resolves to the skill directory's basename.
• Cross-skill data coupling: export-skill, drop-skill and rename-skill write the managed section only through shared/scripts/skf-rebuild-managed-sections.py, in the format assets/managed-section-format.md documents, and change .export-manifest.json only through shared/scripts/skf-manifest-ops.py (v2 schema in references/manifest-rebuild.md). A change to either contract changes all three skills.

Role