skill-guide

Guides creation and modification of SKILL.md skill units with frontmatter and structure conventions.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/psw7205/skills --skill skill-guide-psw7205
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-guide
Source: https://github.com/psw7205/skills/tree/main/skills/skill-guide
Command: npx skills add https://github.com/psw7205/skills --skill skill-guide-psw7205

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing a new agent skill or editing an existing one often leads to broken frontmatter, weak trigger descriptions, and bloated SKILL.md files that never activate. This Skill provides the conventions, checklists, and design patterns needed to author well-structured, reliably triggered skills in this repository. ## Core Features & Use Cases - Authoring checklist: Covers frontmatter rules (name, description, no angle brackets), bilingual trigger phrases, imperative tone, and mandatory Gotchas sections. - Progressive Disclosure sizing: Enforces the 500-line SKILL.md limit with references/ and scripts/ split strategies and directory structure patterns. - Design patterns: Documents scripts bundling with fallbacks, mode constraints, loop exit conditions, setup config, and memory storage patterns. - Use Case: When you ask to create a new skill for automating a workflow, this Skill guides naming, description writing for reliable triggering, structure selection, and validation via frontmatter parsing and trigger tests. ## Quick Start Ask the agent to create a new skill for your workflow and have it follow the skill-guide conventions for frontmatter, description, and structure.

Frequently Asked Questions about skill-guide

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

FAQPage Schema
How do I write a SKILL.md file for an agent skill?▼

Create a directory with a kebab-case name containing SKILL.md with YAML frontmatter defining name and description, followed by imperative markdown instructions. Keep the body under 500 lines and move detailed specs into a references/ directory.

How to write a skill description that triggers reliably?▼

Include both what the skill does and concrete trigger phrases users would actually say, in both Korean and English. Write slightly pushy descriptions since agents tend to under-trigger, and avoid abstract summaries like 'PDF tool'.

What is Progressive Disclosure in agent skills?▼

Progressive Disclosure is a three-stage loading model: name and description load always, the SKILL.md body loads on trigger, and references or scripts load only when explicitly needed. This keeps context usage minimal while allowing unlimited bundled resources.

Why does my skill frontmatter fail to parse?▼

Frontmatter parsing breaks when the description contains angle bracket characters. Use a YAML block scalar and avoid literal less-than or greater-than signs in the description text.

When should I split skill content into a references directory?▼

Split content when SKILL.md exceeds roughly 500 lines or when material is not needed on every invocation. Reference files over 300 lines should include a table of contents so the agent can navigate them efficiently.