corpus-sweep
Skill2 starsChanged 8 months agoApache-2.0View on GitHub
Orchestrates a large-corpus scouting pass (≥20 docs) using batched reads and compressed return. USE FOR: scanning research/, docs/, agent fleet for cross-cutting patterns before a synthesis phase; producing a compressed ≤2000-token findings summary. DO NOT USE FOR: single-doc reads; live web fetches (use source-caching skill instead).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nubjs/nubtheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nubjs/nub★ 4.4ksame 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 repository27 other files it gives its agents.
- adopt-test-2/AGENTS.mdAGENTS.md
- adopt-test-3/AGENTS.mdAGENTS.md
- adopt-test/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- {{cookiecutter.project_slug}}/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- .github/agents/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-file-authoringSkill
- conventional-commitSkill
- deep-research-sprintSkill
- delegation-routingSkill
- phase-gate-sequenceSkill
- prompt-archaeologySkill
- pr-review-replySkill
- pr-review-triageSkill
- rate-limit-resilienceSkill
- research-epic-planningSkill
- secondary-research-sprintSkill
- session-managementSkill
- session-retrospectiveSkill
- skill-authoringSkill
- source-cachingSkill
- sprint-planningSkill
- transcript-extractionSkill
- validate-before-commitSkill
- workplan-scaffoldSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Do not use this skill for:
- Very specific: line 47
Use read_file (for long docs) or grep_search (for keyword scanning).
- Distinctive: line 49
Stop scanning a document once sufficient signal is found — avoid reading full content when a heading scan suffices.
- Distinctive: line 56
Write incrementally after each batch.
- Very specific: line 89
If compression is truly unavoidable, note [truncated — N docs omitted] at the end.
≈ “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
Corpus Sweep
Governing Axiom
This skill enacts the Endogenous-First axiom from MANIFESTO.md and is governed by AGENTS.md § Programmatic-First Principle. Before sweeping any corpus, check whether a prior sweep result is already cached in .cache/sources/ or recorded in the active session scratchpad — re-sweeping a cached corpus wastes tokens and violates Local Compute-First.
"Scaffold from existing system knowledge and external best practices." — MANIFESTO.md § 1 Endogenous-First
When to Use
- A synthesis or implementation phase requires patterns found across ≥20 source documents.
- The Orchestrator needs a cross-cutting summary before delegating to a Synthesizer.
- A research epic requires an initial landscape report before forming hypotheses.
- You are auditing agent files, research docs, or session scratchpads for a recurring pattern.
Do not use this skill for:
- Single-document reads (use
read_filedirectly). - Live web fetches (use the
source-cachingskill instead). - Tasks where the required context fits within a single
grep_searchorsemantic_searchcall.
Workflow
- Pre-warm cache — before reading any source file, run:
Skip ifuv run python scripts/fetch_all_sources.py.cache/sources/manifest.jsonwas updated within the current session. - Read source index — identify the target corpus:
- For research sources: read
.cache/sources/manifest.jsonto list all cached URLs. - For internal docs: list
docs/research/,docs/guides/, or.github/agents/as appropriate. - Record the total document count before batching.
- For research sources: read
- Batch-read docs — divide the corpus into batches of 5–10 files. For each batch:
- Use
read_file(for long docs) orgrep_search(for keyword scanning). - Record findings per document: filename, key claim, relevant quote (≤50 words), and cross-references noted.
- Stop scanning a document once sufficient signal is found — avoid reading full content when a heading scan suffices.
- Use
- Record findings — append findings to the active session scratchpad under
## Corpus Sweep Output:
Write incrementally after each batch; do not accumulate all findings in memory before writing.## Corpus Sweep Output - <filename>: <key claim> — "<quote>" - Compress and return — after all batches complete, produce a ≤2000-token compressed summary and return it to the Orchestrator. Follow the compression rules in
AGENTS.md§ Focus-on-Descent / Compression-on-Ascent.
Output Format
Return only the compressed summary — no preamble, no prose framing. Use this structure:
Corpus: <name> — <N> docs scanned
Keywords: <keyword list>
Findings:
- <doc-name>: <one-line finding>
- …
Patterns:
- <cross-cutting pattern 1>
- <cross-cutting pattern 2>
Gaps:
- <topic with no coverage>
Token count: ~<estimate>Maximum return: ≤2000 tokens. If findings exceed this, compress by:
- Dropping per-document lines with no cross-cutting signal.
- Merging duplicate findings into a single pattern entry.
- Omitting gaps that are not actionable for the current phase.
If compression is truly unavoidable, note [truncated — N docs omitted] at the end.
Example Invocation
@corpus-sweep Sweep docs/research/ for "values encoding" patterns across all synthesis docs.
Return: compressed summary, ≤2000 tokens, bullets only.Expected output shape:
Corpus: docs/research/ — 23 docs scanned
Keywords: values encoding, encoding fidelity, signal loss
Findings:
- values-encoding.md: cross-reference density proxy for encoding fidelity
- agent-taxonomy.md: POSTURE-mapped toolsets reduce drift at T3 static layer
- bubble-substrate-model.md: membrane permeability spec governs Scout→Synthesizer handoff
Patterns:
- Encoding loss is highest at session-prompt layer (T4)
- Cross-reference density (back-links per 1000 words) is the primary fidelity metric
Gaps:
- No synthesis covering T4 runtime governor effectiveness data
Token count: ~320Does 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.

