skill-management

Create and delete custom managed skills with YAML frontmatter and Markdown bodies.

1.0k|158|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/vellum-ai/vellum-assistant --skill skill-management-vellum-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-management
Source: https://github.com/vellum-ai/vellum-assistant/tree/main/assistant/src/config/bundled-skills/skill-management
Command: npx skills add https://github.com/vellum-ai/vellum-assistant --skill skill-management-vellum-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing the lifecycle of custom managed skills across teams is error-prone without a centralized process and tooling.

Core Features & Use Cases

  • Scaffold a new managed skill with YAML frontmatter and markdown body
  • Delete an existing managed skill and remove it from the SKILLS.md index
  • Skills created via scaffold_managed_skill become available for skill_load immediately

Quick Start

Scaffold a new managed skill using scaffold_managed_skill and then delete unused ones with delete_managed_skill.

Frequently Asked Questions about skill-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new custom skill with YAML frontmatter and markdown?

Scaffold a custom skill by using scaffold_managed_skill to create a SKILL.md file with YAML frontmatter and a markdown body in your workspace skills directory. The new skill becomes available for skill_load immediately after persistence.

What is the best way to manage the lifecycle of custom developer skills?

Managing custom developer skill lifecycles involves using centralized tooling to scaffold new skills with YAML frontmatter and delete unused ones, automatically updating the SKILLS.md index to ensure accuracy across development teams.

How do I delete an existing managed skill and update the index?

Delete a managed skill by invoking delete_managed_skill, which removes the specific skill directory from your workspace and automatically updates the SKILLS.md index to keep your skill registry synchronized and clean.

Do I need a specific directory structure to manage custom skills?

Managing custom skills requires a {workspaceDir}/skills directory to persist skill files and a SKILLS.md index file to track them. This structure ensures scaffolded skills are immediately available for loading during workflows.

When should I not use automated skill scaffolding for my workflow?

Avoid automated skill scaffolding if your custom workflow does not use YAML frontmatter configurations or requires managing skills outside the {workspaceDir}/skills directory, as these explicit formats and safeguards are required for proper persistence and availability.