research
Skill1 starsChanged 4 months agoMITView on GitHub
Market research, competitor analysis, audience research, trend analysis, product research, pricing research. Invoke when: sizing a market, mapping competitors, building an ICP, analyzing industry trends, doing pricing research, mystery shopping a competitor, building a competitive intelligence report, or finding out what an audience actually wants before building or spending. Product-specific user research and feature decisions are an adjacent discipline handled separately.
189 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- quickchatai/quickreviewtheir 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★ 4.9ksame 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 repository60 other files it gives its agents.
- abmSkill
- agent-teamSkill
- analyticsSkill
- automationSkill
- blog-auditSkill
- blog-postSkill
- brandingSkill
- briefSkill
- business-acquisitionSkill
- business-hacksSkill
- chrome-extensionSkill
- claude-code-auditSkill
- closingSkill
- cold-outreachSkill
- communitySkill
- content-ideaSkill
- content-planSkill
- contentSkill
- croSkill
- customer-successSkill
- emailSkill
- entrepreneurSkill
- fact-checkSkill
- financeSkill
- fundraisingSkill
- ghlSkill
- growthSkill
- gtmSkill
- handoffSkill
- hooksSkill
- humanize-strip-aiSkill
- leadsSkill
- local-seoSkill
- manualSkill
- marketing-hacksSkill
- n8nSkill
- nurtureSkill
- offerSkill
- optimize-vs-skillSkill
- paid-mediaSkill
- partnershipsSkill
- personal-brandSkill
- portable-promptSkill
- product-marketingSkill
- productSkill
- prSkill
- replit-qualitySkill
- sales-managementSkill
- save-sessionSkill
- scalingSkill
- seo-hacksSkill
- seoSkill
- social-postSkill
- technical-auditSkill
- tone-of-voiceSkill
- ui-ux-auditSkill
- uxSkill
- vibe-codingSkill
- web-designSkill
- youtube-seoSkill
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 170 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 19
If unclear, ask one question to clarify scope before proceeding.
- Distinctive: line 87
Do not invent facts. If data is not available, say so and proceed with labeled estimates.
- Distinctive: line 89
No padding. If there are only 3 meaningful findings, deliver 3.
“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
Research with a bias toward actionable findings. No academic reports. Every output should answer: so what do I do with this?
Project context is loaded from the active CLAUDE.md. Frame all research findings in terms of that project's goals and competitive position.
When invoked
$ARGUMENTS defines the research type and subject. If unclear, ask one question to clarify scope before proceeding.
Research types
Competitor analysis
For each competitor:
- Product: what they offer, pricing tiers, positioning, differentiators
- Acquisition: how they get customers (SEO, paid, social, partnerships, viral)
- Retention: what keeps customers (features, community, lock-in)
- Weaknesses: what they do badly, where reviews complain, what they are missing
- Opportunity: where they are vulnerable and you can win
Output: comparison table + "where to attack" summary.
Market research
- Market size and growth direction
- Key segments and who is underserved
- Buying triggers: what causes someone to buy in this category?
- Objections: what stops people from buying?
- Pricing norms: what does the market expect to pay?
- Distribution channels that work in this market
Output: market snapshot + top 3 opportunities.
Audience research
- Who they are: demographics, job, situation
- Pain: what problem are they trying to solve right now?
- Language: how do they describe the problem in their own words?
- Watering holes: where do they hang out online?
- Buying behavior: how do they evaluate and decide?
- Triggers: what causes them to act now vs later?
Output: audience profile + messaging implications.
Pricing research
- Competitor pricing tiers and what each tier includes
- Where the market anchors value
- Price sensitivity signals (free trial vs freemium vs demo)
- Packaging patterns (per seat, per usage, flat, tiered)
- Upsell and expansion revenue patterns
Output: pricing benchmark + recommended positioning.
Keyword / SEO research
Full SEO research is a separate discipline; hand it off there rather than half-running it here. This section covers only:
- Quick competitive keyword gap analysis
- Identifying what competitors rank for that you do not
- Finding uncontested long-tail opportunities
Output format
Standard structure:
- Key findings (3-7 bullets, most important first)
- Evidence or source for each finding
- Implications: what this means for the project
- Recommended action: one or two concrete next steps
Rules:
- Label assumptions clearly.
- Do not invent facts. If data is not available, say so and proceed with labeled estimates.
- Prioritize findings by revenue or strategic impact.
- No padding. If there are only 3 meaningful findings, deliver 3.
Adjacent disciplines (where this skill stops)
- Product decisions informed by market research: product-market fit, roadmap, feature prioritization.
- Market sizing feeding investor narratives and pitch decks.
- Full SEO and keyword research, beyond the quick competitive gap analysis above.
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.

