CATLX — Plugin Ecosystem
This skill owns how CATLX grows beyond its built-in capabilities: isolated, versioned, sandboxed,
replaceable plugins, with a marketplace-ready SDK and security guarantees.
Canonical detail: ../knowledge/references/plugin-ecosystem.md. Manifest template:
../templates/plugin-manifest.json. Load on demand.
Purpose
Let third-party developers extend CATLX safely, with signature verification, capability grants, sandboxing,
and deterministic dependency resolution — without exposing internal CATLX module IDs or risking the host
runtime.
When to activate
- User asks how to write/install/update/uninstall a CATLX plugin.
- Configuring plugin signing, capability grants, or the marketplace.
- Debugging plugin sandboxing, hot reload, or dependency conflicts.
What this skill handles
- Plugin architecture philosophy — every non-core capability can be a plugin; plugins are isolated,
versioned, sandboxed, replaceable; support a public marketplace while maintaining host security.
- Plugin Runtime — isolated execution environment separate from core; worker threads (T0/T1) or Docker
containers (T2+); versioned Plugin API via a typed proxy; internal module IDs never exposed.
- Plugin security — every package signed with the developer's private key; runtime verifies against the
registered public key; unsigned plugins rejected unless developer mode is enabled. At install the user
reviews declared capabilities (file access, network hosts, credential names) and approves/rejects each;
approvals stored in
plugins.db and checked at every invocation.
- Plugin SDK —
@catlx/plugin-sdk npm package: TypeScript types for the full Plugin API, scaffolding
CLI (catlx plugin new my-plugin), test harness, mock core-CATLX services, build toolchain
(esbuild + manifest generator).
- Marketplace readiness — integrated panel in the Electron shell + web portal (marketplace.catlx.ai);
discover by category, capability, hardware-tier compatibility, rating; in-app client handles search, one-click
install, update notifications, uninstall; authors submit via the Developer Portal which auto-scans
(static analysis + capability audit) before listing.
- Hot reload — during development, a file watcher reloads a plugin module without restarting CATLX;
in-flight calls finish under the old version; disabled for production unless explicitly opted in.
- Version management & dependency resolution — deterministic resolver (analogous to yarn berry PnP);
each plugin vendors its own third-party deps; a module alias map resolves imports; breaking API changes via
API versioning with a compatibility shim up to 2 major versions back.
Requirements / constraints
- R5 (least privilege): capability grants reviewed and stored in
plugins.db; enforced per invocation.
- R9 (modularity): plugins are isolated/replaceable.
- Sandbox tier from CapabilityMap (
plugin_sandbox = process / quota / docker).
Canonical knowledge it reads
../knowledge/references/plugin-ecosystem.md · ../knowledge/references/security.md ·
../knowledge/references/folder-structure.md · ../knowledge/references/data-registries.md.
Delegation
- Signing/capability grant/sandbox enforcement → delegate to
catlx-security
(skill({ name: "catlx-security" })).
- Plugin packaging/artifact → delegate to
catlx-silexis-modules
(skill({ name: "catlx-silexis-modules" })).
- Marketplace panel in the shell → delegate to
catlx-electron-shell
(skill({ name: "catlx-electron-shell" })).
- Docker-container plugin sandbox → delegate to
catlx-docker
(skill({ name: "catlx-docker" })).
- Registering plugin capabilities with the router → delegate to
catlx-capability-routing
(skill({ name: "catlx-capability-routing" })).
Edge cases & warnings
- Unsigned plugin: reject unless explicit developer mode (local development only).
- Capability grant: the user approves each capability; un-granted access is blocked and logged.
- Dependency conflicts: vendored copies + module alias map prevent host/plugin conflicts.
- Hot reload: only for development; production plugins are loaded immutably.
- Destroying sandbox on uninstall: call
cleanup(), deregister capabilities, remove files.
Component lifecycle policy (reuse → install → adapt → create)
NEVER create a new component as the default. Before building/creating anything (a sub-skill, dependency,
reference, workflow, helper, adapter, or template), check, in order:
- Reuse an existing local component (resolve aliases/equivalent capabilities first) — reuse, don't rebuild.
- Use an already-registered component from the registry.
- Install a suitable existing, trusted, supported component → validate → register → connect to the graph → use.
- Adapt an existing compatible component via a small persistent adapter/wrapper instead of re-creating it.
- Create only as last resort — then make it permanent immediately: stable id, canonical location, register,
add to the capability index + dependency graph, add provenance, use, and allow future reuse.
- Never reorganise/recreate already-generated components (no
Skill X 2 / new / temp variants); extend the
existing one. Never create a second competing knowledge source; connect back to the canonical knowledge/ layer.
Promote any reusable artifact out of /tmp/scratch into the permanent ecosystem.
Full policy: ../knowledge/rules/component-lifecycle.md.
Source / provenance
- Source: PART XIII §13.1–13.7 (philosophy, runtime, security, SDK, marketplace readiness, hot reload,
version management & dependency resolution).
- Inferred: none; plugin/Publisher/Portal naming preserved; marketplace coordinates (
marketplace.catlx.ai)
preserved as source facts, not endorsements.
1---2> Mirror copy of `skills\catlx-core\catlx-plugin-ecosystem\SKILL.md` (canonical content lives in `catlx-core`). Kept at the repository root only for registry-path compatibility. Edit the canonical copy, not this file.3name: catlx-plugin-ecosystem4description: "Handles the CATLX plugin ecosystem: the plugin runtime (worker threads / Docker), signed plugin security with capability grants, the @catlx/plugin-sdk, the Plugin Marketplace, hot reload, and version management with deterministic dependency resolution (PnP-style) and API compatibility shims. Use when the user asks about CATLX plugins, writing/installing a plugin, the Plugin SDK, marketplace, hot reload, plugin signing/security, or plugin dependency resolution."5metadata:6 catlx: subsystem7 category: architecture8 subsystem: Plugin_Runtime9 capability: plugin-ecosystem10 version: "1.0.0"11 source: https://skillmd.com/skills/samraddhashrivastavatech/catlx-plugin-ecosystem12 upstream: "PART XIII §13.1-13.7"13 aliases: "plugins, plugin, plugin sdk, marketplace, extensions, hot reload"14 depends-on: "catlx-silexis-modules, catlx-security, catlx-electron-shell, catlx-docker"15---1617# CATLX — Plugin Ecosystem1819This skill owns how CATLX **grows beyond its built-in capabilities**: isolated, versioned, sandboxed,20replaceable plugins, with a marketplace-ready SDK and security guarantees.2122> Canonical detail: `../knowledge/references/plugin-ecosystem.md`. Manifest template:23> `../templates/plugin-manifest.json`. Load on demand.2425---2627## Purpose2829Let third-party developers extend CATLX safely, with signature verification, capability grants, sandboxing,30and deterministic dependency resolution — without exposing internal CATLX module IDs or risking the host31runtime.3233## When to activate3435- User asks how to write/install/update/uninstall a CATLX plugin.36- Configuring plugin signing, capability grants, or the marketplace.37- Debugging plugin sandboxing, hot reload, or dependency conflicts.3839## What this skill handles40411. **Plugin architecture philosophy** — every non-core capability can be a plugin; plugins are isolated,42 versioned, sandboxed, replaceable; support a public marketplace while maintaining host security.432. **Plugin Runtime** — isolated execution environment separate from core; worker threads (T0/T1) or Docker44 containers (T2+); versioned Plugin API via a typed proxy; internal module IDs never exposed.453. **Plugin security** — every package signed with the developer's private key; runtime verifies against the46 registered public key; **unsigned plugins rejected** unless developer mode is enabled. At install the user47 reviews declared capabilities (file access, network hosts, credential names) and approves/rejects each;48 approvals stored in `plugins.db` and checked at every invocation.494. **Plugin SDK** — `@catlx/plugin-sdk` npm package: TypeScript types for the full Plugin API, scaffolding50 CLI (`catlx plugin new my-plugin`), test harness, mock core-CATLX services, build toolchain51 (esbuild + manifest generator).525. **Marketplace readiness** — integrated panel in the Electron shell + web portal (marketplace.catlx.ai);53 discover by category, capability, hardware-tier compatibility, rating; in-app client handles search, one-click54 install, update notifications, uninstall; authors submit via the Developer Portal which auto-scans55 (static analysis + capability audit) before listing.566. **Hot reload** — during development, a file watcher reloads a plugin module without restarting CATLX;57 in-flight calls finish under the old version; disabled for production unless explicitly opted in.587. **Version management & dependency resolution** — deterministic resolver (analogous to yarn berry PnP);59 each plugin vendors its own third-party deps; a module alias map resolves imports; breaking API changes via60 API versioning with a compatibility shim up to **2 major versions back**.6162## Requirements / constraints6364- **R5 (least privilege):** capability grants reviewed and stored in `plugins.db`; enforced per invocation.65- **R9 (modularity):** plugins are isolated/replaceable.66- Sandbox tier from CapabilityMap (`plugin_sandbox` = process / quota / docker).6768## Canonical knowledge it reads6970`../knowledge/references/plugin-ecosystem.md` · `../knowledge/references/security.md` ·71`../knowledge/references/folder-structure.md` · `../knowledge/references/data-registries.md`.7273## Delegation7475- **Signing/capability grant/sandbox enforcement** → delegate to `catlx-security`76 (`skill({ name: "catlx-security" })`).77- **Plugin packaging/artifact** → delegate to `catlx-silexis-modules`78 (`skill({ name: "catlx-silexis-modules" })`).79- **Marketplace panel in the shell** → delegate to `catlx-electron-shell`80 (`skill({ name: "catlx-electron-shell" })`).81- **Docker-container plugin sandbox** → delegate to `catlx-docker`82 (`skill({ name: "catlx-docker" })`).83- **Registering plugin capabilities with the router** → delegate to `catlx-capability-routing`84 (`skill({ name: "catlx-capability-routing" })`).8586## Edge cases & warnings8788- **Unsigned plugin:** reject unless explicit developer mode (local development only).89- **Capability grant:** the user approves each capability; un-granted access is blocked and logged.90- **Dependency conflicts:** vendored copies + module alias map prevent host/plugin conflicts.91- **Hot reload:** only for development; production plugins are loaded immutably.92- **Destroying sandbox on uninstall:** call `cleanup()`, deregister capabilities, remove files.9394## Component lifecycle policy (reuse → install → adapt → create)9596**NEVER create a new component as the default.** Before building/creating anything (a sub-skill, dependency,97reference, workflow, helper, adapter, or template), check, in order:981. **Reuse** an existing local component (resolve aliases/equivalent capabilities first) — reuse, don't rebuild.992. **Use** an already-registered component from the registry.1003. **Install** a suitable existing, trusted, supported component → validate → register → connect to the graph → use.1014. **Adapt** an existing compatible component via a small persistent adapter/wrapper instead of re-creating it.1025. **Create only as last resort** — then make it permanent immediately: stable id, canonical location, register,103 add to the capability index + dependency graph, add provenance, use, and allow future reuse.1046. Never reorganise/recreate already-generated components (no `Skill X 2` / `new` / `temp` variants); extend the105 existing one. Never create a second competing knowledge source; connect back to the canonical `knowledge/` layer.106 Promote any reusable artifact out of `/tmp`/scratch into the permanent ecosystem.107108> Full policy: `../knowledge/rules/component-lifecycle.md`.109110## Source / provenance111112- **Source:** PART XIII §13.1–13.7 (philosophy, runtime, security, SDK, marketplace readiness, hot reload,113 version management & dependency resolution).114- **Inferred:** none; plugin/Publisher/Portal naming preserved; marketplace coordinates (`marketplace.catlx.ai`)115 preserved as source facts, not endorsements.