SkillForge

Delete a skill permanently. Auto-backs up before deletion.

This is a destructive operation — the skill will be removed from the active library. A backup is always created so it can be restored later if needed.

Args: name: Skill identifier to delete. confirm: Must be True to actually delete. This two-step confirmation prevents accidental deletions.

View the optimization history for a skill.

Use this to understand how a skill has evolved over time and what feedback drove each change. Helpful before making further edits to avoid reverting previous improvements.

Args: skill_name: The skill to check.

Read the full content of a skill.

Call this to load a skill's complete instructions before executing a task in that skill's domain. The returned body contains actionable guidelines — treat them as project-level requirements, not suggestions.

Args: name: The skill identifier (directory name).

Get the Skill Writing & Optimization Guide.

Call this BEFORE creating or modifying any skill. It covers: file format, writing principles, description optimization, and iterative improvement.

WHY: Skills that ignore the guide tend to be either too rigid (walls of MUST/NEVER) or too vague (no actionable instructions). The guide teaches how to write skills that actually help.

List all backups for a skill, newest first.

Use this to inspect version history before restoring or to verify that a backup was created after a save/delete operation.

Args: name: The skill identifier.

🔴 MANDATORY FIRST CALL — Call this before starting ANY task.

Returns all available skills with name and description. Review each description — if relevant to your current task, call get_skill to load full instructions.

WHY: Skills encode hard-won conventions and user preferences. Skipping this step means you will miss domain-specific guidance and repeat mistakes that have already been corrected.

Prepare and return a structured optimization plan for a skill.

Call this when user feedback indicates a skill needs improvement or a new skill should be created. Returns a step-by-step plan that you can follow directly — no sub-agent required.

Recommended workflow:

1. Call triage_skill_request first to check for existing skills

2. Call this tool to get the optimization plan

3. Call get_skill_guide to understand writing best practices

4. Draft the skill content following the plan and guide

5. Call save_skill — it will validate and reject if quality is insufficient

Trigger signals to watch for:

• User corrects your approach → existing skill may need updating

• User states a preference ('always X', 'never Y') → skill candidate

• Repeated pattern across conversation → new skill candidate

• User explicitly mentions skills → act immediately

Args: skill_name: Which skill to optimize (or create if it doesn't exist). feedback: The user feedback that triggered this optimization. context: Optional additional context about what went wrong or what the user expects.

Restore a skill from a specific backup. Current version is backed up first.

Use this when a skill optimization went wrong and you need to roll back. The current version is always saved before overwriting, so no data is lost.

Args: name: The skill identifier. timestamp: Backup timestamp (from list_backups output).

Create or update a skill. Validates before saving, auto-backs up before overwrite.

This tool enforces quality gates — if the skill fails validation, it will be REJECTED with specific error messages explaining what to fix. Fix the issues and call save_skill again.

Validation checks:

• Description must be >= 50 chars and explain WHAT + WHEN

• Body must be 3-500 lines of actionable instructions

• Description should include trigger conditions

• Body should avoid overly rigid language (explain WHY instead)

Args: name: Skill identifier (lowercase, hyphens, max 64 chars). description: What the skill does and when to trigger (>= 50 chars). Front-load the key use case. Include trigger conditions like 'Use this skill when...' or 'Activate whenever...'. body: Markdown body (3-500 lines). Follow the skill writing guide. extra_frontmatter: Optional JSON of additional frontmatter fields.

Analyze intent against existing skills to decide the best action.

Call this BEFORE creating or optimizing a skill. It returns all existing skills with their descriptions so you can determine:

• REUSE: An existing skill already covers this need (match >= 80%). → Just call get_skill to load it.

• IMPROVE: An existing skill partially covers this (match 50-79%). → Call request_skill_optimization with the existing skill name.

• CREATE: No existing skill is relevant (match < 50%). → Call request_skill_optimization with a new skill name.

You (the LLM) make the routing decision — this tool provides the information you need to decide.

Args: intent: What the user wants or the feedback that triggered this. Be specific — include the domain, task type, and context.