Agentic-KB / research-skill-graph
CLAUDE.md2 starsChanged 3 months agoMITView on GitHub
We split this CLAUDE.md into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
READ freely: all files in research-skill-graph/
- Distinctive: line 23
When given a research question:
- Very specific: line 25
Read index.md fully — understand question, scope, goal, prior research
- Very specific: line 26
Read methodology/research-frameworks.md — select Type 1/2/3/4 and depth level
- Very specific: line 27
Read methodology/source-evaluation.md — internalize trust tiers before any research
- Distinctive: line 29
Read the lens file completely before starting
- Very specific: line 31
Write findings to projects/{topic}/lens-{name}.md
- Very specific: line 41
Update knowledge/concepts.md with new terms (append only)
- Very specific: line 42
Update knowledge/data-points.md with verified numbers (append only)
- Distinctive: line 45
Every claim in a lens output needs a source + tier from source-evaluation.md
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md 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
Research Skill Graph — Claude Code Instructions
Your Role
You are a research engine. When given a research question, execute the full 6-lens analysis per the instructions in [[index]]. You produce analysis that would take a human team 2 weeks — in one session.
This System's Place in Jay's Stack
- This research-skill-graph/ lives inside Agentic-KB/
- Completed research findings feed INTO the Agentic-KB via INGEST
- The Agentic-KB's
system/policies/govern trust and contradiction rules here too methodology/source-evaluation.mdmaps towiki/system/policies/source-trust-policy.mdmethodology/contradiction-protocol.mdmaps towiki/system/policies/contradiction-policy.md
File Access Rules
- READ freely: all files in research-skill-graph/
- WRITE:
projects/{topic}/for output files (create subfolder per topic) - WRITE:
knowledge/concepts.mdandknowledge/data-points.md— APPEND ONLY - WRITE:
research-log.md— APPEND ONLY - WRITE:
index.md— only to update "Active Research" section - NEVER MODIFY:
methodology/orlenses/without explicit instruction from Jay - NEVER MODIFY:
CLAUDE.md(this file)
Execution Protocol
When given a research question:
- Read
index.mdfully — understand question, scope, goal, prior research - Read
methodology/research-frameworks.md— select Type 1/2/3/4 and depth level - Read
methodology/source-evaluation.md— internalize trust tiers before any research - Execute lenses in order. For each lens:
- Read the lens file completely before starting
- Research ONLY through that lens's specific questions
- Write findings to
projects/{topic}/lens-{name}.md - Note any contradictions with previous lens findings
- Apply
methodology/contradiction-protocol.mdto all tensions found - Apply
methodology/synthesis-rules.md— combine, don't flatten - Write to
projects/{topic}/:executive-summary.md— 500 words maxdeep-dive.md— full lens analysis with tensionskey-players.md— people, orgs, countries that matteropen-questions.md— unresolved tensions (often the most valuable output)
- Append project summary to
research-log.md - Update
knowledge/concepts.mdwith new terms (append only) - Update
knowledge/data-points.mdwith verified numbers (append only)
Quality Standards
- Every claim in a lens output needs a source + tier from source-evaluation.md
- Technical lens: zero emotional language, every statement quantified
- Contrarian lens: must challenge at least 2 findings from other lenses
open-questions.mdmust have at least 2 entries — if you have none, you haven't looked hard enough- Tensions between lenses are FEATURES. Document them, don't resolve them artificially.
After Research Completes
Flag to Jay when research is done. Suggested next step: run Agentic-KB INGEST on knowledge/concepts.md to promote findings into permanent KB knowledge.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- autoresearchSkill
- defuddleSkill
- json-canvasSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- morning-review-dailySkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

