Skip to content

Verify Paperclip

Test a Paperclip install or stack through real UI and CLI journeys and capture evidence

Stars
110,078
Licence
MIT
Files
9 files

What it does

When installed, this gives an AI agent a structured procedure for checking whether the Paperclip project works. It helps the agent pick what to test (a source checkout, a published npm package, or a staging or production server), set up clean or reused data, drive the browser or command line through real user steps, and save evidence. It also includes helper scripts that start an isolated local Paperclip instance for first-run onboarding checks and then stop it safely.

Great for

  • Contributors to the Paperclip repository who need to verify a feature or fix before merging
  • Release testers checking that a published npm canary or stable package installs and onboards correctly
  • QA staff validating a staging deployment against a defined test account

Skip it if

  • Production systems without explicit authorization, because the skill is scoped to authorized targets and can drive real user journeys there
  • Someone without the Paperclip repository checked out, since the launch scripts expect the repo layout and installed dependencies
  • Checking agent runs with live model credentials through this path, because the empty-instance launcher deliberately runs without model credentials

Try asking

  • “Verify the onboarding wizard works on a fresh checkout of the current branch”
  • “Check that the latest npm canary installs and completes first-run onboarding”
  • “Run a feature journey against the staging stack and capture evidence”
  • “Stop the isolated verification instance I started earlier and confirm its database exited”
Step-by-step guide: how to use Verify PaperclipInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 9 original files, the MIT licence and an attribution note.

    verify-paperclip.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip verify-paperclip.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip verify-paperclip.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Use separate, empty data and evidence directories for every launch; the launcher refuses reused directories
  • Keep the launch command running in a foreground terminal, and use the doctor and stop scripts to confirm the instance is the one you started
  • Report exactly which combination was tested (for example, a source build does not prove the npm package), since the skill itself warns against overstating coverage

What's inside

  • references/hosted-qa-accounts.md
  • references/npm-install.md
  • references/verification-targets.md
  • scripts/doctor.py
  • scripts/launch.py
  • scripts/onboarding-smoke.mjs
  • scripts/stop.py
  • SKILL.md
  • tests/test_ownership.py

Redistributed unmodified from paperclipai/paperclip under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.