farm
Skill217 starsChanged 8 months agoMITView on GitHub
Manually trigger a context farmer subagent. Usage - /farm <name> (e.g., /farm slack)
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Shawn-Dong/skill-farmtheir own version, first seen Nov 8, 2026
- master-g/skillstheir own version, first seen Oct 10, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Shawn-Dong/skill-farm★ 1same name
- master-g/skills★ 0same name
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.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- create-farmerSkill
- daily-reviewSkill
- delegate-taskSkill
- historySkill
- newSkill
- start-second-brainSkill
- todaySkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Distinctive: line 9
Run a context farmer to pull information from an external source into the vault.
- Very specific: line 17
Validate argument: If $ARGUMENTS is empty, list available farmers by globbing .claude/agents/*-farmer.md and ask the user which one to run.
- Very specific: line 19
Validate farmer exists: Check that .claude/agents/$ARGUMENTS-farmer.md exists.
- Very specific: line 22
Use the agent name $ARGUMENTS-farmer
- Distinctive: line 25
Report results: After the farmer completes, summarize what was captured:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Farm
Run a context farmer to pull information from an external source into the vault.
Argument
$ARGUMENTS is the farmer name (e.g., slack).
Workflow
- Validate argument: If
$ARGUMENTSis empty, list available farmers by globbing.claude/agents/*-farmer.mdand ask the user which one to run. - Validate farmer exists: Check that
.claude/agents/$ARGUMENTS-farmer.mdexists. If not, list available farmers and report the error. - Run the farmer: Launch the farmer subagent using the Agent tool:
- Use the agent name
$ARGUMENTS-farmer - Prompt: "Execute your farming instructions now."
- Use the agent name
- Report results: After the farmer completes, summarize what was captured:
- Number of new files created
- Number of existing files updated
- List of entities with their types (task/project/person/idea)
- Any issues encountered
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.