research
Skill137 starsChanged 4 months agoMITView on GitHub
Investigate a question against high-trust primary sources and capture the findings as a cited Markdown file. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated.
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 165 edited versions we read keep these.
2
Distinctive
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 6
If your environment supports background subagents, spin one up to do the research so you keep working while it reads.
- Distinctive: line 11
Write the findings to a single Markdown file, citing each claim's source.
“Common” is measured: kept by at least 6 in 10 of the 165 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
If your environment supports background subagents, spin one up to do the research so you keep working while it reads. Otherwise, do the research yourself in this session.
The job:
- Investigate the question against primary sources — official docs, source code, specs, first-party APIs — not a secondary write-up of them. Follow every claim back to the source that owns it.
- Write the findings to a single Markdown file, citing each claim's source.
- Save it where the repo already keeps such notes; match the existing convention. If there is no convention, save to
.plan/research/<slug>.mdand say where.
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 51
- mattpocock/skills★ 309k66% same
- QuivrHQ/quivr★ 40k70% same
- ArcReel/ArcReel★ 6k70% same
- withcoral/coral★ 4.9k70% same
- bestofjs/bestofjs★ 3.1k70% same
- CelestoAI/SmolVM★ 1.1k62% same
- moeru-ai/xsai★ 66470% same
- aws/graph-explorer★ 48970% same
- biersoeckli/QuickStack★ 36170% same
- itsmylife44/cliproxyapi-dashboard★ 28170% same
41 more not listed
Wrote their own version · 136
- Yeachan-Heo/oh-my-claude-sisyphus★ 40ksame name
- Yeachan-Heo/oh-my-claudecode★ 40ksame name
- udecode/plate★ 17ksame name
- openai/plugins★ 7.4ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- docker/docs★ 4.7ksame name
- thinking-machines-lab/tinker-cookbook★ 4.2ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
126 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.
Used alongsideProjects with it also use daily-arxiv, exp-eval and 10 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.
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文，过滤相关性，auto-ingest 高优先级论文，检测 SOTA 更新
Also in 5 projects that use this
- LambenthanSkill
exp-eval
实验判决门：Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
truongtv22SkillProblem-Solving Techniques
Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.
Also in 5 projects that use this
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 33 projects that use this
parcadeiSkillast-grep-find
AST-based code search and refactoring via ast-grep MCP
Also in 4 projects that use this
- parcadeiSkill
debug-hooks
Systematic hook debugging workflow. Use when hooks aren't firing, producing wrong output, or behaving unexpectedly.
Also in 4 projects that use this
- +5 more from Lambenthan
In this repository13 other files it gives its agents.
- verifySkill
- domain-modelingSkill
- grill-meSkill
- codebase-designSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- review-codeSkill
- to-specSkill
- to-ticketsSkill
- writing-great-skillsSkill
- prototypeSkill
- wayfinder-mapsSkill
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.