seis-plugin-runtime

Validates plugin manifests, capability lanes, and release gates for SEIS plugin governance.

1|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-plugin-runtime-emirhankudun-ux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seis-plugin-runtime
Source: https://github.com/emirhankudun-ux/SEIS/tree/main/plugins/seis/skills/seis-plugin-runtime
Command: npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-plugin-runtime-emirhankudun-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plugin ecosystems drift quickly: manifests fall out of sync, capability lanes become stale, and unverified plugins get treated as production-ready. This Skill keeps SEIS plugin work controlled and auditable by validating what is installed, enabled, gated, and safe to route before any release-facing claim is made. ## Core Features & Use Cases - Plugin Manifest Health Checks: Inspect plugin contracts, manifest sources, and lane status artifacts to detect mismatches and dependency issues. - Capability Lane Gating: Update capability records and dashboard-facing evidence only where contract-driven evidence exists, keeping release claims honest. - Evidence-First Integration Planning: Plan plugin updates in small, reversible steps with manifest snapshots and command output attached to every change. - Use Case: Before shipping a new SEIS plugin bundle, run the lane checks to confirm every plugin manifest is synced, every capability lane is validated, and no unapproved external installer is marked active. ## Quick Start Ask the agent to audit the current SEIS plugin manifests and capability lanes, then report which plugins are gated, healthy, or blocked before release.

Frequently Asked Questions about seis-plugin-runtime

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

FAQPage Schema
How do I validate plugin manifests before a release?▼

Run the lane validation commands such as npm run check:seis-plugin-bundle and npm run check:plugin-capability-lanes to confirm manifests are synced and capability lanes match contract evidence. Attach command output and manifest snapshots to any runtime change.

How to check plugin capability lanes in SEIS?▼

Use npm run check:plugin-capability-lanes to compare capability records against manifest-backed evidence. Update lane metadata and dashboard-facing records only where contract-driven evidence exists.

Can this skill auto-install or activate external plugins?▼

No. Auto-installation and unscoped activation are explicitly out of scope. Any plugin action involving external installers or external permissions stays in planned state until explicit user approval is given.

What evidence is required before marking a plugin release-ready?▼

Release-ready gating requires manifest snapshots, command output, and check command status attached to the change, plus passing results from the plugin integration, specialist plugin, capability lane, and bundle checks.

What are the limitations of this plugin runtime approach?▼

Capability inventory is not proof of real authentication or production access, and the skill never mutates plugin state without explicit user intent and lane ownership. It is designed for repository-safe governance, not ad-hoc marketplace actions.