update-skill

Update SKILL.md frontmatter and workflow while preserving tool constraints.

2|1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/enbiyagoral/.claude --skill update-skill-enbiyagoral
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-skill
Source: https://github.com/enbiyagoral/.claude/tree/main/.claude/skills/update-skill
Command: npx skills add https://github.com/enbiyagoral/.claude --skill update-skill-enbiyagoral

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you safely update an existing skill's SKILL.md content or its frontmatter, ensuring consistency across the skill's metadata and workflow.

Core Features & Use Cases

  • Update frontmatter fields (name, description, argument-hint, triggers, allowed-tools) to reflect new requirements.
  • Update the workflow steps inside SKILL.md to align with new instructions.
  • Validate frontmatter YAML and ensure the workflow references only allowed-tools.

Quick Start

Update the target skill by running the update-skill tool and specifying the skill name, then follow the prompts to modify frontmatter or workflow.

Frequently Asked Questions about update-skill

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

FAQPage Schema
How do I update SKILL.md frontmatter and workflow without breaking YAML validation?

You can update frontmatter and workflow content by parsing and validating the YAML metadata, modifying the file in place, and ensuring all workflow references align with the allowed-tools constraints defined in the skill library.

What is the best way to manage and fix metadata consistency across a library of Claude skills?

Fixing metadata consistency across a skill library requires parsing YAML frontmatter to correct naming, descriptions, and triggers, then modifying the SKILL.md files in place to ensure all tooling requirements align across the directory.

Can I modify allowed-tools and triggers in an existing SKILL.md file?

Yes, you can update frontmatter fields like allowed-tools and triggers by modifying the SKILL.md file in place, provided you validate the YAML structure and preserve existing disable-model-invocation constraints during the process.

Why does updating a skill workflow require validating allowed-tools constraints?

Updating a skill workflow requires validating allowed-tools constraints to ensure the modified SKILL.md instructions reference only permitted tooling, preventing execution errors and maintaining operational boundaries within the skill library.

How do I edit SKILL.md files in place while preserving disable-model-invocation settings?

Editing SKILL.md files in place while preserving disable-model-invocation settings requires parsing the YAML frontmatter, applying updates, and explicitly carrying over existing invocation constraints during the modification process.