Clear description of what this skill does and when to use it
Overall
score
27%
Does it follow best practices?
Validation for skill structure
Brief description of the skill and its purpose.
List any setup requirements:
Example setup:
export SKILL_API_KEY="your_api_key"How to use the skill quickly:
cd <skill_directory>
python3 scripts/command.py --option valuepython3 scripts/script.py "input"Output:
Expected output herepython3 scripts/script.py "input" --flag --option valueAll commands run from the skill directory.
python3 scripts/script1.py --help
python3 scripts/script1.py "param1" --option valuepython3 scripts/script2.py "param1" "param2"script1.py - Description of what this script doesscript2.py - Description of what this script doesSymptom: Description of the problem
Solution:
Symptom: Description of the problem
Solution:
See examples/ directory for full workflow examples.
The YAML frontmatter at the top of this file is required:
| Field | Type | Required | Description |
|---|---|---|---|
name | string | ✓ | Unique identifier (kebab-case) |
description | string | ✓ | What the skill does and when to use it |
triggers | array | ✓ | Keywords that activate this skill |
dependencies | object | Dependent skills (format: skill-name: ">=X.Y.Z") |
Use semantic versioning format:
"^1.0.0" - Compatible with 1.x versions">=1.0.0" - Version 1.0.0 or higher"1.0.0" - Exact version only">=1.0.0,<2.0.0" - Range of versionsskills/your-skill-name/scripts/examples/skills.json with your skill entryIf you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.