Agent skill · software engineering · paperclipai
garden-inbox
Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections. Use when asked to garden, clean up, prune, or tidy a Paperclip inbox without changing issues, branches, or workspaces.
Why this skill is useful
Adds a complete executable script for managing inbox archiving in Paperclip, including API interactions and user confirmations.
What it needs
Requires node installed locally. Requires paperclip account access. About 2k tokens when loaded. Last updated 2026-08-07. 75,771 stars on the source repository.
What this skill does
Garden Inbox Use the bundled script for every stage. Keep the workflow strictly ordered: scan → confirm → apply. Safety contract Treat scan as read-only. It may read inbox, workspace, close-readiness, and local Git metadata only. Treat confirm as a confirmation-card write only. It must not archive inbox entries or mutate issue fields, branches, or workspaces. Run apply only after a resolved requestcheckboxconfirmation interaction. It archives only accepted option IDs that also occur in the originating candidates.json. Remember that inbox archive state is per-user presentation state. It is reversible and does not change the underlying issue. Never substitute issue status changes, branch deletion, workspace cleanup, or issue deletion for inbox archiving. Inputs Require PAPERCLIPAPIURL and PAPERCLIPAPIKEY. The script strips a trailing /api from the URL. It resolves the target user from the run JWT payload's responsibleuserid; use --user-id <uuid> only for an explicit target override. Use a run-owned output directory when available: 1. Scan Inspect garden-inbox-report.md and candidates.json. The report groups every inbox row into exactly one bucket: The scan reads Mine separately for each included issue status so the endpoint's global 500-row cap does not silently omit older rows. If any single-status query reaches that cap, both outputs mark coverage as possibly truncated; do not treat that scan as complete. A: merged/archived workspace and all linked work terminal; selected by default. B: terminal or workspace-gone work idle beyond the threshold; selected by default. C: stale work with commits ahead of base; never selected by default. D: keep; never offered for archiving. Do not manually promote bucket D entries into the candidate file. 2. Confirm Post checkbox interactions on the driving issue: The script posts sequential cards when a scan has more than 200 candidates. Re-running confirm with the same scan file is idempotent. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills paperclipai/garden-inbox