paperclip-create-plugin

Scaffold, install, and verify external Paperclip plugins using the CLI-first workflow.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill paperclip-create-plugin-adamtpang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paperclip-create-plugin
Source: https://github.com/adamtpang/summon.company/tree/main/.agents/skills/paperclip-create-plugin
Command: npx skills add https://github.com/adamtpang/summon.company --skill paperclip-create-plugin-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developing a Paperclip plugin involves many moving parts: scaffolding the package, wiring the manifest, installing it into a running Paperclip instance, and verifying the build. This Skill guides an AI agent through that entire CLI-first workflow so plugins are created as external packages and installed correctly the first time. ## Core Features & Use Cases - CLI-first scaffolding: Uses paperclipai plugin init with template, category, and SDK snapshot flags to generate a complete plugin package outside the Paperclip repo. - Local install and rebuild loop: Installs plugins by absolute local path with paperclipai plugin install, leveraging the server's watch mode so rebuilt dist/ output reloads without reinstalling. - Verification and reporting: Runs pnpm typecheck, pnpm test, and pnpm build, then reports scaffold path, install status, and reload limitations. - Use Case: Ask the agent to create a new connector plugin for your Paperclip instance; it scaffolds the package in an external directory, installs it locally, confirms plugin list shows a ready status, and reports the exact commands run. ## Quick Start Create a new Paperclip plugin called @acme/my-plugin, install it into my 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 a plugin package outside the Paperclip repo. Then run `pnpm install`, `pnpm dev`, and `paperclipai plugin install <absolute-path>` to load it into your running instance.

How do I install a local Paperclip plugin for development?▼

Use `paperclipai plugin install` with an absolute local path; the CLI auto-detects local paths and forwards isLocalPath to the server. The server watches the plugin's dist/ output and restarts the worker on rebuild, so you do not reinstall after each edit.

Should Paperclip plugins live inside the Paperclip repository?▼

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 example lists and docs.

What are the current limitations of the Paperclip plugin runtime?▼

Plugin workers and UI run as trusted same-origin code, worker APIs are capability-gated, and plugin UI is not sandboxed by manifest capabilities. There is no host-provided shared UI component kit, and ctx.assets is not supported in the current runtime.

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.