paper-cuts
Installation
SKILL.md
Paper cuts
A paper cut is friction you hit along the way that sits outside the task. The user decides what happens to each one; your job is to notice it, look a little, and report it.
Kinds
- Library: a bug, missing feature, awkward API, wrong docs, or unhelpful error in a dependency, framework, CLI, or service we use, the user's own libraries included.
- Machine: the machine behaved in a way you didn't expect: a missing binary, a wrong version, a permission, a full disk, a killed process, a busy port, stale config.
- Blocked: something you wanted to do and couldn't: a denied tool call, a missing credential or integration, an unreachable host, a sandbox limit.
When you hit one, work around it if you can, note it, and carry on with the task. The fix, the issue, or the config change waits for the user's call.
Look a little
Spend a few lookups per cut, enough to fill its card:
- Library: the installed version from the lockfile, a search of the upstream issues, and the changelog or releases since that version.
- Machine: the command and its output, the likely cause, and whether the machine's notes already cover it.
- Blocked: the exact error or denial, and what would unblock it: a permission, an integration, a machine change.