openskills-plugin-separation
Enforce clean separation between core openskills-runtime and optional WASM build plugins so plugin compilation does not break runtime consumers or language bindings.
git clone --depth 1 https://github.com/Geeksfino/openskills /tmp/openskills-plugin-separation && cp -r /tmp/openskills-plugin-separation/.cursor/skills/openskills-plugin-separation ~/.claude/skills/openskills-plugin-separationSKILL.md
# OpenSkills Plugin Separation Use this skill when changing plugin features, build-tool wiring, or runtime dependency topology. ## Objective Keep core runtime usable without plugin toolchains, especially for bindings and non-build execution paths. ## Key Files - `runtime/Cargo.toml` - `runtime/src/lib.rs` - `runtime/src/bin/openskills-runtime.rs` - `runtime/src/build/**` - `bindings/ts/Cargo.toml` - `bindings/python/Cargo.toml` ## Separation Rules 1. Build plugins must be gated behind explicit features. 2. Core runtime defaults should not force plugin toolchains. 3. Bindings should opt out of plugin-heavy default features when appropriate. 4. Public exports for build functions must be feature-gated. 5. CLI build commands must degrade gracefully when build features are disabled. ## Validation Checklist - `cargo check -p openskills-runtime` passes with default features. - Bindings compile without pulling plugin-specific dependencies unintentionally. - Runtime tests that do not require plugin build paths continue to pass. ## Output Format - Feature graph summary - Leakage findings (if any) - Minimal patch plan - Post-change verification commands
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.
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.