AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Openskills Plugin Separation

skill-geeksfino-openskills-openskills-plugin-separation · by Geeksfino

Enforce clean separation between core openskills-runtime and optional WASM build plugins so plugin compilation does not break runtime consumers or language bindings.

↗ Repository
— No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add skill-geeksfino-openskills-openskills-plugin-separation

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Openskills Plugin Separation? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills