market-research
Skill0 starsChanged 2 months agoMITView on GitHub
Build an ICP/competitor/opportunity research pack with dated sources and explicit unknowns. Use when researching a segment, lead company, or market before outbound. Trigger on market research, ICP, competitor, or research pack.
118 other projects use a version of this.
Adopted by
Most recently taken up by
- hmohammed7/claude-skillstheir own version, first seen Nov 16, 2026
- fatihkan/baditheir own version, first seen Nov 16, 2026
- aya-taleb/mimic-skillstheir own version, first seen Nov 15, 2026
- aya-taleb/entrepreneur-skillstheir own version, first seen Nov 15, 2026
- thiefdroppers/cyber-investigator-skillstheir own version, first seen Nov 15, 2026
- Cure-Consulting-Group/ProductEngineeringSkillstheir own version, first seen Nov 12, 2026
Used with
Projects with it also use everything-claude-code, everything-claude-code-conventions 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.
InfopibeSkilleverything-claude-code
Also in 9 projects that use this
mryeastcodeSkilleverything-claude-code-conventions
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Also in 8 projects that use this
InfopibeSkillinvestor-materials
Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.
Also in 22 projects that use this
shawnpangSkillcompetitor-monitoring
When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions. Also use when the user mentions "track competitors", "what are competitors doing", "competitor alerts", or "market watch".
Also in 3 projects that use this
niloykumarbarmanSkillagent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Also in 7 projects that use this
CodeWithBehnamSkilldmux-workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
Also in 15 projects that use this
- +1 more from Infopibe
Other versions118 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 118
- affaan-m/ECC★ 246ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
- CatCatUncle/openworkbuddy★ 413same name
- shawnpang/startup-founder-skills★ 331same name
- loulanyue/awesome-claude-notes★ 272same name
- alexsmedile/hormozi-skills★ 208same name
- okikusan-public/stock_skills★ 134same name
- cohen-liel/hivemind★ 108same name
- extruct-ai/gtm-skills★ 108same name
- tpavanipradeep/everything-claude-code★ 104same name
108 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- eng-prSkill
- sales-outboundSkill
- support-l1Skill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 104 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Read wiki/market/ if pages exist.
- Very specific: line 27
Write or update a page under wiki/market/ (or wiki/sales/leads/<slug>.md for a single lead).
- Very specific: line 34
Do not draft email here — hand off to sales-outbound.
- Distinctive: line 35
Run verifier on claims (no invented TAM/quotes) and confirm the checklist is present for leads.
- Very specific: line 56
Do not invent headcount, ARR, or shipping status to avoid Unknown.
- Distinctive: line 63
No email, no CRM write
- Very specific: line 69
Every number/claim sourced or marked Unknown
“Common” is measured: kept by at least 6 in 10 of the 104 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
When to use
- Before first-touch outbound
- New segment or lead company needs a wiki pack
Models
- Actor:
planner(Gemini Flash — long context + browse) - Verifier:
thinkerorverifier(GLM-4.7-Flash / Groq gpt-oss — different family) - Resolve:
./scripts/resolve-model.sh market-research
Steps
- Restate the research question in one sentence.
- Read
wiki/market/if pages exist; noteUpdated:dates. - Write or update a page under
wiki/market/(orwiki/sales/leads/<slug>.mdfor a single lead). - Produce exactly:
- ICP or account hypothesis
- 3 evidence bullets (sourced or
Unknown) - Competitors / alternatives (known vs unknown)
- Opportunity one-liner + next skill (
sales-outbound)
- If the page is a lead (
wiki/sales/leads/<slug>.md): complete the Required Unknown checklist below. Every row must appear. A row’s value is either a sourced fact or the literal wordUnknown. Omitting a row = incomplete — do not hand off tosales-outbound. - Do not draft email here — hand off to
sales-outbound. - Run verifier on claims (no invented TAM/quotes) and confirm the checklist is present for leads.
Required Unknown checklist (lead pages)
Copy this block into every lead page (values filled):
## Unknown checklist
| Field | Value |
|---|---|
| Headcount / team size (ICP 1–5?) | <sourced fact or Unknown> |
| Shipping status of cited features (GA / beta / coming soon) | <sourced fact or Unknown> |
| Decision-maker path | <sourced fact or Unknown> |
| Timeline ≤90 days | <sourced fact or Unknown> |
| Willingness to talk / design-partner interest | Unknown |Notes:
- “Headcount” may be “appears solo (first-person site)” with a URL — still cite the source. If not evidenced, write
Unknown. - Do not invent headcount, ARR, or shipping status to avoid
Unknown. Willingness…staysUnknownuntil a human confirms a reply or meeting.
Tools allowed
- Browser (read-only)
- Wiki read/write under
wiki/ - No email, no CRM write
Definition of done
- Wiki page path recorded
- 3 evidence bullets present
- Every number/claim sourced or marked
Unknown - Lead pages include the full Unknown checklist (all five rows)
- Next step named:
sales-outbound - Verifier pass (or human escalate)
Never do
- Invent TAM/SAM, quotes, or pricing
- Skip checklist rows on lead pages
- Hand off to
sales-outboundwith missing checklist - Send outreach
Escalation
- Conflicting sources →
SOP_GAP: conflict+ ask human
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.

