SDK for building OpenClaw plugins.

Define your tools and config. The SDK generates a fully typed OpenClaw plugin, a standalone CLI, and a plugin manifest — automatically.

npm install carapace-plugin-sdk

New plugin? Use carapace-plugin-template — it scaffolds the full project structure, CI, and tests in one click.

Here's what you write in src/plugin.ts:

import { definePlugin } from "carapace-plugin-sdk";
import { Type } from "@sinclair/typebox";

// The export must be named `createEntry` — the SDK's build tools look for it by name.
export const createEntry = definePlugin({
  id: "my-plugin",
  name: "My Plugin",
  description: "Does something useful.",

  configSchema: Type.Object({
    apiKey: Type.Optional(Type.String({ description: "API key for the service." })),
  }),

  tools: (tool) => [
    tool({
      name: "do_thing",
      description: "Does the thing.",
      parameters: Type.Object({
        input: Type.String({ description: "Input value." }),
      }),
      execute: async ({ input }, config) => {
        // input: string ✓   config.apiKey: string | undefined ✓
        return { result: input, usingKey: !!config.apiKey };
      },
    }),
  ],
});

Run npm run build and you get:

Nothing else to write. No registration boilerplate, no result wrapping, no manifest to maintain.

Add to package.json:

{
  "bin": { "my-plugin": "./dist/bin/my-plugin.js" },
  "scripts": {
    "build": "tsup && carapace-generate-cli --entry ./dist/plugin.js --out ./dist/bin"
  }
}

The SDK ships shared configs so your project files stay minimal:

tsconfig.json — one line:

{ "extends": "carapace-plugin-sdk/tsconfig.base.json" }

tsup.config.ts — three lines:

import { defineConfig } from "tsup";
import { definePluginConfig } from "carapace-plugin-sdk/tsup";

export default defineConfig(definePluginConfig());

vitest.config.ts — not needed. Vitest finds tests/**/*.test.ts without configuration.

Every plugin is automatically a standalone CLI. After npm run build:

my-plugin --help
my-plugin do-thing "hello"
my-plugin do-thing "hello" --json
MY_PLUGIN_API_KEY=sk-... my-plugin do-thing "hello"

Config fields map to environment variables: <PLUGIN_ID_SCREAMING_SNAKE>_<FIELD_SCREAMING_SNAKE>

Call the shared GitHub Actions workflows from your plugin repo — no workflow logic to copy:

# .github/workflows/ci.yml
jobs:
  ci:
    uses: JeffSteinbok/carapace-plugin-sdk/.github/workflows/plugin-ci.yml@main

# .github/workflows/release.yml
on:
  workflow_dispatch:
    inputs:
      version-bump:
        type: choice
        options: [patch, minor, major]
      prerelease:
        type: choice
        options: ['', alpha, beta, rc]
jobs:
  release:
    uses: JeffSteinbok/carapace-plugin-sdk/.github/workflows/plugin-release.yml@main
    with:
      version-bump: ${{ inputs.version-bump }}
      prerelease: ${{ inputs.prerelease }}
    secrets:
      npm-token: ${{ secrets.NPM_TOKEN }}

• carapace-plugin-template — starter template with CI, tests, and build pre-configured
• carapace-stock-quotes — real plugin with multiple data sources (Yahoo Finance + Finnhub)

See ARCHITECTURE.md for how the SDK works under the hood — the type machinery behind definePlugin, how carapace-generate-cli generates artifacts, the CLI runtime, and the adapter pattern.

MIT