competitor-research
Skill145 starsChanged 6 months agoMITView on GitHub
Research 3–5 competitors for any product or feature. Returns positioning, pricing, key differentiators, and gaps. Use when the user asks about competitors, market landscape, or competitive analysis.
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 19 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 6
Ask the user: "What product or feature are you researching?
- Distinctive: line 17
After all competitors, add a Gap Analysis section:
- Distinctive: line 22
Keep each competitor to 6 bullet points max.
“Common” is measured: kept by at least 6 in 10 of the 19 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
Ask the user: "What product or feature are you researching? Who is it for?"
Then research 3–5 direct competitors using web search. For each competitor return:
[Competitor Name]
- Positioning: one sentence on how they describe themselves
- Target customer: who they're built for
- Pricing: tiers and price points if public
- Key differentiators: 2–3 things they do well
- Weaknesses: 1–2 gaps or complaints from reviews/forums
After all competitors, add a Gap Analysis section:
- What no competitor does well
- Where pricing is underserved
- One positioning angle that is unclaimed
Keep each competitor to 6 bullet points max. No padding. End with one sharp question: "Based on this, which gap are you trying to own?"
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- explorium-ai/gtm-skills★ 346same name
- marcosmodly/marketing-skill★ 100same name
- matteotitta/claude-code-marketing-quickstart★ 70same name
- matteotitta/repo-structure-in-house★ 70same name
- matteotitta/genesys-skills★ 46same name
- smithjohn78390/smith--skills★ 41same name
- yangliu2060/smith--skills★ 40same name
- Synter-Media-AI/mcp-server★ 21same name
- jsath/claude-skills★ 14same name
- CodeAlive-AI/ceo-ai-os★ 9same name
16 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.
Used alongsideProjects with it also use tov-guidelines, icp-research and 2 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.
matteotittaSkilltov-guidelines
Extracts a company's tone of voice from its own content and turns it into rules a writer or an AI can follow. Phase 1 analyses 15 to 20 pages for sentence, paragraph, word and structure patterns with frequency counts; after the user reviews it, Phase 2 writes the guidelines: tone attributes with before and after examples, a We are / We are not table, tone by context, vocabulary to use and avoid, and open questions. Triggers: "tone of voice", "brand voice", "voice guidelines", "writing style guide", "extract voice from our website", "TOV". Not for visual identity (use /brand-kit) or messaging (use /messaging).
Also in 4 projects that use this
matteotittaSkillicp-research
Builds an ideal customer profile from evidence: case studies, testimonials, customer logos, solutions pages, reviews and any sales notes you have. Produces market sizing layers, firmographic segments, a champion and an economic buyer persona, a negative ICP, intent signals, customer proof points and a voice-of-customer section in the buyers' own words, every claim sourced. Triggers: "ICP research", "ideal customer profile", "who are our customers", "customer segments", "buyer personas", "who should we target". Run after /company-context. Not for competitor analysis (use /competitor-research) or call transcript patterns (use /win-loss).
Also in 4 projects that use this
nocodeworkSkillcompany-context
Interview the user to build or update a reusable company context file for AI tools — what the company does, its offer, clients, personas, positioning, voice, and the questions clients ask most. Use when the user says "build our company context", "create company context", "set up business context for AI", "update our company context", or wants AI to answer clients and write content in the company's voice without re-explaining the business each time. Produces company-context.md.
Also in 3 projects that use this
VercelSkillpositioning
Use when working out what a product is, who it's for, and what it competes with: the market alternatives, the ideal customer, the differentiators worth claiming, and the positioning statement that follows.
Also in 3 projects that use this
In this repository53 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- beautiful-htmlSkill
- boris-planSkill
- brandkitSkill
- industrial-brutalist-uiSkill
- business-caseSkill
- changelog-writerSkill
- claude-code-deckSkill
- content-repurposerSkill
- customer-personaSkill
- deploy-checklistSkill
- dockerfile-generatorSkill
- email-writerSkill
- exec-summarySkill
- feature-prioritizerSkill
- frontend-slidesSkill
- gpt-tasteSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- karpathy-reviewSkill
- launch-checklistSkill
- linkedin-postSkill
- market-sizingSkill
- md-to-pdfSkill
- meeting-analyzerSkill
- minimalist-uiSkill
- newsletter-ideatorSkill
- okr-writerSkill
- full-output-enforcementSkill
- prd-generatorSkill
- proposal-writerSkill
- redesign-existing-projectsSkill
- retro-facilitatorSkill
- seo-optimizerSkill
- sharpenSkill
- skill-evaluatorSkill
- skill-to-sdkSkill
- slides-builderSkill
- high-end-visual-designSkill
- sprint-plannerSkill
- stakeholder-updateSkill
- stitch-design-tasteSkill
- design-taste-frontendSkill
- design-taste-frontend-v1Skill
- test-writerSkill
- trend-spotterSkill
- ui-ux-pro-maxSkill
- user-story-writerSkill
- verify-workSkill
- voice-dnaSkill
- youtube-deepdiveSkill
- youtube-researcherSkill
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.

