Checking if an existing skill follows best practices
Understanding token budgets and progressive disclosure
Constraints
name: 1-64 chars, lowercase + hyphens, match directory
description: 1-1024 chars, ≤60 words, explain WHAT and WHEN
Use WHEN: with quoted trigger phrases (preferred over USE FOR:)
Avoid DO NOT USE FOR: unless the skill has trigger overlap with a broader skill (see frontmatter guidelines)
Use inline double-quoted strings (not >- folded scalars)
SKILL.md: <500 tokens (soft), <5000 (hard)
references/*.md: <1000 tokens each
Structure
SKILL.md (required) - Instructions
references/ (optional) - Detailed docs
scripts/ (optional) - Executable code
Frontmatter: name (lowercase-hyphens), description (WHAT + WHEN)
Progressive Disclosure
Metadata (~100 tokens) loads at startup. SKILL.md (<5000 tokens) loads on activation. References load only when explicitly linked (not on activation). Keep SKILL.md lean.
Reference Loading
References are JIT (just-in-time) loaded:
Only files explicitly linked via [text](references/file.md) load
Link to files, not folders - [Recipes](references/recipes/README.md) not [Recipes](references/recipes/)
Each file loads in full (not sections)
No caching between requests - write self-contained files
Create or improve portable agent skills with clear trigger metadata, focused instructions, bundled resources, safety boundaries, and real validation. Use when writing, reviewing, refactoring, packaging, or publishing a SKILL.md skill for PapiSkill, Codex, Claude Code, Factory, GitHub Copilot, Cursor, VS Code, or another agent runtime.
Development workflows for the playwright-cli repository. Use when the user asks about rolling dependencies, releasing, or other repo maintenance tasks.