Openskills plugin separation
Skill Geeksfino/openskills/.cursor/skills/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.From its SKILL.md
npx -y skills add Geeksfino/openskills --skill openskills-plugin-separationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.4 KB, 243 tokens by cl100k_base, as published. Nobody here has run it
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.tomlruntime/src/lib.rsruntime/src/bin/openskills-runtime.rsruntime/src/build/**bindings/ts/Cargo.tomlbindings/python/Cargo.toml
Separation Rules
- Build plugins must be gated behind explicit features.
- Core runtime defaults should not force plugin toolchains.
- Bindings should opt out of plugin-heavy default features when appropriate.
- Public exports for build functions must be feature-gated.
- CLI build commands must degrade gracefully when build features are disabled.
Validation Checklist
cargo check -p openskills-runtimepasses 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
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.