agentleFS
rrrrrredyrrrrrredy/research-toolkit/agents/claude.md

research-toolkit / agents

CLAUDE.md314 starsChanged 54 days agoMITView on GitHub

English | 简体中文 With Git and the client ready, run from your project root. If the destination already exists, use the update guide. For a new installation, the agent runs the commands below with Python 3.10+. For an existing copy, configure recording only where missing or changed; reuse effective settings and plugin hooks, preserving off. Basic events are sent by default without prompts, research titles, conversations, reports or paths. Recording can be disabled; setup failure does not block direct use…

The file

We split this claude.md into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start Claude Code in this project and invoke /research-toolkit.

    line 16
  2. Distinctive:

    Use Claude Code’s native subagents for production, assembly, independent content review, audit and acceptance.

    line 33
  3. Distinctive:

    Run this from the same project directory:

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
claude.md

Claude Code: use the complete research methods

English | 简体中文

Install

With Git and the client ready, run from your project root. If the destination already exists, use the update guide.

For a new installation, the agent runs the commands below with Python 3.10+. For an existing copy, configure recording only where missing or changed; reuse effective settings and plugin hooks, preserving off. Basic events are sent by default without prompts, research titles, conversations, reports or paths. Recording can be disabled; setup failure does not block direct use of the research methods.

git clone --depth 1 -c core.longpaths=true https://github.com/rrrrrredy/research-toolkit.git .claude/skills/research-toolkit
python .claude/skills/research-toolkit/scripts/install_usage.py --host claude --project . --channel github-clone --form skill

Start Claude Code in this project and invoke /research-toolkit. Claude web chat and Cowork have different loading rules; use the file/text route there. Official skill requirements.

core.longpaths applies to this Git checkout and prevents long-path checkout failures on Windows.

Try it

Use research-toolkit.
Read .claude/skills/research-toolkit/SKILL.md.
Research question: [Question, audience and intended use.]
Scope and length: [Coverage, information cutoff and expected depth.]
Existing material: [Sources, files or an existing report.]
Load the complete methods as needed and develop the evidence, comparisons,
mechanisms and synthesis. Deliver the complete report with usable citations;
preserve sources and full analysis for handoff; organize independent review, audit and acceptance through Claude Code.

Use Claude Code’s native subagents for production, assembly, independent content review, audit and acceptance. They use Claude Code’s existing model access, without separate API configuration. Share current requirements and original materials, and retain full handoffs.

The shared research guide provides a complete request and setup details.

Agent execution adapter

For script-managed work, use the shared Agent execution adapter with --host claude. Native subagent tools also use the same work/save/review contracts. Both paths use Claude Code's login and model configuration.

The shared example describes dependencies, input updates, original records and independent review. Use one dispatcher for a work unit; do not launch it through native tools and the adapter at the same time.

If it does not load

Run this from the same project directory:

git -C .claude/skills/research-toolkit status --short

No output means the checkout is clean; a path error means the command is running from the wrong directory or the clone failed. Changes may indicate missing or edited files—preserve your edits before updating. If files exist but the skill is absent, reopen the project/session and check Claude Code’s skill settings. You can also ask the agent to read the installed SKILL.md by its exact path. All input methods and limits.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.