# Verify Paperclip Install

Drives real UI or CLI journeys against a checkout, npm install or staging stack.

- Repository: https://github.com/paperclipai/paperclip (109885 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add paperclipai/paperclip --skill verify-paperclip -g -a claude-code -y`
Codex: `npx skills add paperclipai/paperclip --skill verify-paperclip -g -a codex -y`
Cursor: `npx skills add paperclipai/paperclip --skill verify-paperclip -g -a cursor -y`
Gemini CLI: `npx skills add paperclipai/paperclip --skill verify-paperclip -g -a gemini-cli -y`

## Description

Verify Paperclip from a source checkout, published npm install, or existing staging or production stack. Select the environment, data state, version, and platform; drive real UI or CLI journeys and capture evidence. Route deployment to the private Cloud skills.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Verify Paperclip

Read the [map contract](../../../maps/README.md), then use the
[feature map](../../../maps/feature-map/README.md) to select user verification
recipes. For API/agent access, read the same-named
[agent access companion](../../../maps/agent-access-map/README.md) and use the
actual permitted agent identity, target and work mode. Follow existing API/runner/MCP
fixtures for access proof; a board request does not prove agent access. Report
recipe or access drift with evidence; map updates belong to
[maintain-verification-skill](../maintain-verification-skill/SKILL.md).
Read [development instructions](../../../doc/DEVELOPING.md) for current commands.

## Select the verification target

State what is being tested before starting. Use the requested target; for ordinary
feature development, default to the current checkout on the current host with
isolated data. Expand into cross-platform or release qualification only when
requested or needed to reproduce the problem.

Record these independent dimensions together:

- **Artifact:** source checkout (path, commit, dirty state), published npm package
  (requested channel and resolved exact version), or deployed image/release.
- **Environment:** local, staging, or production; target URL and intended company
  or workspace; board/user/agent identity and authentication mode.
- **Starting data:** fresh and unonboarded, freshly seeded, cloned, or reused;
  embedded versus external PostgreSQL; configuration/data location or a redacted
  database identifier. Never record credentials or connection strings.
- **Platform:** server OS/architecture, Node/npm versions, and browser/client OS
  when relevant. A Mac browser against a Linux server is Linux server evidence;
  WSL is Linux evidence, not native Windows evidence.
- **Journey:** first installation/onboarding, an existing-user feature, upgrade,
  or a live agent run; expected outcome and real versus simulated dependencies.

The rest: https://github.com/paperclipai/paperclip/blob/HEAD/.agents/skills/verify-paperclip/SKILL.md