Collecting Worker Results

Inspect a stopped worker's returned work and evidence before accepting it, retrying it or handing it to an integration owner. Use when a worker finishes, records disagree, or a green result has no visible change. Collection does not authorize merging.

33 stars 4 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add okgrit/done-is-a-claim

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add okgrit/done-is-a-claim --skill collecting-worker-results
Manual install
git clone --depth 1 https://github.com/okgrit/done-is-a-claim.git /tmp/done-is-a-claim
mkdir -p ~/.claude/skills
cp -r /tmp/done-is-a-claim/skills/collecting-worker-results ~/.claude/skills/collecting-worker-results

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Collecting worker results

A worker stopping, delivering a change and satisfying a task are different
events. Reconcile the report, returned files and verification before deciding
what was delivered. These are operational checks, not incident statistics.

## Separate the records

| Observation | Supports | Does not establish |
|---|---|---|
| Process exit or runner status | The recorded process outcome | A delivered change or acceptance |
| Worker report | The worker's account of work and blockers | Independent verification |
| Commits, patches and working-tree diff | A change footprint against a named base | Correctness or integration |
| Acceptance record | The result on its recorded input tree | A pass on a different returned tree |
| Destination state | What reached the target revision or location | That it matches the tested work |

## Procedure

1. Confirm the run identity and that the worker stopped; a stale status or
   another process with the same name is insufficient. Collect only the
   assigned result. Resolve competing ownership before changing shared state.
2. Read the report and blockers, then inspect the returned base, tip, commits,
   tracked diff and untracked files. A clean tree with no new commits may mean
   no change, an already-delivered change or a patch elsewhere; investigate.
3. Compare the footprint with the task scope. A report-only return may satisfy
   a reporting task, but is not an implementation. Identify unrelated or stacked
Read the full skill on GitHub

Details

Skill name
collecting-worker-results
Path
skills/collecting-worker-results/SKILL.md
License
Apache-2.0
Repo updated
25 October 2026

FAQ

What does the Collecting Worker Results skill do?

Inspect a stopped worker's returned work and evidence before accepting it, retrying it or handing it to an integration owner. Use when a worker finishes, records disagree, or a green result has no visible change. Collection does not authorize merging.

How do I install the Collecting Worker Results skill?

Claude Code plugin: /plugin marketplace add okgrit/done-is-a-claim. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Collecting Worker Results popular?

It lives in okgrit/done-is-a-claim, which has 33 GitHub stars and 4 forks, and is included in 1 curated skill list.

Related skills

Acceptance Design

33

okgrit/done-is-a-claim

Define executable acceptance for a bounded task before work or dispatch. Use when writing a worker brief, selecting success checks, or repairing an acceptance contract that cannot test the intended outcome.

Testing & QAIn 1 list

Checking Delivery

33

okgrit/done-is-a-claim

Verify an artifact at its actual delivery destination and distinguish send attempts, acknowledgements, publication and consumer checks. Use when reporting a file, message, export or deployment as delivered; creating a local draft alone does not imply delivery.

DevOps & CloudIn 1 list

Debugging with Evidence

33

okgrit/done-is-a-claim

Diagnose unexpected behavior with a reproduction, competing explanations and experiments that separate them before fixing. Use for bugs, failed checks or repeated unsuccessful fixes; attribute branch failures only with suitable comparison evidence.

Software DevelopmentIn 1 list

Daily Brief

48

amplitude/mcp-marketplace

Delivers a daily briefing of the most important changes across your Amplitude instance. Use when the user asks for a "daily download", "morning briefing", "what's happening", "anything I should know", or wants a summary of recent metric changes, experiments, and user feedback.

Other12

Sketch Checker

38

sam-dumont/claude-skills

Use when the user asks to check if a band is sketch, fascist, NSBM, or far-right. Also trigger for: "is [band] sketch?", "is [band] safe?", "sketch check [band]", "check [band] for fascist ties", "is [band] NSBM?", "is [band] fash?", "should I listen to [band]?", "is [band] problematic?", "are [band] nazis?", "RABM check", "band vetting", "is it sketch", "sketch report", "any red flags for [band]", "does [band] have far-right connections", "sketch check", "vet this band", "is [band] safe to support".

Other

Evidence Freshness

33

okgrit/done-is-a-claim

Bind a check or action to the input snapshot it actually used. Use before relying on cached verification, consuming a reviewed batch, acting while inputs may change, or retrying an operation with an ambiguous result.

OtherIn 1 list

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.