openskills-plugin-separation

Separate OpenSkills core runtime from WASM build plugins using Rust feature flags.

68|14|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/Geeksfino/openskills --skill openskills-plugin-separation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openskills-plugin-separation
Source: https://github.com/Geeksfino/openskills/tree/main/.cursor/skills/openskills-plugin-separation
Command: npx skills add https://github.com/Geeksfino/openskills --skill openskills-plugin-separation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that the core OpenSkills runtime remains stable and usable, even when plugin development or build processes introduce changes or dependencies. It prevents plugin compilation issues from affecting the main functionality.

Core Features & Use Cases

  • Feature Gating: Manages build plugins using Rust's feature flags to control their inclusion.
  • Dependency Management: Prevents core runtime and language bindings from unintentionally pulling in plugin-specific toolchains.
  • Use Case: When updating the WASM build plugins for OpenSkills, this skill helps verify that the core runtime and Python/TypeScript bindings can still be built and used independently without errors.

Quick Start

Use the openskills-plugin-separation skill to verify that the core openskills-runtime can be checked with default features.

Frequently Asked Questions about openskills-plugin-separation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate WASM plugin builds from a Rust runtime?

To isolate WASM plugin builds from a Rust runtime, enforce a clear separation between the core runtime and optional build plugins. This manages plugin compilation and dependency topology to ensure the core runtime remains unaffected by plugin toolchains.

How does feature gating control optional build plugins in Rust?

Feature gating controls optional build plugins in Rust by using feature flags to manage their inclusion. This mechanism prevents the core runtime and language bindings from unintentionally pulling in plugin-specific toolchains during compilation.

Why does my Rust core runtime pull in plugin-specific dependencies?

Your Rust core runtime pulls in plugin-specific dependencies due to a lack of dependency topology management. Validating build integrity and enforcing separation prevents this unintentional dependency leakage into the core runtime.

Can I build Python and TypeScript bindings independently of WASM plugins?

Yes, you can build Python and TypeScript bindings independently of WASM plugins. Enforcing runtime separation verifies that language bindings can be checked and built with default features without requiring plugin toolchains.

What is dependency leakage in Rust build toolchains?

Dependency leakage in Rust build toolchains occurs when plugin compilation unintentionally affects the core runtime. Managing dependency topology and validating build integrity identifies and prevents this leakage from impacting core functionality.