market-research
Skill8 starsChanged 2 months agoMITView on GitHub
Define a market and examine customers, demand, segments, trends, and defensible size estimates with transparent evidence.
113 other projects use a version of this.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- ahmadvahidi/skill-atlastheir own version, first seen Nov 8, 2026
- CatCatUncle/openworkbuddytheir own version, first seen Nov 5, 2026
- Cure-Consulting-Group/ProductEngineeringSkillstheir own version, first seen Nov 4, 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-outreach
Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.
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
tpavanipradeepSkillnextjs-turbopack
Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.
Also in 14 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
- +1 more from Infopibe
Other versions113 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 113
- affaan-m/ECC★ 246ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
- CatCatUncle/openworkbuddy★ 398same 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
103 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 repository77 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- archive-milestoneSkill
- assess-product-opportunitySkill
- automate-testsSkill
- bump-versionSkill
- capture-work-itemsSkill
- commit-workSkill
- competitive-researchSkill
- consume-nats-messageSkill
- decontextualize-textSkill
- deep-researchSkill
- define-docs-normsSkill
- define-missionSkill
- define-north-starSkill
- define-roadmapSkill
- define-strategic-pillarsSkill
- define-visionSkill
- deliver-featureSkill
- design-strategic-goalsSkill
- eli5Skill
- establish-delivery-workflowSkill
- execute-delivery-workflowSkill
- generate-agent-entrySkill
- generate-github-workflowSkill
- generate-standard-readmeSkill
- inspect-artifact-stateSkill
- integrate-branchesSkill
- manage-secretSkill
- map-item-dependenciesSkill
- orchestrate-code-reviewSkill
- orchestrate-governance-stepSkill
- orchestrate-repair-loopSkill
- orchestrate-repair-requirements-loopSkill
- orchestrate-roadmap-planningSkill
- plan-milestonesSkill
- plan-nextSkill
- policy-researchSkill
- ponytailSkill
- prepare-presales-responseSkill
- prepare-version-notesSkill
- prioritize-backlogSkill
- product-opportunity-analysisSkill
- promote-roadmap-itemsSkill
- publish-nats-messageSkill
- record-milestone-achievementSkill
- redeploy-localSkill
- refine-skill-designSkill
- review-architectureSkill
- review-codebaseSkill
- review-diffSkill
- review-dotnetSkill
- review-error-surfacingSkill
- review-functional-designSkill
- review-goSkill
- review-implementation-alignmentSkill
- review-javaSkill
- review-observabilitySkill
- review-orm-usageSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 99 edited versions we read keep these.
0
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
- Very specific: line 22
If sizing is defensible, show formula, source inputs, assumptions, range, units and date.
“Common” is measured: kept by at least 6 in 10 of the 99 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: Market Research
Purpose
Study a defined market without assuming that a popular category or vendor estimate is a real demand signal. Apply deep-research and preserve its Research Report as the evidence core.
Procedure
- Define geography, segment, buyer and user, included products, exclusions, period and currency before searching. Record definition changes across sources.
- Decompose demand, customer jobs, adoption, budgets, size, growth, supply and shifts. Prefer authorized customer interviews and observed use for need; method-bearing datasets, filings and associations for size. Attribute vendor, consultant and media estimates.
- Inspect methodology, sample, denominator, year and provenance family. Cross-check important numbers against independent sources where possible. Do not add incompatible figures.
- If sizing is defensible, show formula, source inputs, assumptions, range, units and date; map each input to finding IDs. If it is not, state
unsupportedand list missing inputs instead of inventing TAM/SAM/SOM. - Separate demand evidence from awareness or sales assertions. Classify every material statement and preserve contradictory estimates in conflicts. Add
domain: "market"anddomain_detailsonly if useful; never replace common source or finding fields.
Self-check
The reader can reproduce the market boundary and any estimate. Vendor claims remain attributed; trend and demand evidence are dated. Missing customer signals and unsupported sizing appear as gaps.
Examples
Reproducible estimate
Input: estimate annual spending for a defined buyer segment in one country. Output: show the segment boundary, source-backed buyer count and spend assumptions, formula, dated range, and finding IDs for each input.
Incompatible estimates
Input: two sources use different definitions of the market, and neither discloses a denominator. Output: keep the figures separate as attributed claims, mark sizing unsupported, and name the missing inputs needed for a defensible estimate.
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.

