enhance-skill
Enhance Skill
Review an existing skill and apply improvements in one pass — structure, description, and content quality.
Quick start
/enhance-skill path/to/skill-name/ — enhance a skill by path
/enhance-skill skill-name — enhance an installed skill by name
Workflow
1. Locate and read the skill
Find the skill folder and read all files (SKILL.md and any supporting files).
2. Review against guidelines
Evaluate every criterion from the write-a-skill checklist:
Description
- Present and under 1024 chars
- Written in third person
- First sentence states what it does
- Includes "Use when [specific triggers]"
- Triggers specific enough to distinguish from similar skills
SKILL.md structure
- Valid frontmatter (
name,description) - Under 100 lines
- No time-sensitive information
- Consistent terminology throughout
- Concrete examples included
- References one level deep
File structure
- Content split into separate files when SKILL.md > 100 lines
- Scripts only for deterministic, repeated operations
- No unnecessary files
Content quality
- Instructions are clear and unambiguous
- Steps are actionable, not vague
- No redundant or duplicated guidance
- Appropriate level of detail — not too terse, not over-explained
- Examples reflect real use cases
3. Propose improvements
Present a concise summary of all proposed changes grouped by category:
- Must fix — structural or description failures that affect reliability
- Should fix — warnings and content clarity issues
- Optional — style or minor readability improvements
For each item, show a brief before/after or description of the change.
Ask the user: "Would you like a full review report before applying changes?"
- If yes — produce the report using the format in REPORT.md, then ask for approval to proceed.
- If no — ask for approval to apply changes directly.
4. Apply changes
With user approval, rewrite the affected files in place. Do not change anything not listed in the proposal.
5. Confirm
Show a diff summary of what changed. Re-run the checklist and confirm all previously failing criteria now pass.
More from kenlck/skills
bug-fix
Structured bug fixing with reproduction, root cause analysis, fix design, regression risk analysis, and quality review. Only invoke this skill when the user explicitly asks to use it by name (e.g. "use bug-fix", "run bug-fix") or clearly requests a structured/systematic bug fixing process. Do not invoke for general bug reports, error messages, or broken behavior — handle those directly without this skill.
19feature-dev
Optimized guided feature development with deep requirement drilling, codebase understanding, and design-quality frontend implementation. Use this skill whenever the user wants to build or implement a feature — whether they say "let's build X", "add feature Y", "implement Z", "I want to create", "can we add", or any variation. This is the go-to skill for any non-trivial software feature work. Prefer this over a plain coding response whenever the feature has more than one moving part.
18code-review
Review changed code for bugs, simplicity, security, and convention adherence using parallel reviewer agents. Use when the user asks to review code, review a PR, check quality, or wants a second pair of eyes before merging.
18grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
17simplify
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
17frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
15