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

90%

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

88%Weight 40%Scale 1-5

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-structured body with copy-paste-ready commands, explicit validation checkpoints, and a reporting checklist. Remaining improvement room is in removing the duplicated out-of-repo guardrail and moving flag/runtime-constants detail into a reference file.

Suggestions

Merge the duplicated guardrail: section 8 ("When NOT to edit Paperclip core") repeats section 1's "do not add plugin source under packages/plugins/" rule — state it once and cross-reference from the other section.

Move the CLI flag list (section 3) and the runtime-assumptions list (section 2) into a references/ file (e.g. references/cli-flags.md), keeping SKILL.md to the workflow overview with a one-level-deep pointer.

Tighten the sanity-check checklist in section 5 by folding the "make sure the plugin" rules into the per-file checks so each constraint appears once.

Dimension	Reasoning	Score
Conciseness	The body is dense and imperative with no concept explanations, but the out-of-repo guardrail ("do not add plugin source under packages/plugins/") is stated in both sections 1 and 8, and the runtime-assumptions list duplicates spec constraints — minor instances that could be trimmed rather than every token earning its place.	4 / 5
Actionability	Fully executable throughout: copy-paste-ready commands ("paperclipai plugin init @acme/my-plugin --output ~/dev/paperclip-plugins", the node fallback invocation, "pnpm install / pnpm dev", "paperclipai plugin install"), a documented flag list, and concrete verification commands (pnpm typecheck/test/build) cover the common cases.	5 / 5
Workflow Clarity	A clearly sequenced scaffold → install → rebuild-loop → sanity-check → verify → report workflow with explicit validation (section 6 "run before declaring success"), error feedback (report lastError and reload limitations in section 7), and a final reporting checklist — matching the top anchor including feedback loops and checklists.	5 / 5
Progressive Disclosure	Nine well-ordered sections with clearly signaled one-level-deep references ("doc/plugins/PLUGIN_AUTHORING_GUIDE.md", "packages/plugins/sdk/README.md") and no bundle files to misplace; however, at ~150 lines the flag reference and runtime-assumptions list are candidates for a separate reference file, leaving minor organization gaps rather than an ideal split.	4 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

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: concrete domain-specific actions, an explicit 'Use when' trigger clause, and a distinct niche with low conflict risk. The only gap is modest keyword variation coverage.

Dimension	Reasoning	Score
Specificity	"Create and develop external Paperclip plugins with the CLI-first workflow" plus "scaffolding a plugin, iterating on a local plugin, installing it into Paperclip, or updating plugin authoring docs" lists multiple specific concrete actions covering the skill's full range, matching the comprehensive-coverage anchor rather than the minor-gaps anchor below it.	5 / 5
Completeness	It explicitly answers both what ("Create and develop external Paperclip plugins with the CLI-first workflow") and when ("Use when scaffolding a plugin, iterating on a local plugin, installing it into Paperclip, or updating plugin authoring docs") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural phrases like "scaffolding a plugin" and "installing it into Paperclip" are present, but common variations such as "build a plugin", "plugin development", or "add a plugin" are missing — good coverage with a few natural terms absent rather than comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	"Paperclip plugins" is a clear niche with distinct, product-specific triggers; there is minimal risk of this description firing for an unrelated skill.	5 / 5
	Total	19 / 20 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: 1c07b59

Reviewed: 1 day 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.