openskills-skill-authoring
Create and refine OpenSkills-compatible skills (SKILL.md + optional resources) with strong metadata, clear activation triggers, and reliable execution guidance.
git clone --depth 1 https://github.com/Geeksfino/openskills /tmp/openskills-skill-authoring && cp -r /tmp/openskills-skill-authoring/.cursor/skills/openskills-skill-authoring ~/.claude/skills/openskills-skill-authoringSKILL.md
# OpenSkills 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: - `name` - `description` - Body with concise instructions and practical execution flow. - Description must include both: - what the skill does - when to activate it ## Writing Guidance 1. Keep core instructions short; move details to `references/`. 2. Prefer deterministic scripts for fragile or repetitive steps. 3. Include explicit input/output expectations. 4. Avoid vague names and ambiguous activation phrases. ## Validation Flow 1. Ensure directory name matches skill `name` semantics. 2. Verify skill discovery and activation behavior in runtime or example agent. 3. If scripts are present, verify paths and execution assumptions. ## Output Format - Skill metadata quality review - Instruction clarity review - Activation trigger quality review - Suggested revisions
Maintain compatibility between openskills-runtime and language bindings (TypeScript, Python), including feature flags, build configuration, and smoke verification.
Route OpenSkills development tasks to the right project skill or subagent, including sequencing rules for debugging, feature work, regression checks, and release readiness.
Run deterministic OpenSkills end-to-end validation across runtime tests and example agents, then report tool calls, activation behavior, and regressions.
Enforce clean separation between core openskills-runtime and optional WASM build plugins so plugin compilation does not break runtime consumers or language bindings.
Prepare and validate OpenSkills release readiness across runtime, bindings, examples, and regression gates with a deterministic checklist and go/no-go outcome.
Diagnose openskills-runtime execution failures in sandboxed paths (Landlock, seatbelt, native script execution, wasm execution) and produce root-cause-first findings with minimal-risk remediation steps.
Reviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems.
Explains code clearly and thoroughly. Use when asked to explain, clarify, or teach about code snippets, functions, or concepts.