market-research
Skill0 starsChanged 7 months agoMITView on GitHub
Use to scan a competitor, segment, or pricing landscape before a positioning, campaign, or product decision. Produces a one-page brief with competitors, pricing patterns, positioning gaps, and one recommended angle. Cites every claim.
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 repository8 other files it gives its agents.
- code-reviewSkill
- cold-email-sequenceSkill
- content-calendarSkill
- funnel-analysisSkill
- qualify-leadSkill
- release-notesSkill
- seo-outlineSkill
- write-linkedin-postSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 104 edited versions we read keep these.
4
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 16
If the user hasn't given a question, ask: *"What decision will this research inform?"*
- Distinctive: line 57
Every claim about a competitor's pricing, feature, or customer is sourced (URL or screenshot reference).
- Very specific: line 58
If a fact can't be verified, mark [unverified — source: vendor marketing site].
- Distinctive: line 59
Never copy a competitor's copy verbatim into the deliverable.
- Distinctive: line 60
Don't recommend an angle the product can't credibly hold today (or within 90 days).
“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
market-research
Strategic research is not a dump of links. It's a tight brief that ends with a recommendation.
Inputs to gather
- Question — what decision is this research informing?
- Scope — competitors named, segment, geography, price band.
- Time budget — quick scan (≤ 30 min) or deep dive?
If the user hasn't given a question, ask: "What decision will this research inform?"
Method
- List 3-7 competitors that fit the scope.
- For each, capture: tagline, target persona, pricing, top 3 features advertised, last public update.
- Cluster the positioning angles you see (e.g. "all-in-one platform", "best-of-breed point tool", "open-source alt to X").
- Find the gaps — angles nobody is taking, or that everyone is taking poorly.
- Recommend one angle the user could own, plus the proof points needed to credibly hold it.
Output format
## Question
<the decision this informs>
## Competitor matrix
| Company | Tagline | Persona | Pricing | Top features | Last update |
|---|---|---|---|---|---|
| ... | ... | ... | ... | ... | ... |
## Positioning clusters
- Cluster A: <name>. Companies: <list>. Promise: <line>.
- Cluster B: <name>. Companies: <list>. Promise: <line>.
## Gaps
1. <angle nobody owns> — why it's open
2. <angle everyone owns badly> — why we could win it
## Recommendation
Own: <the angle>
Because: <one-paragraph rationale>
Proof points needed: <list>
## Sources
- <url> — <claim it backed>
- <url> — <claim it backed>Hard rules
- Every claim about a competitor's pricing, feature, or customer is sourced (URL or screenshot reference).
- If a fact can't be verified, mark
[unverified — source: vendor marketing site]. - Never copy a competitor's copy verbatim into the deliverable. Paraphrase + cite.
- Don't recommend an angle the product can't credibly hold today (or within 90 days).
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.

