paperclip-create-plugin

Scaffold Paperclip plugin packages with manifest, worker, UI, and test files.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill paperclip-create-plugin-kmshihab7878
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paperclip-create-plugin
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/paperclip-create-plugin
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill paperclip-create-plugin-kmshihab7878

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rapidly creating and validating Paperclip plugin packages is error prone and involves boilerplate, runtime conventions, and verification steps that are easy to miss. This Skill provides a deterministic scaffold and a checklist of runtime assumptions and verification steps so engineers can produce compliant plugins consistently.

Core Features & Use Cases

  • Scaffold Generation: Use the create-paperclip-plugin scaffold to generate package layout, manifest, worker, UI, tests, and package.json with recommended defaults.
  • SDK Snapshotting: Support for snapshotting a local SDK into a .paperclip-sdk folder for plugins developed outside the monorepo.
  • Conventions & Verification: Guidance on manifest fields, allowed capabilities, route and slot usage, prohibited runtime APIs (for example, no ctx.assets), and a verification flow requiring typecheck, test, and build.
  • Use Cases: Adding an example plugin to packages/plugins/examples, onboarding a third-party plugin repository, or updating plugin authoring documentation and examples.

Quick Start

Scaffold a new Paperclip plugin named @acme/plugin-name into /absolute/path/to/plugin-repos using the create-paperclip-plugin scaffold and prepare manifest, worker, UI, and tests for verification.

Frequently Asked Questions about paperclip-create-plugin

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

FAQPage Schema
How do I scaffold a Paperclip plugin with the correct manifest and worker files?

Scaffolding a Paperclip plugin generates the package layout, manifest, worker, UI, tests, and package.json with recommended defaults. You provide the plugin name and target repository path to produce a compliant package structure ready for verification.

What runtime conventions and API limitations must a Paperclip plugin manifest follow?

Paperclip plugin manifests must adhere to capability constraints, route and slot rules, and prohibit specific runtime APIs like ctx.assets. Following these conventions ensures the plugin operates safely within the runtime environment without violating boundary restrictions.

Can I develop and package a Paperclip plugin outside of a monorepo?

Developing a Paperclip plugin outside the monorepo requires snapshotting a local SDK into a .paperclip-sdk folder. This provides the necessary local dependencies for external plugin repositories before packaging into a local path.

What verification steps are required when building a Paperclip plugin?

Building a Paperclip plugin requires running typecheck, test, and build verification steps. This deterministic verification flow ensures the scaffolded plugin meets all runtime and manifest conventions before deployment.

Why does my Paperclip plugin scaffold fail verification during the build process?

Plugin verification fails when scaffolded files violate manifest conventions, bypass capability constraints, or use prohibited APIs like ctx.assets. Running the required typecheck, test, and build sequence identifies which runtime assumptions were not satisfied.

Does the Paperclip plugin scaffold support adding example plugins to an existing repository?

The Paperclip plugin scaffold supports adding example plugins to packages/plugins/examples within a monorepo. It generates the required manifest, worker, UI, test, and packaging files to onboard third-party plugin repositories or update authoring documentation.