skill-improver

Audit and refactor SKILL.md files against an LLM-first style guide.

Updated May 24, 2026
One-click install
npx skills add https://github.com/etrigan16/v0-cipher-ar --skill skill-improver-etrigan16
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-improver
Source: https://github.com/etrigan16/v0-cipher-ar/tree/main/.opencode/skills/skill-improver
Command: npx skills add https://github.com/etrigan16/v0-cipher-ar --skill skill-improver-etrigan16

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Existing SKILL.md files often drift from the required structure: missing frontmatter, bloated bodies, prose-heavy branching, or tutorial-style content that wastes context tokens. This Skill audits and normalizes those files against a normative style guide without losing author intent. ## Core Features & Use Cases - Structured Auditing: Checks frontmatter completeness, trigger clarity, section order, body token budget, decision gates, and output contracts for each skill. - Safe Refactoring: Defaults to audit-only mode and only edits files when explicitly asked, moving long explanations into local references/ or assets/ instead of deleting content. - Registry Awareness: Uses .atl/skill-registry.md to locate skills and recommends a registry refresh when metadata or paths change. - Use Case: After adding several custom skills to a repository, run an audit to find skills with invalid frontmatter or oversized bodies, then apply fixes that convert prose branching into decision tables. ## Quick Start Audit all skills in this repository against the skill style guide and report issues grouped by severity.

Frequently Asked Questions about skill-improver

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

FAQPage Schema
How do I audit existing SKILL.md files for quality?▼

Invoke the skill-improver skill, which reads the style guide, locates skills via .atl/skill-registry.md or by scanning for SKILL.md files, and returns a report grouped by skill with severity levels and exact proposed changes.

What structure should a SKILL.md file follow?▼

A SKILL.md should contain frontmatter with name, description, license, and metadata, followed by Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract, and References sections in that order.

Does skill-improver modify files automatically?▼

No. It defaults to audit-only mode and only edits files when the user explicitly requests apply mode. Even then it preserves meaningful content by moving long explanations into references/ or assets/ rather than deleting them.

What is the token budget for a SKILL.md body?▼

The style guide targets 180-450 tokens for the body, with a recommended maximum of 700 tokens and a hard maximum of 1000 tokens. Overflow content such as examples and schemas should move to references/ or assets/.

When should I use skill-creator instead of skill-improver?▼

Use skill-creator when building a brand-new skill from a reusable pattern. Use skill-improver only when auditing, refactoring, normalizing, or upgrading existing SKILL.md files.