paperclip-create-plugin

Scaffold Paperclip plugin packages aligned to the alpha SDK/runtime.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/mighty-hq/mighty-paperclip --skill paperclip-create-plugin-mighty-hq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paperclip-create-plugin
Source: https://github.com/mighty-hq/mighty-paperclip/tree/main/skills/paperclip-create-plugin
Command: npx skills add https://github.com/mighty-hq/mighty-paperclip --skill paperclip-create-plugin-mighty-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the guesswork and boilerplate involved in creating a new Paperclip plugin by guiding you through the current supported SDK/runtime shape, expected files, conventions, and verification steps.

Core Features & Use Cases

  • Plugin scaffolding guidance: Use the provided create/scaffold workflow to generate a plugin package aligned to the current alpha SDK/runtime.
  • Surface + convention checklist: Ensures you follow the supported worker/UI surface, route conventions (including when to use routePath), and capability declaration expectations.
  • Trusted-code model documentation: Helps you author or update plugin authoring docs without assuming future host UI component kits or unsupported APIs like ctx.assets.

Quick Start

Tell the AI to scaffold a new Paperclip plugin scaffold using the current alpha SDK/runtime, then verify it with typecheck, test, and build.

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 from scratch?

To scaffold a Paperclip plugin, use the provided create workflow to generate a package aligned to the current alpha SDK runtime, then update the manifest, worker, UI, and tests before verifying with typecheck, test, and build.

What files do I need to update when creating a Paperclip plugin?

Creating a Paperclip plugin requires updating the plugin manifest, worker scripts, UI surface, tests, and package.json to align with the expected route conventions and supported capability declarations.

When should I use routePath in a Paperclip plugin manifest?

You should use routePath when defining route conventions in your Paperclip plugin manifest to ensure discoverable in-app behavior and accurate UI surface mapping within the supported worker architecture.

Does the Paperclip plugin SDK support ctx.assets or custom host UI component kits?

No, the Paperclip plugin SDK operates on a trusted-code model and does not support unsupported APIs like ctx.assets or assume future host UI component kits, constraining you to currently supported capabilities.

How do I verify a newly scaffolded Paperclip plugin before publishing?

You verify a newly scaffolded Paperclip plugin by running typecheck, test, and build commands to ensure the package meets the current alpha SDK runtime requirements and passes all surface convention checks.