paperclip-create-plugin

Create and develop external Paperclip plugins with the CLI-first workflow. Use when scaffolding a plugin, iterating on a local plugin, installing it into Paperclip, or updating plugin authoring docs.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced plugin-authoring skill with executable commands and an explicit verification gate. Its only real weakness is progressive disclosure: it is a single self-contained file rather than a lean overview pointing to bundled reference materials.

Suggestions

Move the CLI flag reference (section 3) and/or the success checklist (section 7) into bundled files under ./references/ and link to them one level deep, keeping SKILL.md a leaner overview.

Add a short 'Quick start' pointer near the top that links to the scaffold + install loop so the core workflow is skimmable before the detailed sections.

Dimension	Reasoning	Score
Conciseness	Lean and operational throughout — no explanation of concepts Claude already knows; every section is concrete commands, flags, or terse runtime assumptions, so each token earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands and flags (paperclipai plugin init, pnpm dev, plugin install/list/inspect, typecheck/test/build) plus a concrete fallback path; not a 2 because nothing is pseudocode or abstract.	3 / 3
Workflow Clarity	Clear numbered sequence (sections 1–9) with an explicit verification gate ('run before declaring success') and a reporting checklist; validation feedback is present, so it is not capped at 2.	3 / 3
Progressive Disclosure	Well-organized into clear sections with one-level-deep repo-doc references, but all detail lives inline in a single ~150-line file and no bundle files exist; flag reference and success checklist could be split out. Not a 3 because content that could be separate is inline rather than appropriately split into bundled references.	2 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit what/when guidance, concrete enumerated actions, and a well-scoped Paperclip-plugin niche. Voice is appropriately imperative/third person with no over-claims or fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'scaffolding a plugin, iterating on a local plugin, installing it into Paperclip, or updating plugin authoring docs' — rather than vague language.	3 / 3
Completeness	Clearly answers both what ('Create and develop external Paperclip plugins with the CLI-first workflow') and when via an explicit 'Use when...' clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	Natural terms a user would say ('scaffolding a plugin', 'installing it into Paperclip', 'plugin authoring docs') are present with good coverage; not a 2 because common trigger phrasings are well represented.	3 / 3
Distinctiveness Conflict Risk	A clear niche (external Paperclip plugins) with distinct, niche-specific triggers makes conflict with other skills unlikely; not a 2 because it is not merely 'works with plugins'.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: paperclipai/paperclip
Path: .agents/skills/paperclip-create-plugin/SKILL.md
Commit: 81f47e7

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.