SKILLEMALL.ai
GitHub ↗ RU Sign in

CC verify-paperclip

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.

The skillemall take

The skill promises to verify Paperclip across environments and versions, capture test evidence, and route deployments. Eight files, five scripts, but half don't run: doctor.py, launch.py, and stop.py fail with missing arguments that the skill doesn't provide. Code quality scores 67, process score 55. Broken references suggest incomplete integration. No critical errors, but the skill can't perform real verification—scripts fail silently.

Don't install it. The tool needs fixing: either pass required parameters or generate them automatically. Right now it's a skeleton that breaks on its own tests.

paperclipai/paperclip Agent Skills author: paperclipai MIT 8 files · 5 scripts body ≈ 3 549 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Verify Paperclip from a source checkout, published npm install, or existing staging or production stack.

As a process C 55/100 · Has gaps — References files that are not bundled: ../../../maps/README.md, ../../../maps/feature-map/README.md, ../../../maps/agent-access-map/README.md

AnalyzerPlaywrightPostgreSQLCommerceInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
C
55/100
Has gaps
References files that are not bundled: ../../../maps/README.md, ../../../maps/feature-map/README.md, ../../../maps/agent-access-map/README.md
Tools and files w 18
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: ../../../maps/README.md
  • warning missing-ref reference to a missing file: ../../../maps/feature-map/README.md
  • warning missing-ref reference to a missing file: ../../../maps/agent-access-map/README.md
  • warning missing-ref reference to a missing file: ../maintain-verification-skill/SKILL.md
  • warning missing-ref reference to a missing file: ../../../doc/DEVELOPING.md
  • warning missing-ref reference to a missing file: ../release/SKILL.md
  • warning missing-ref reference to a missing file: ../../../doc/DEVELOPING.md
  • warning missing-ref reference to a missing file: ../paperclip-dev-workspace-run-verify-fix/SKILL.md
  • warning missing-ref reference to a missing file: ../../../doc/AGENT-ARTIFACTS.md

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: ../../../maps/README.md, ../../../maps/feature-map/README.md, ../../../maps/agent-access-map/README.md
  • 0Tools and files. 9 referenced file(s) missing: ../../../maps/README.md, ../../../maps/feature-map/README.md, ../../../maps/agent-access-map/README.md
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 31 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 7 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3549 tokens
  • high The skill tells the model to perform an irreversible action with no human approval

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 261: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 7 items
  • +4Has examples (5 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +3All 4 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.

In the sandbox The scripts kept to themselves

The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.

Запущено 4 скрипта; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.

Из них 3 не дошли до работы, и об их поведении мы ничего не узнали.

scripts/doctor.pyне запустился: doctor.py: error: the following arguments are required: --evidence-dir
scripts/launch.pyне запустился: launch.py: error: the following arguments are required: --data-dir, --evidence-dir
scripts/onboarding-smoke.mjsничего за пределами своей папки
scripts/stop.pyне запустился: stop.py: error: the following arguments are required: --evidence-dir

16 Oct 2026