SKILL.md Optimizer

Problem

Many SKILL.md files read like project notes rather than Agent instructions: the YAML description lacks WHAT, WHEN, and trigger words; sections mix installation, FAQs, and background explanations; terms and path styles drift; long files dilute the rules an Agent needs to follow. This makes matching less stable and maintenance harder.

How it works

The skill optimizes the document against a standard format:

• YAML repair: rewrite in third person, add WHAT + WHEN, append trigger words, and keep the field under 1024 characters.
• Structure cleanup: require a concise intro and a feature table at the start, add an auth section if missing, and remove empty or user-facing sections.
• Reduction: delete repeated explanations, basic tutorials, and excess examples while preserving executable rules.
• Consistency: unify terms, code-block languages, forward-slash paths, and table style; move oversized details into references/ when needed.

Boundaries

It edits only SKILL.md and does not change README.md, scripts, or referenced files. The goal is to improve expression and structure, not alter behavior. If auth details or references are absent, it should not invent them; a human should verify after optimization.