ClaudeSkillsSource reviewed69ef37e9424c
Best practices
Write concise, reliable Agent Skills for Claude.
Agent Skills specification · Claude documentation
First-party guide reviewed against current official references. It is not a full official-documentation translation.
Source text is documentation. These workflows have not been executed or tested by this site.
On this page
This is an original ClaudeSkills guide reviewed against the references below on 2026-10-04. It is not a full official-documentation translation.
Make the trigger specific
Describe the task and the circumstances that call for the skill. Compare a positive example with a nearby request that should not trigger it.
Keep the main workflow readable
State the inputs, steps and success criteria. Put detailed references in separate files and link directly to them. Explain when to stop, ask for missing information or inspect an output.
Check the format
The open specification requires name and description. The name must match the folder, use lowercase letters, digits and hyphens, and be at most 64 characters. The description must be nonempty and at most 1024 characters. Optional compatibility and license fields make requirements clearer.
Test realistic tasks
Use representative inputs and inspect the resulting artifacts. Include ambiguous requests, missing files and an example that should not activate the skill. Record results without claiming that an untested source has passed.
Official references
Agent Skills specification · Claude best-practices · Claude Code skills