Analyze and optimize skill frontmatter for reliable automatic invocation. Use this skill when: (1) improving an existing skill's description for better triggering, (2) diagnosing why a skill isn't being invoked, (3) rewriting frontmatter to match production patterns, (4) validating description quality against best practices, or any task involving skill metadata optimization (examples: \"optimize frontmatter\", \"fix skill triggering\", \"improve skill description\", \"why isn't my skill invoked…
Analyze and optimize skill frontmatter for reliable automatic invocation.
Use this skill when: (1) improving an existing skill's description for better triggering, (2) diagnosing why a skill isn't being invoked, (3) rewriting frontmatter to match production patterns, (4) validating description quality against best practices, or any task involving skill metadata optimization (examples: \"optimize frontmatter\", \"fix skill triggering\", \"improve skill description\", \"why isn't my skill invoked\").
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeDeclared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Skill metadata
Parsed from SKILL.md frontmatter.
Declared agentsclaude-code
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md2,780 B
docsSUMMARY.md530 B
History
First seen on skills.sh
First recorded snapshot · 1 installs
SKILL.md
Skill Frontmatter Optimizer
Optimize skill frontmatter descriptions for reliable automatic invocation by Claude Code.
Core Problem
The description field is the sole triggering mechanism for skills. Claude only sees name + description (~100 words) until a skill triggers. The SKILL.md body is invisible until after the decision. Poor descriptions = unreliable invocation.
Optimization Workflow
Step 1: Analyze the Existing Skill
Run the analysis script to extract key information:
description: "[CAPABILITY_VERBS] [DOMAIN/FORMAT] [FEATURE_LIST]. Use this skill when [USER_INTENT] for: (1) [SCENARIO_1], (2) [SCENARIO_2], (3) [SCENARIO_3], or [CATCH_ALL]. (examples include [CONCRETE_TRIGGERS])"