harvest
Skill1 starsChanged 4 months agoMITView on GitHub
Collect finished ollamaq jobs — read their compact digests, then run the Opus/Sonnet reduce/clean pass over only the residue the local model got wrong, and write the final artifact. Use after /offload jobs reach the "done" state.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- jsuchet/jonathan-skills-labtheir own version, first seen Nov 16, 2026
- mad01/thismoontheir own version, first seen Nov 15, 2026
- darkroomengineering/cc-settingstheir own version, first seen Nov 12, 2026
- zedarvates/frugal-skillstheir own version, first seen Nov 8, 2026
- yuri-xyz/skillstheir own version, first seen Nov 8, 2026
- egregore-labs/egregoretheir own version, first seen Nov 6, 2026
Used with
Projects with it also use handoff.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 4 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- huytieu/COG-second-brain★ 1.3ksame name
- egregore-labs/egregore★ 293same name
- darkroomengineering/cc-settings★ 53same name
- toustifer/dsh-harvest★ 10same name
- sergeeey/Claude-cod-top-2026★ 9same name
- aidvgg/operator-os★ 4same name
- FabianoArthur/claude-code-kitchen★ 4same name
- mad01/thismoon★ 2same name
- yuri-xyz/skills★ 2same name
- cwade12c/spicerack★ 1same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Clean pass (all good): if the digest shows high success and the samples look right, the local output is the deliverable.
- Very specific: line 29
Fix the residue: if the digest shows a systematic local error (e.g.
- Very specific: line 33
Per-row review (last resort): only read all of merged.jsonl into context when the task genuinely needs Claude to inspect every row.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/harvest — reduce and finalize offloaded work
The map phase already ran locally for $0. Harvest is where Claude tokens get spent — so spend them only on the residue, guided by each digest. See [CLAUDE.md] for the token-economy contract.
1. Find finished jobs
ollamaq status — shows counts per state and the ids in each. Note the ids in
done (and failed). For one job: ollamaq status <job_id>.
2. Read the digest FIRST (cheap)
ollamaq digest <job_id> — prints results/<job_id>/digest.md (≤ 8 KB): success
rate, sample outputs, the full list of failures, and the estimated cloud cost
avoided. This is usually all you need to decide what to do next. Do not read
merged.jsonl yet.
3. Decide the reduce strategy
- Clean pass (all good): if the digest shows high success and the samples
look right, the local output is the deliverable. Point the user at
results/<job_id>/merged.jsonl(anditems/). No token-heavy pass needed. - Fix the residue: if the digest shows a systematic local error (e.g. a
format the small model didn't follow) or lists failures, prefer a mechanical
fix — write a small script/transform that corrects that specific error across
merged.jsonl, and run it. This keeps the reduce at O(digest), not O(n). - Per-row review (last resort): only read all of
merged.jsonlinto context when the task genuinely needs Claude to inspect every row. This is the expensive path — say so, and confirm it's warranted. - Escalate failures: re-run just the
failed_items.jsonlitems as a new small job on a stronger local model, or handle them inline.
4. Write the final artifact
Produce the cleaned/aggregated output the user asked for (a file under their
project, not under results/). State plainly what you did: how many items came
from the local run untouched, how many you corrected and how, and how many
failed. Include the digest's "cost avoided" figure so the savings are visible.
5. gen_test / pipeline jobs
- gen_test: the digest is a scored leaderboard — the deliverable is the top candidate(s). Report the best and its score; no reduce pass usually needed.
- pipeline: the digest shows a stage funnel;
merged.jsonlholds each item at its final stage. Verify the funnel matches intent (right counts continued vs finalized) before finalizing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

