Paperclip Create Plugin

Community

IncomeStreamSurfer

paperclip-create-plugin

Create new Paperclip plugins with the current alpha SDK/runtime. Use when scaffolding a plugin package, adding a new example plugin, or updating plugin authoring docs. Covers the supported worker/UI surface, route conventions, scaffold flow, and verification steps.

Overview

Publisher	IncomeStreamSurfer
Repository	`paperclip-surfers`
Skill name	`paperclip-create-plugin`
Stars	74
Forks	32
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by IncomeStreamSurfer on GitHub. Read the source before you install it.

Installation

Install the Paperclip Create Plugin AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/IncomeStreamSurfer/paperclip-surfers/tree/master/skills/paperclip-create-plugin

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/IncomeStreamSurfer/paperclip-surfers.git /tmp/paperclip-surfers
mkdir -p .claude/skills
cp -r /tmp/paperclip-surfers/skills/paperclip-create-plugin .claude/skills/paperclip-create-plugin

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Paperclip Create Plugin in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Paperclip Create Plugin on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Paperclip Create Plugin is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Create a Paperclip Plugin

Use this skill when the task is to create, scaffold, or document a Paperclip plugin.

1. Ground rules

Read these first when needed:

doc/plugins/PLUGIN_AUTHORING_GUIDE.md
packages/plugins/sdk/README.md
doc/plugins/PLUGIN_SPEC.md only for future-looking context

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

2. Preferred workflow

Use the scaffold package instead of hand-writing the boilerplate:

bash
pnpm --filter @paperclipai/create-paperclip-plugin build
node packages/plugins/create-paperclip-plugin/dist/index.js <npm-package-name> --output <target-dir>

For a plugin that lives outside the Paperclip repo, pass --sdk-path and let the scaffold snapshot the local SDK/shared packages into .paperclip-sdk/:

bash
pnpm --filter @paperclipai/create-paperclip-plugin build
node packages/plugins/create-paperclip-plugin/dist/index.js @acme/plugin-name \
  --output /absolute/path/to/plugin-repos \
  --sdk-path /absolute/path/to/paperclip/packages/plugins/sdk

Recommended target inside this repo:

packages/plugins/examples/ for example plugins
another packages/plugins/<name>/ folder if it is becoming a real package

3. After scaffolding

Check and adjust:

src/manifest.ts
src/worker.ts
src/ui/index.tsx
tests/plugin.spec.ts
package.json

Make sure the plugin:

declares only supported capabilities
does not use ctx.assets
does not import host UI component stubs
keeps UI self-contained
uses routePath only on page slots
is installed into Paperclip from an absolute local path during development

4. If the plugin should appear in the app

For bundled example/discoverable behavior, update the relevant host wiring:

bundled example list in server/src/routes/plugins.ts
any docs that list in-repo examples

Only do this if the user wants the plugin surfaced as a bundled example.

5. Verification

Always run:

bash
pnpm --filter <plugin-package> typecheck
pnpm --filter <plugin-package> test
pnpm --filter <plugin-package> build

If you changed SDK/host/plugin runtime code too, also run broader repo checks as appropriate.

6. Documentation expectations

When authoring or updating plugin docs:

distinguish current implementation from future spec ideas
be explicit about the trusted-code model
do not promise host UI components or asset APIs
prefer npm-package deployment guidance over repo-local workflows for production

Frequently asked questions

What does the Paperclip Create Plugin AI skill do?

Why use Paperclip Create Plugin on TypingMind?

Because you install it once and use it with any model. Paperclip Create Plugin is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Paperclip Create Plugin in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/IncomeStreamSurfer/paperclip-surfers/tree/master/skills/paperclip-create-plugin. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Paperclip Create Plugin?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Paperclip Create Plugin?

As many as you like. As long as a model supports skills, you can use Paperclip Create Plugin with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Paperclip Create Plugin AI skill free?

Yes. It is published on GitHub by IncomeStreamSurfer under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Receiving Code Review

obra

CommunityPopular

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative…

Requesting Code Review

obra

CommunityPopular

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Systematic Debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Test Driven Development

obra

CommunityPopular

Use when implementing any feature or bugfix, before writing implementation code

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Create a Paperclip Plugin

1. Ground rules

2. Preferred workflow

3. After scaffolding

4. If the plugin should appear in the app

5. Verification

6. Documentation expectations

Frequently asked questions

Related AI Skills

Set up your own AI workspace now