paperclip-create-plugin

Scaffold Paperclip plugin packages with worker/UI conventions and verification steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Paperclip plugin authors need a reliable way to scaffold, configure, and verify new plugins without manually wiring workers, UI, routes, and capabilities incorrectly.

Core Features & Use Cases

  • Plugin scaffolding guidance: Explains the recommended scaffold flow using the current alpha SDK/runtime and the official plugin authoring guides.
  • Surface and convention coverage: Covers the supported worker and UI expectations, route conventions, manifest/workers/UI file touchpoints, and capability model assumptions.
  • Post-scaffold verification and checks: Provides the exact typecheck, test, and build steps to ensure the plugin package is valid and adheres to runtime constraints.
  • Documentation expectations: Helps write plugin docs that clearly distinguish current behavior from future spec ideas and avoid promising unsupported host UI components or asset APIs.

Quick Start

Use this skill to scaffold a new Paperclip plugin package and then follow the recommended verification steps for typecheck, tests, 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 new Paperclip plugin package?

Scaffold a Paperclip plugin package by following the alpha SDK runtime workflow, which wires workers, UI surfaces, routes, and manifest capabilities automatically to avoid manual configuration errors.

What conventions must a Paperclip plugin manifest follow?

A Paperclip plugin manifest must follow supported worker and UI surface assumptions, route conventions, and capability model constraints defined by the alpha SDK runtime to ensure valid plugin verification.

What verification steps are required after scaffolding a Paperclip plugin?

Required verification steps after scaffolding a Paperclip plugin include running typecheck, tests, and build checks to ensure the package adheres to runtime constraints and is valid.

Can I use unsupported host UI components when authoring Paperclip plugin documentation?

Plugin documentation must avoid promising unsupported host UI components or asset APIs, clearly distinguishing current alpha SDK behavior from future spec ideas to prevent inaccurate capability claims.

Why does my Paperclip plugin fail typecheck after manual scaffolding?

Manual scaffolding often misconfigures worker, UI, route, and manifest touchpoints, causing typecheck failures; using the official scaffold flow ensures these file touchpoints match current alpha runtime expectations.