research-methodology
Skill0 starsChanged 5 months agoMITView on GitHub
For the Researcher (02). Research the external context from the brief, reuse before building (plugins/MCPs/APIs/libraries), with an explicit recommendation and qualified sources. Use it when building the RESEARCH.md.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- komluk/scaffoldingtheir own version, first seen Nov 7, 2026
- SWEStash/swe-workflow-skillstheir own version, first seen Nov 1, 2026
- irahardianto/awesome-agvtheir own version, first seen Oct 14, 2026
- poemswe/co-researchertheir own version, first seen Oct 13, 2026
- The-Focus-AI/standardstheir own version, first seen Oct 12, 2026
- HughYau/pengsida-learning-research-skillstheir own version, first seen Oct 8, 2026
Used with
Projects with it also use literature-review, context-engineering and 1 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.
JDerekLomasSkillliterature-review
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). This skill should be used when conducting systematic literature reviews, meta-analyses, research synthesis, or comprehensive literature searches across biomedical, scientific, and technical domains. Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles (APA, Nature, Vancouver, etc.).
Also in 3 projects that use this
mrgoonieSkillcontext-engineering
Master context engineering for AI agent systems. Use when designing agent architectures, debugging context failures, optimizing token usage, implementing memory systems, building multi-agent coordination, evaluating agent performance, or developing LLM-powered pipelines. Covers context fundamentals, degradation patterns, optimization techniques (compaction, masking, caching), compression strategies, memory architectures, multi-agent patterns, LLM-as-Judge evaluation, tool design, and project development.
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- VAMFI/claude-user-memory★ 206same name
- magnus919/agent-skills★ 172same name
- irahardianto/awesome-agv★ 157same name
- poemswe/co-researcher★ 135same name
- HughYau/pengsida-learning-research-skills★ 27same name
- komluk/scaffolding★ 16same name
- stupidZZ/skills★ 9same name
- KhaledSaeed18/dotclaude★ 5same name
- ntaffzii/Skill-Agents★ 4same name
- nic095layson/claude★ 1same name
6 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 repository20 other files it gives its agents.
- docs/AGENTS.mdAGENTS.md
- adopt-groundSkill
- agent-authoringSkill
- architecture-decisionSkill
- asset-sourcingSkill
- brand-evaluation-rubricSkill
- criticSkill
- data-integritySkill
- diagrams-gateSkill
- drift-protocolSkill
- env-reproducibleSkill
- orchestrator-bridgeSkill
- project-cleanupSkill
- qa-eyesSkill
- qa-visual-criteriaSkill
- security-auditSkill
- setupSkill
- smoke-testSkill
- technical-documentationSkill
- visualizerSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
3
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 14
Before recommending to build something, verify it doesn't exist.
- Distinctive: line 15
Before recommending a technology, verify it solves the specific problem.
- Distinctive: line 16
Never research in the abstract — always in relation to the brief.
“Common” is measured: kept by at least 6 in 10 of the 14 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
SKILL: research-methodology
For: Agent 02 — RESEARCHER
Version: 1.0.0
Purpose
This skill defines how to research a project's external context. The goal is to deliver actionable information. Every finding must have enough context for the orchestrator and PO to decide.
Core principle
Before recommending to build something, verify it doesn't exist. Before recommending a technology, verify it solves the specific problem. Never research in the abstract — always in relation to the brief.
Process
STEP 1 — Read the full brief. Identify the core problem, user, constraints, and what the product explicitly is NOT. STEP 2 — Search in order: complete tools → plugins/MCPs/APIs → libraries → patterns. For each solution: what it solves, what it doesn't, license, maturity, integration with the stack. STEP 3 — Analyze 3-5 similar products: what they do well, what badly, the differentiator. STEP 4 — Explore tangents if they would change a project decision. STEP 5 — Build the report with an explicit recommendation per section.
Source criteria
HIGH: official documentation, active GitHub, recent changelog, real cases. MEDIUM: recent technical articles, comparisons with methodology. DISCARD: marketing without evidence, undated articles, opinions without context.
Recommend integrating if:
It solves it better than we could build, lower cost, actively maintained, compatible license.
Recommend building if:
Nothing solves the specific problem, or the dependencies complicate more than they help.
RESEARCH.md structure
Executive summary → Existing solutions → Similar products → Relevant technologies → Patterns → Risks → Opportunities → Final recommendation
Mistakes to avoid
× Researching without reading the brief first × Recommending without verifying the license × Confusing popular with suitable for this project × Presenting links without context
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.