$npx -y skills add Geeksfino/openskills --skill openskills-skill-authoringCreate and refine OpenSkills-compatible skills (SKILL.md + optional resources) with strong metadata, clear activation triggers, and reliable execution guidance.
| 1 | # OpenSkills Skill Authoring |
| 2 | |
| 3 | Use this skill when creating or updating skills under `examples/skills` or any OpenSkills-compatible skill directory. |
| 4 | |
| 5 | ## Authoring Standard |
| 6 | |
| 7 | Each skill directory should include: |
| 8 | |
| 9 | - `SKILL.md` (required) |
| 10 | - optional `scripts/`, `references/`, `assets/` |
| 11 | |
| 12 | ## SKILL.md Requirements |
| 13 | |
| 14 | - YAML frontmatter with: |
| 15 | - `name` |
| 16 | - `description` |
| 17 | - Body with concise instructions and practical execution flow. |
| 18 | - Description must include both: |
| 19 | - what the skill does |
| 20 | - when to activate it |
| 21 | |
| 22 | ## Writing Guidance |
| 23 | |
| 24 | 1. Keep core instructions short; move details to `references/`. |
| 25 | 2. Prefer deterministic scripts for fragile or repetitive steps. |
| 26 | 3. Include explicit input/output expectations. |
| 27 | 4. Avoid vague names and ambiguous activation phrases. |
| 28 | |
| 29 | ## Validation Flow |
| 30 | |
| 31 | 1. Ensure directory name matches skill `name` semantics. |
| 32 | 2. Verify skill discovery and activation behavior in runtime or example agent. |
| 33 | 3. If scripts are present, verify paths and execution assumptions. |
| 34 | |
| 35 | ## Output Format |
| 36 | |
| 37 | - Skill metadata quality review |
| 38 | - Instruction clarity review |
| 39 | - Activation trigger quality review |
| 40 | - Suggested revisions |