optimize-description

To improve SKILL.md discoverability, rewrite the frontmatter description to include action-led triggers, explicit input/output contracts, and scope boundaries. This ensures agents can accurately identify and invoke the skill based on user intent.

A good skill description for trigger clarity uses an action-led format, states specific inputs and outputs, and includes disambiguation when similar skills exist. It scores well on trigger clarity, scope boundaries, and readability criteria.

Optimize YAML frontmatter by analyzing the existing description's trigger clarity and input/output contracts, then rewriting it into a concise, action-led format. Include example triggers and disambiguation to maximize agent discoverability and invocation accuracy.

Yes, you can analyze an existing SKILL.md to extract the current description, triggers, and I/O requirements. The tool scores the description on trigger clarity, disambiguation, input/output, scope boundaries, and readability before generating an optimized version.

Yes, this process specifically targets SKILL.md files with vague or missing triggers. It analyzes existing documentation to produce a precise, reusable frontmatter description that defines explicit triggers and input/output contracts for better agent matching.

Rewrite a skill description to include disambiguation when similar skills exist in the same category. This prevents agent misfires by explicitly stating scope boundaries and differentiating the input/output contracts from overlapping tools.