paperclip-create-plugin

Scaffold and develop Paperclip plugins using the CLI-first local install workflow.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/Douglas-v/strategic-ai-paperclip-lab --skill paperclip-create-plugin-douglas-v
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paperclip-create-plugin
Source: https://github.com/Douglas-v/strategic-ai-paperclip-lab/tree/main/paperclip/skills/paperclip-create-plugin
Command: npx skills add https://github.com/Douglas-v/strategic-ai-paperclip-lab --skill paperclip-create-plugin-douglas-v

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating a Paperclip plugin involves many moving parts: scaffolding the package, wiring the manifest, worker, and UI entries, installing it into a running Paperclip instance, and verifying everything works. This Skill guides the entire CLI-first workflow so plugins are built correctly outside Paperclip core and pass verification before being declared done. ## Core Features & Use Cases - CLI-first scaffolding: Uses paperclipai plugin init with templates, categories, and SDK snapshot options, with a documented fallback when the CLI is not on PATH. - Local install and rebuild loop: Covers paperclipai plugin install <path>, watch-mode rebuilds, worker restarts, and UI hot-reload caveats. - Verification and success checklist: Enforces pnpm typecheck, pnpm test, pnpm build, plus a structured report of scaffold path, commands run, install status, and reload limitations. - Use Case: A developer wants to add a custom connector plugin to their local Paperclip instance. The Skill scaffolds the package in an external directory, installs it by absolute path, and confirms the plugin reports ready status via paperclipai plugin list. ## Quick Start Create a new Paperclip plugin called @acme/my-plugin, install it into my running local Paperclip instance, and verify it builds and passes tests.

Frequently Asked Questions about paperclip-create-plugin

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

FAQPage Schema
How do I create a new Paperclip plugin?

Run `paperclipai plugin init @acme/my-plugin --output <dir>` to scaffold the package, then run `pnpm install`, `pnpm dev`, and `paperclipai plugin install <absolute-path>` in the generated folder. The CLI prints the exact next commands on success.

How do I install a local Paperclip plugin for development?

Use `paperclipai plugin install /absolute/path/to/my-plugin`. The CLI auto-detects local paths and the server watches the plugin's `dist/` output, restarting the worker on rebuild so you do not need to reinstall after every edit.

Should I develop my plugin inside the Paperclip repo?

No. Plugins are their own packages and should be scaffolded outside the Paperclip checkout, then installed by local path. Only edit Paperclip core when explicitly creating a bundled in-repo example, which also requires updating `server/src/routes/plugins.ts`.

What if the paperclipai CLI is not available on PATH?

Fall back to building the scaffold package with `pnpm --filter @paperclipai/create-paperclip-plugin build` and invoking its node entrypoint directly with the same arguments, including `--output` and `--sdk-path` pointing at the local SDK.

What limitations exist in the current Paperclip plugin runtime?

Plugin workers and UI run as trusted code, worker APIs are capability-gated, and plugin UI is not sandboxed by manifest capabilities. `ctx.assets` is not supported, there is no host-provided shared UI component kit, and `--version` only applies to npm installs, not local paths.

How do I verify a Paperclip plugin works before finishing?

Run `pnpm typecheck`, `pnpm test`, and `pnpm build` from the plugin folder, then check `paperclipai plugin list` and `plugin inspect` for a `ready` status. Report any non-ready status with its `lastError` and note anything that did not hot-reload.