big-research-setup
Skill13 starsChanged 23 days agoMITView on GitHub
Set up Big-Research, diagnose local prerequisites, choose a research home, or guide a researcher through a first saved project.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- HaoYangJin/Big-Researchword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- HaoYangJin/Big-Research★ 13100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository6 other files it gives its agents.
- big-research-analysisSkill
- big-research-designSkill
- big-research-reviewSkill
- big-research-scoutSkill
- big-researchSkill
- big-research-writingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Only Latest is installed. Migrate pre-v2 data into a new directory.
≈ “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
Start a research workspace
Explain the mission briefly, then help produce a first useful result. Identify the goal, available materials and desired project location only when not already known.
The full local plugin needs uv and Python 3.11+; uv can provision compatible Python. MCP Apps UI support is optional. Search and inference come from the user's client; no model API key or Connected App is required by this plugin.
Resolve PLUGIN_ROOT from this skill's installed location: two parents above its containing skill folder. Run uv run --isolated --frozen --no-dev --project PLUGIN_ROOT big-research doctor and inspect actual MCP tools. Never invent an installation path.
The MCP research home defaults to ~/Big-Research. Configure BIG_RESEARCH_HOME in the client's MCP environment for another directory. Project names are relative to this home. CLI operations accept explicit paths for projects elsewhere. Do not scan arbitrary directories.
Offer guided or concise explanation. Select methods by paradigm and question, not discipline alone. Create persistent work only in an empty destination. Show its research map and deliver an actual first artifact or bounded plan. Without MCP, use the identical current CLI; without execution/storage, disclose that persistence is unavailable.
Only Latest is installed. Migrate pre-v2 data into a new directory; never run old Skills or executors. If an independently installed old skill remains in the user's client, explain how to remove that exact duplicate after preserving their data; do not delete unrelated skills.
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.

