add-language
Skill1 starsChanged 4 months agoLicence not identifiedView on GitHub
Use for any work on how deeply fathom understands a programming language or file format. That covers adding a dialect (tree-sitter tags.scm or a doc engine), pinning or re-pinning a grammar, building support for a format such as justfiles or systemd units, measuring or regrading a reading against an oracle (ctags, a SCIP indexer, the tool's own evaluation), explaining why a language sits below its target level (L1 to L4) or was refused (parse errors over the 5% line), choosing the next item from the language-breadth queue, and flipping an LB-Q plan row. Trigger whenever someone in the fathom repository asks to support, add, finish, fix, re-pin or measure a language or format, or asks why one is below target or refused, even if they never say "dialect" or "skill". Not for using fathom on another repository, fathom's MCP tools, or the daemon's memory.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Locker-Room-Tools/synapsetheir own version, first seen Oct 11, 2026
- DailybotHQ/deepworkplan-websitetheir own version, first seen Oct 9, 2026
- madeinoz67/madeinoz-knowledge-systemtheir own version, first seen Jan 18, 2026
- ZoneMinder/zmNinjaNgtheir own version, first seen Jan 10, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- ZoneMinder/zmNinjaNg★ 101same name
- DailybotHQ/deepworkplan-website★ 15same name
- madeinoz67/madeinoz-knowledge-system★ 3same name
- Locker-Room-Tools/synapse★ 2same 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- internal/AGENTS.mdAGENTS.md
- schema/AGENTS.mdAGENTS.md
- fathom-activateSkill
- fathom-custodianSkill
- fathom-doctorSkill
- fathom-feedbackSkill
- fathom-findingsSkill
- fathom-impactSkill
- fathom-offloadSkill
- fathom-onboardSkill
- fathom-planSkill
- fathom-rewireSkill
- fathom-verifySkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 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.
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.