Enforce frontmatter-driven structure and progressive disclosure in SKILL.md files.
npx skills add https://github.com/ahgraber/skills --skill optimize-skills
Please help me install this Agent Skill. Skill: optimize-skills Source: https://github.com/ahgraber/skills/tree/main/skills/optimize-skills Command: npx skills add https://github.com/ahgraber/skills --skill optimize-skills
This skill helps maintainers and authors craft concise, trigger-focused SKILL.md skills by enforcing a minimal, frontmatter-driven metadata surface and by guiding where deeper guidance should live (references, assets, scripts).
name and description to support reliable discovery.references/, assets/, and scripts/ to keep SKILL.md lean.Scaffold a new skill by creating SKILL.md with the required frontmatter and progressively move detailed guidance to references, assets, and scripts.
High-intent search queries and answers about installing and using this skill.
To optimize SKILL.md files for skill triggering, enforce a concise frontmatter-driven surface containing required name and description metadata, then progressively move verbose workflow details into referenced assets and scripts to keep the file lean.
The best way to structure a SKILL.md file is by applying progressive disclosure: keep the surface minimal with frontmatter, and move detailed guidance into organized component directories like references, assets, and scripts as needed.
SKILL.md skills fail to trigger reliably when they lack concise frontmatter or contain bloated content. Enforcing a minimal frontmatter surface with clear name and description fields supports accurate discovery and better trigger phrasing.
Yes, frontmatter is required in SKILL.md files for skill discovery. You must include name and description fields in the frontmatter to support reliable triggering and ensure users can find the skill.
Yes, you can use references and assets directories to organize detailed workflow guidance. This progressive disclosure approach keeps SKILL.md lean by moving verbose details into structured component directories while maintaining safe, testable guidance.
You should move detailed instructions out of SKILL.md into separate files when the content becomes verbose or bloated. Relocating deeper guidance to references, assets, and scripts ensures the SKILL.md surface remains concise and trigger-focused.
vasilyu1983Optimize LLM inference performance and cost with vLLM and quantization.
kehwarScaffold and validate Skill units with SKILL.md frontmatter and resource scaffolds.
pr-pmVerify Claude skill installation paths, directory structure, and frontmatter parsing in CI pipelines.
flutterConfigures dart_skills_lint for automated validation of AI agent skill directories.