- name
Compatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workf
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add paperclipai/paperclip --skill diagnose-why-work-stopped -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add paperclipai/paperclip --skill diagnose-why-work-stopped -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add paperclipai/paperclip --skill diagnose-why-work-stopped -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add paperclipai/paperclip --skill diagnose-why-work-stopped -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/paperclipai/paperclip/tree/HEAD/.agents/skills/diagnose-why-work-stoppedFrom the publisher
Use Fix Failed Paperclip Run. It owns the current workflow: find the first causal failure, reproduce it red, repair the shared contract, test second-order effects, verify the real workflow, and deliver a PR with passing checks. A normal request to fix stopped work continues through that workflow without a separate plan-approval gate.
If the user or calling workflow explicitly asks for diagnosis only or requires approval before implementation, perform the investigation and safety analysis within that scope. For example, a Terminal-Bench diagnosis child does not override the loop's board approval boundary. Keep the next action and its owner explicit.
For issue-tree diagnosis, inspect the relevant subtree and recent repairs, and classify non-progressing nodes:
Preserve these three invariants together:
Frame any repair as a general behavioral contract, check it against a productive counterexample, and follow the new skill through the authorized finish line. Historical task links and private incident access are not required.
© 2026 Skills Rack.
---name: diagnose-why-work-stoppeddescription: Compatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use…---# .agents/skills/diagnose-why-work-stopped/SKILL.mdOverview
Compatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.
FAQ
Download .agents/skills/diagnose-why-work-stopped/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/paperclipai/paperclip.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.