The Capability Layer

## Turn every tool into
a discoverable capability

supercli standardizes inputs, outputs, and execution across 999+ bundled plugins — from AWS, GitHub, Docker, to Kubernetes and beyond.

999+

Bundled plugins

Zero

Setup required

One

Consistent interface

Explore 999+ Plugins

Quick filter

Start here

## Getting Started

supercli runs in two modes: Local-only (default, no server required) or Server mode (optional, shared backend). Run `npx supercli help` for instant usage or `npx supercli --help` for all options.

Local-only: `npx supercli help`, `supercli beads issue list`, `supercli skills list` — everything works out of the box, no installation needed.

Server mode: Install dependencies (`npm install`), copy `.env.example` to `.env`, then start via `npm start` or `supercli --server`. The web UI is reachable at `http://localhost:3000`.

Refer to the repository README for detailed setup instructions.

Concept

## Capability Layer Basics

Every executable unit becomes a capability, whether it originates from CLI commands, OpenAPI endpoints, MCP tools, workflows, or HTTP requests. supercli indexes capabilities as `namespace.resource.action`, exposes schemas, and lets agents discover, inspect, and execute consistently.

    supercli skills list
    supercli skills search "database"
    supercli skills get beads.issue.create

Sources

## Capability Sources

### Plugin Harnesses

999 bundled plugins (gh, aws, gcloud, az, docker, kubectl, terraform, stripe, supabase, and many more) via `supercli plugins install`.

Explore Plugins

### Built-in Adapters

OpenAPI specs, raw HTTP, and MCP servers become capabilities automatically.

### AI Plans / Workflows

Natural language `ask` and `plan` commands create DAGs of capabilities.

Runtime

## Architecture

Agents route requests through the capability discovery layer, which maps namespaces to harnesses/adapters. Execution envelopes guarantee deterministic JSON responses and exit codes.

    Agents/Humans → supercli runtime → Capability Router → Harness / Adapter → Tool

Interface

## CLI Usage

    supercli help                     # list harnesses
    supercli <namespace>              # list capabilities in harness
    supercli beads issue list --json
    supercli skills list
    supercli skills teach
    supercli discover --intent "deploy app"
    supercli inspect beads issue create
    supercli plugins explore
    supercli plugins show <name>

`--json`, `--human`, and `--compact` control output, while exit codes communicate validation, resource, or integration errors.

Extension

## Plugins & Harnesses

supercli extends via 999 bundled plugin harnesses and supports custom plugin authoring. Each plugin lives in its own directory with isolated metadata — no shared file edits needed.

### manifest.json

Commands, schemas, dependency checks, passthrough rules

### meta.json

Registry metadata (description, tags, has_learn flag)

### install-guidance.json

Optional install steps

Need more? Check `docs/plugins-how-to.md` for authoring details, or `supercli plugins explore` to browse available plugins.

Vision

## Capability Mesh Direction

The platform is evolving toward a mesh that handles discovery, routing, execution, composition, and governance. Key areas under exploration include a unified capability registry, graph-native discovery, mesh-wide policy, DAG orchestration, agent endpoints, composition tooling, telemetry, and richer plugin UX.

Resources

## More Documentation

### Plugin Directory

Browse all 999+ plugins — from AWS and GitHub to Docker, Kubernetes, and beyond.

### README.md

Repository root documentation

### docs/skills-catalog.md

Skills reference catalog

### docs/features/skills.md

Skills feature documentation

### docs/plugins.md

Plugin system overview

### docs/plugins-how-to.md

Plugin authoring guide

Extension

## Custom Adapters

Server

## Server UI

## Navigate