extension-api

Define a unified Extension API for domain bundles to declare skills and discover modules.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill extension-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extension-api
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/plan-marshall/skills/extension-api
Command: npx skills add https://github.com/cuioss/plan-marshall --skill extension-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill defines a unified Extension API that allows domain bundles to declare their skills and participate in module discovery and command resolution.

Core Features & Use Cases

  • ExtensionBase: a single abstract base class for all domain extensions.
  • Discovery utilities: load, aggregate, and expose skill domains from multiple bundles.
  • Canonical commands: shared vocabulary enabling consistent command resolution across domains.
  • Build utilities: helpers for module discovery, path resolution, and descriptor parsing.

Quick Start

Run the extension discovery command to load and register the Extension API across all bundles.

Frequently Asked Questions about extension-api

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

FAQPage Schema
How do I unify module discovery across multiple domain bundles?

To unify module discovery across multiple domain bundles, use the Extension API to load and aggregate skill domains through its built-in discovery utilities. It provides a consistent mechanism for cross-bundle interoperability.

What is an abstract base class for domain extensions?

An abstract base class for domain extensions is a single contract, known as ExtensionBase, that allows domain bundles to declare their skills and participate in standardized command resolution.

How do I resolve canonical commands across different domain skills?

To resolve canonical commands across different domain skills, implement the shared command vocabulary defined by the Extension API. This establishes consistent command resolution and cross-domain interoperability.

Does the Extension API require specific dependencies for module path resolution?

The Extension API has no external dependencies and provides its own build utilities for module discovery, path resolution, and descriptor parsing to ensure stable integration across bundles.

How do I register skill domains using an extension discovery script?

To register skill domains using an extension discovery script, run the canonical extension discovery command provided by the API. This action loads and registers the API across all participating bundles.