skill-management

To create a custom managed skill, scaffold it under {workspaceDir}/skills with a skill id, name, description, emoji, and markdown body. The skill becomes immediately available for skill_load and can optionally register in the SKILLS.md index.

Skill scaffolding optionally adds the new managed skill to the SKILLS.md index during creation. This maintains workspace configuration integrity while ensuring the skill is discoverable and available for immediate use.

The best way to delete a managed skill is using a removal workflow that unregisters it from the SKILLS.md index and deletes it from {workspaceDir}/skills. This safe execution uses temporary-file testing and explicit user-consented persistence.

Yes, you can formalize an internal prompt template into a managed skill by scaffolding it with YAML frontmatter and a markdown body. This enables consistent team use and clean retirement when requirements change.

Yes, skill management requires explicit user-consented persistence before writing or deleting files. Safe execution is enforced via temporary-file testing and host-executed tool runners for deterministic lifecycle operations.

You need to update the SKILLS.md index when scaffolding new managed skills or removing existing ones. This optional inclusion during creation and deletion ensures workspace configuration stays synchronized without risking unintended persistence.