lint
Skill0 starsChanged 8 days agoMITView on GitHub
Health-check the second brain. Run the mechanical linter (scripts/lint.py), add a semantic review (contradictions, uncited claims, merge candidates, questions to explore), and save a ranked report to 50-outputs/lint/. Report-only, it never fixes anything. Use when the owner says "lint", "check vault health", "audit the wiki", "what's broken", or for the weekly/monthly maintenance pass.
82 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/coreai-design-systemtheir own version, first seen Nov 15, 2026
- wikilayer/skillstheir own version, first seen Nov 13, 2026
- playingpossumm/loose-endstheir own version, first seen Nov 10, 2026
- HurricaHjz/second-yourselftheir own version, first seen Nov 9, 2026
- PMDevSolutions/Flaviantheir own version, first seen Nov 8, 2026
- aiagentkit-labs/agentic-dev-kittheir own version, first seen Nov 8, 2026
Used with
Projects with it also use coverage, save and 6 more.
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.
PydanticSkillcoverage
Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.
Also in 4 projects that use this
seongjaeryuSkillsave
Complete and save your current thinking to Bindly
Also in 5 projects that use this
GitHubSkillstate-management
CoreAI Sandbox's TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app/hooks/use*.ts`), adding mock data in `app/data/`, or wiring a component to query state.
Also in 3 projects that use this
AWSSkillissue
Implement a GitHub issue end-to-end — branch, code, test, docs, and commit.
Also in 4 projects that use this
AnthropicSkilldigest
Generate a daily or weekly digest of activity across all connected sources. Use when catching up after time away, starting the day and wanting a summary of mentions and action items, or reviewing a week's decisions and document updates grouped by project.
Also in 3 projects that use this
agenticnotetakingSkillupgrade
Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".
Also in 3 projects that use this
Other versions82 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 82
- ray-project/ray★ 44ksame name
- FalkorDB/FalkorDB★ 11ksame name
- FastLED/FastLED★ 7.5ksame name
- fleetdm/fleet★ 7.2ksame name
- aaddrick/claude-desktop-debian★ 5.5ksame name
- cloudposse/atmos★ 1.4ksame name
- ethereum/execution-specs★ 1.2ksame name
- adobe/S3Mock★ 1.2ksame name
- maxGraph/maxGraph★ 1.2ksame name
- jason-effi-lab/karpathy-llm-wiki-vault★ 718same name
72 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.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brain-reviewSkill
- captureSkill
- gap-finderSkill
- ingestSkill
- projectSkill
- querySkill
- repairSkill
- second-brainSkill
- setupSkill
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 68 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.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Don't re-check by hand what the script covers.
- Very specific: line 43
Never "fix" 10-raw/ issues by editing raw files.
“Common” is measured: kept by at least 6 in 10 of the 68 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
Lint: health check (report only)
Never fix anything during lint. Repair is a separate decision (the repair skill).
1. Mechanical pass
scripts/qmd-sync.sh --wait # fresh search index for the semantic pass (no-op without qmd)
python3 scripts/lint.py --writeThis saves 50-outputs/lint/YYYY-MM-DD-lint.md with errors, warnings, and notes: broken links, frontmatter,
index coverage, orphans, one-way links, duplicates, stale seeds/state/inbox, and raw-modified (git).
Don't re-check by hand what the script covers. If the script fails to run, report that first.
2. Semantic pass
Fill the report's ## Semantic review (agent) section. Don't read every page: sample smartly.
- Contradictions: pages on overlapping topics (shared links/tags) that state different facts with no
## Contradictionssection. Check pages updated recently against their neighbours. - Uncited claims: specific numbers, dates, quotes without a nearby
[[source]]. Spot-check ~10 pages, prioritizingstablepages and the most-linked hubs. - Lost caveats: compare 2-3 recently ingested source pages with their raw files. Did hedges survive?
- Scatter: several pages covering one topic (merge candidates). With qmd, run a
vec:query per hub page title and look for near-duplicate hits in-c wiki; bloat: one page covering many (split candidates). - Superseded state: newer sources that changed a fact while other pages still describe the old one.
- Missing pages: people/concepts mentioned on 3+ pages without their own page.
- Next questions & sources: 3-5 questions the wiki can almost answer, plus the source that would close each gap.
3. Rank
Finish the report with ## Recommended order: the top 5-10 fixes, ordered by what they unblock
(errors that break navigation first, then contradictions, then hygiene). Number them so the owner can say
"fix 1-3".
4. Log and report
- Append to
log.md:## [YYYY-MM-DD] lint | N errors, M warnings+- report: 50-outputs/lint/YYYY-MM-DD-lint.md. - Tell the owner the headline counts, the top 3 recommended fixes, and "say fix 1-3 to repair".
Hard constraints
- Report only: no edits outside
50-outputs/lint/andlog.md. - Never "fix"
10-raw/issues by editing raw files. Araw-modifiedfinding means restore from git (owner decides).
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.

