openskills-bindings-maintainer
Maintain compatibility between openskills-runtime and language bindings (TypeScript, Python), including feature flags, build configuration, and smoke verification.
git clone --depth 1 https://github.com/Geeksfino/openskills /tmp/openskills-bindings-maintainer && cp -r /tmp/openskills-bindings-maintainer/.cursor/skills/openskills-bindings-maintainer ~/.claude/skills/openskills-bindings-maintainerSKILL.md
# OpenSkills Bindings Maintainer Use this skill when runtime APIs, features, or dependency topology changes may affect bindings. ## Scope - `bindings/ts/**` - `bindings/python/**` - runtime crate feature interactions affecting bindings ## Workflow 1. Identify runtime change surface (API, features, dependencies). 2. Check both bindings for feature/compile assumptions. 3. Verify build and smoke tests for each binding. 4. Confirm lockfile and manifest consistency where applicable. ## TS Binding Checks ```bash cd bindings/ts npm install npm run build ``` ## Python Binding Checks Use project-standard build/test commands for Python bindings and confirm import/runtime behavior. ## Guardrails - Avoid introducing plugin/build-tool dependencies into default binding paths unless intentional. - Keep generated files and lockfiles aligned with project policy. ## Output Format - Compatibility matrix (runtime vs TS/Python) - Breaking changes - Required migration steps - Verification evidence
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.
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.