openskills

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.

Create and refine OpenSkills-compatible skills (SKILL.md + optional resources) with strong metadata, clear activation triggers, and reliable execution guidance.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Minimal skill for testing context fork behavior. Do not use in production.

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.