improve-skill

Inspects a skill directory and applies targeted improvements to its SKILL.md content.

11|1|Updated Jul 25, 2025

Search Tags:#workflow automation #agent skills #skill audit #skill maintenance #frontmatter validation #cli optimization

Ready to run

npx skills add https://github.com/tomzx/agents --skill improve-skill-tomzx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: improve-skill
Source: https://github.com/tomzx/agents/tree/main/skills/improve-skill
Command: npx skills add https://github.com/tomzx/agents --skill improve-skill-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Skill libraries degrade over time as commands become outdated, descriptions drift from behavior, and small errors accumulate. Manually auditing each skill is slow and inconsistent, so this Skill automates the review and surgical improvement of a single skill in place. ## Core Features & Use Cases - End-to-end skill audit: Reads every file in a target skill directory, checks frontmatter validity, cross-references, CLI calls, and repo conventions. - CLI optimization: Detects inefficient command usage such as per-item loops that can collapse into bulk calls, or `gh` reads that should use the repo-preferred `ghx` cache. - Guarded editing: Applies only high-value, low-risk changes confined strictly to the target skill directory, with a git diff verification step. - Use Case: A daily Skill Refresher workflow picks a random skill and invokes `/improve-skill review-tests`, which adds a missing acceptance-checks section and fixes a broken script reference. ## Quick Start Run /improve-skill followed by a skill name such as git-commit to audit and improve that skill in place.

Frequently Asked Questions about improve-skill

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

FAQPage Schema

How do I improve a skill in an Agent Skills library?▼

Invoke /improve-skill with the target skill name, for example /improve-skill git-commit. It reads every file in the skill directory, reasons about high-value low-risk improvements, and applies them in place following repo conventions.

What kinds of changes does a skill audit apply?▼

It fixes correctness issues like broken commands and wrong paths, improves clarity and completeness, optimizes CLI calls, and repairs frontmatter or cross-references. It avoids churn such as rewrites of working prose or speculative edge cases.

Can improve-skill edit files outside the target skill directory?▼

No. A hard constraint restricts modifications to files inside skills/<skill-name>/ only. A verification step runs git diff to confirm no change escaped the directory and reverts any that did.

How does the skill optimize CLI calls during an audit?▼

It collects every CLI invocation and checks whether the same result is reachable more cheaply, such as using the repo-preferred ghx over gh, a --json flag instead of piping through jq, or a bulk command instead of a per-item loop.

What happens if a skill needs no changes?▼

If the audit finds the skill already clear, correct, and complete, it reports that no changes are needed and exits without editing anything, avoiding unnecessary diff noise.