research
Skill0 starsChanged 6 months agoMITView on GitHub
Use this skill when performing research tasks — codebase analysis, web research, documentation gathering, technology evaluation, or library comparison. Triggers: 'research', 'investigate', 'explore', 'find out', 'compare options', 'what are best practices for', 'look into'. Provides structured research patterns for both codebase and external research.
189 other projects use a version of this.
Adopted by
Most recently taken up by
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- Suge8/friedbuntheir own version, first seen Nov 15, 2026
- Fractera/Agent-Engineering-Infrastructuretheir own version, first seen Nov 15, 2026
- Fractera/Agentic-Engineering-Infrastructuretheir own version, first seen Nov 15, 2026
- iha2/superlitetheir own version, first seen Nov 15, 2026
- SireJeff/k0ntexttheir own version, first seen Nov 15, 2026
Used with
Projects 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
LambenthanSkillexp-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 43 projects that use this
skyllwtSkillexp-pilot-eval
Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.
Also in 4 projects that use this
skyllwtSkillexp-pilot-run
Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.
Also in 4 projects that use this
- +5 more from Lambenthan
- +1 more from skyllwt
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- mattpocock/skills★ 325ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- udecode/plate★ 17ksame name
- openai/plugins★ 7.8ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- withcoral/coral★ 5ksame name
179 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.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-developmentSkill
- agent-teamsSkill
- ai-sdkSkill
- analyzing-financial-statementsSkill
- cache-componentsSkill
- chrome-devtoolsSkill
- Codex-automation-recommenderSkill
- Codex-md-improverSkill
- code-reviewSkill
- Command DevelopmentSkill
- creating-financial-modelsSkill
- data-visualizationSkill
- debugSkill
- develop-ai-functions-exampleSkill
- evolve-ai-layerSkill
- excalidraw-diagramSkill
- find-skillsSkill
- frontend-designSkill
- Hook DevelopmentSkill
- make-skill-templateSkill
- markdown-to-htmlSkill
- mcp-builderSkill
- MCP IntegrationSkill
- pdfSkill
- playwrightSkill
- Plugin SettingsSkill
- Plugin StructureSkill
- refactorSkill
- security-best-practicesSkill
- skill-creatorSkill
- Skill DevelopmentSkill
- smithery-ai-cliSkill
- source-command-commit-and-deploySkill
- source-command-commitSkill
- source-command-create-prdSkill
- source-command-create-rulesSkill
- source-command-empty-redeploySkill
- source-command-evaluateSkill
- source-command-executeSkill
- source-command-handoffSkill
- source-command-plan-featureSkill
- source-command-primeSkill
- source-command-reviewSkill
- source-command-self-healSkill
- source-command-validateSkill
- sql-queriesSkill
- statistical-analysisSkill
- vscode-ext-localizationSkill
- webapp-testingSkill
- web-artifacts-builderSkill
- web-design-guidelinesSkill
- Writing Hookify RulesSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 170 edited versions we read keep these.
10
Distinctive
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
- Distinctive: line 33
Read import statements to understand module relationships
- Very specific: line 34
Check package.json/pyproject.toml for external dependencies
- Distinctive: line 39
Start with entry points (main, index, app)
- Distinctive: line 40
Follow the request/response path
- Distinctive: line 42
Look for patterns: MVC, layered, event-driven, etc.
- Distinctive: line 47
When comparing libraries or tools, assess:
- Distinctive: line 57
When collecting docs for a plan or implementation:
- Distinctive: line 63
Look for migration guides if upgrading
- Distinctive: line 67
Always structure research findings as:
- Distinctive: line 90
When running as a sub-agent for research:
- Distinctive: line 92
Read broadly, summarize tightly
“Common” is measured: kept by at least 6 in 10 of the 170 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
Research Skill
When to Use
The agent should read this skill when doing any research task — whether exploring a codebase, researching libraries, or gathering documentation.
Codebase Research
Finding Patterns
# Find all files matching a pattern
find . -name "*.ts" -not -path "*/node_modules/*" | head -30
# Search for a specific pattern in code
grep -rn "pattern" --include="*.ts" src/
# Find usage of a function or type
grep -rn "functionName" --include="*.ts" --include="*.tsx" .
# Find recent changes to a file or area
git log --oneline -10 -- path/to/file
git log --oneline -10 -- "src/area/**"
# See who changed what recently
git log --oneline --all --since="2 weeks ago" | head -20Mapping Dependencies
- Read import statements to understand module relationships
- Check package.json/pyproject.toml for external dependencies
- Trace data flow: entry point → handler → service → storage
- Identify shared utilities and types
Understanding Architecture
- Start with entry points (main, index, app)
- Follow the request/response path
- Identify boundaries between modules/packages
- Look for patterns: MVC, layered, event-driven, etc.
External Research
Library Evaluation
When comparing libraries or tools, assess:
- Maintenance: Last commit, open issues, release frequency
- Adoption: GitHub stars, npm/pip weekly downloads
- Compatibility: Works with current tech stack versions
- Bundle size: Impact on build (for frontend)
- API quality: Clean, well-typed, good docs
- Migration path: Easy to adopt incrementally
Documentation Gathering
When collecting docs for a plan or implementation:
- Find the official docs first (not blog posts or tutorials)
- Link to specific sections, not just the homepage
- Note the version the docs apply to
- Capture gotchas and known issues from GitHub issues
- Look for migration guides if upgrading
Research Output
Always structure research findings as:
## Research: {Topic}
### Key Findings
- {Finding 1 with source}
- {Finding 2 with source}
### Recommendation
{What to do and why}
### Risks / Gotchas
- {Risk 1}
- {Risk 2}
### Sources
- [Source 1](url) — {what we got from it}
- [Source 2](url) — {what we got from it}As a Sub-Agent
When running as a sub-agent for research:
- Be thorough in exploration but concise in reporting
- Read broadly, summarize tightly
- Include specific file paths, line numbers, and URLs
- Flag anything uncertain or that needs human decision
- Your summary is all the main agent will see — make it count
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.

