optimizing-descriptions

Audit and rewrite SKILL.md descriptions to improve trigger accuracy.

320|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/mizchi/skills --skill optimizing-descriptions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: optimizing-descriptions
Source: https://github.com/mizchi/skills/tree/main/meta/optimizing-descriptions
Command: npx skills add https://github.com/mizchi/skills --skill optimizing-descriptions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits and rewrites SKILL.md descriptions to improve trigger accuracy and discovery.

Core Features & Use Cases

  • Classifies skills into Meta or Project according to the two-track policy and ensures descriptions align with trigger strategy.
  • Performs batch audits of frontmatter (name, description) and enforces concise, user-focused language.
  • Patches description lines in a separate, review-friendly batch and propagates changes for consistency.
  • Supports optional propagation to mirror locations and future audits with tooling like waxa.

Quick Start

Run a batch audit on all skills and apply the optimized description changes in a single commit.

Frequently Asked Questions about optimizing-descriptions

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

FAQPage Schema
How do I audit and rewrite markdown frontmatter descriptions for skill discovery?

To audit and rewrite markdown frontmatter descriptions for skill discovery, you batch process SKILL.md files to enforce concise, user-focused language and explicit invocation triggers. This ensures descriptions align with the two-track Meta and Project classification policy.

What is the character limit for a skill description in frontmatter?

The character limit for a skill description in frontmatter is 1024 characters. Enforcing this limit during batch audits ensures trigger accuracy and keeps descriptions concise for better discovery across the repository.

How do I classify skills into Meta and Project tracks for trigger strategy?

Classifying skills into Meta and Project tracks involves evaluating each SKILL.md against the two-track policy to align descriptions with the appropriate trigger strategy. This batch audit process ensures correct categorization before applying any description tuning.

Can I batch audit all SKILL.md files and apply description changes in a single commit?

Yes, you can batch audit all SKILL.md files and apply optimized description changes in a single commit. The process patches description lines in a separate, review-friendly batch and optionally propagates changes to mirror locations for consistency.

Why does my skill description have low trigger accuracy and poor discovery?

Low trigger accuracy and poor discovery often result from missing concise frontmatter fields or vague invocation language. Auditing and rewriting descriptions to enforce explicit triggers and user-focused language resolves this by improving how accurately the skill is matched.

Do I need explicit invocation language in my skill description frontmatter?

Yes, you need explicit invocation language in your skill description frontmatter. The batch audit process enforces adding concise names and descriptions with explicit invocation triggers to ensure accurate discovery and proper activation of your skills.