Agent skill · software engineering · paperclipai
paperclip-create-plugin
Create and develop external Paperclip plugins with the CLI-first workflow. Use when scaffolding a plugin, iterating on a local plugin, installing it into Paperclip, or updating plugin authoring docs.
Why this skill is useful
Provides specific commands and workflows for creating and managing Paperclip plugins that the AI wouldn't reliably generate on its own.
What it needs
Requires pnpm installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 75,771 stars on the source repository.
What this skill does
Create and develop a Paperclip plugin Use this skill when the task is to create, scaffold, or iterate on a Paperclip plugin against a local Paperclip instance. 1. Default: build the plugin OUTSIDE Paperclip core Plugins are their own packages. Unless the task explicitly asks for a bundled in-repo example, do not add plugin source under packages/plugins/ in this repo. Scaffold the plugin into a directory outside the Paperclip checkout (e.g. ~/dev/paperclip-plugins/<name>). Install it into the running Paperclip instance by local absolute path. Edit code in the external package; let Paperclip pick up rebuilt output. Only edit Paperclip core itself when the user asks to surface a plugin as a bundled example (server/src/routes/plugins.ts, in-repo example lists, docs). 2. Ground rules Reference docs when you need detail: 1. doc/plugins/PLUGINAUTHORINGGUIDE.md 2. packages/plugins/sdk/README.md 3. doc/plugins/PLUGINSPEC.md — future-looking context only Current runtime assumptions: plugin workers are trusted code plugin UI is trusted same-origin host code worker APIs are capability-gated plugin UI is not sandboxed by manifest capabilities no host-provided shared plugin UI component kit yet ctx.assets is not supported in the current runtime 3. CLI-first scaffold workflow Use paperclipai plugin init. Do not invoke the scaffold package node entrypoint by hand unless the CLI command is unavailable in the environment. Useful flags (all optional): --output <dir> — parent directory; the command creates <dir>/<unscoped-name>/. Defaults to the current directory. --template <default connector workspace environment> — starter template. --category <connector workspace automation ui environment> — manifest category. --display-name <name>, --description <text>, --author <name> — manifest metadata. --sdk-path <path> — snapshot the local SDK from a Paperclip checkout into .paperclip-sdk/ (useful when developing against an unreleased SDK). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills paperclipai/paperclip-create-plugin