openskills-skill-authoring
Scannednpx machina-cli add skill Geeksfino/openskills/openskills-skill-authoring --openclawOpenSkills Skill Authoring
Use this skill when creating or updating skills under examples/skills or any OpenSkills-compatible skill directory.
Authoring Standard
Each skill directory should include:
SKILL.md(required)- optional
scripts/,references/,assets/
SKILL.md Requirements
- YAML frontmatter with:
namedescription
- Body with concise instructions and practical execution flow.
- Description must include both:
- what the skill does
- when to activate it
Writing Guidance
- Keep core instructions short; move details to
references/. - Prefer deterministic scripts for fragile or repetitive steps.
- Include explicit input/output expectations.
- Avoid vague names and ambiguous activation phrases.
Validation Flow
- Ensure directory name matches skill
namesemantics. - Verify skill discovery and activation behavior in runtime or example agent.
- If scripts are present, verify paths and execution assumptions.
Output Format
- Skill metadata quality review
- Instruction clarity review
- Activation trigger quality review
- Suggested revisions
Source
git clone https://github.com/Geeksfino/openskills/blob/main/.cursor/skills/openskills-skill-authoring/SKILL.mdView on GitHub Overview
OpenSkills Skill Authoring provides a structured approach to creating and refining SKILL.md-based skills. It enforces strong metadata, clear activation triggers, and reliable execution guidance to ensure consistent discovery and runtime behavior across skill directories.
How This Skill Works
Authors prepare a skill directory containing SKILL.md with YAML frontmatter (name and description) and a concise body. They then use the validation flow to verify that the directory name matches the skill semantics, activation triggers are explicit, and any scripts or resources have correct paths before publishing.
When to Use It
- When creating a brand-new OpenSkills skill under examples/skills
- When updating an existing OpenSkills-compatible skill to improve metadata and activation
- When standardizing activation triggers and execution flow across skills
- When adding optional resources (scripts/references/assets) to a skill
- When validating discovery, activation, and runtime behavior before deployment
Quick Start
- Step 1: Create or open the skill directory (examples/skills/your-skill)
- Step 2: Add SKILL.md with YAML frontmatter (name, description) and a concise body describing inputs/outputs and activation
- Step 3: Run the validation flow to confirm metadata, activation behavior, and script paths
Best Practices
- Keep YAML frontmatter concise with name and description
- Use deterministic, testable scripts for repetitive steps
- Define explicit input/output expectations in the body
- Avoid vague activation phrases; make triggers explicit and unique
- Place detailed guidance in a references/ folder and keep SKILL.md focused on flow
Example Use Cases
- Create a new skill directory under examples/skills with a SKILL.md that defines name, description, and a concrete activation trigger
- Refine an existing skill by updating its metadata and clarifying activation flow for reliability
- Add stable scripts under scripts/ and reference them in the body with clear I/O
- Verify that the directory name semantically matches the skill name
- Run the validation flow to ensure discovery and execution behave as expected