Skip to content
cccskills
FreePublished on GitHub

competitor-research

Researches one B2B SaaS competitor across 13 dimensions (company, product, ICP, pricing, reviews, content, launches, search and AI visibility, tech stack, hiring, go-to-market, social, paid ads) and writes a sourced dossier with an executive summary, a threat level, strengths and weaknesses, and a data gaps section. Run it once per competitor, then compare. Triggers: "competitor analysis", "competitor research on", "what is [competitor] doing", "compare us to", "competitive landscape", "battlecard prep". Run after /company-context and /icp-research. Not for researching your own company (use /company-context).

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md5.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Competitor research

Build a dossier on one competitor that a marketer, a seller and a founder can each act on. The rule that governs everything: no data point without a source. Every claim carries a URL and an access date, or it's marked [Not available].

When to use it

  • Building the context folder, after you know who your customer is.
  • Before positioning, so you know what buyers compare you to.
  • When a competitor shows up in deals more often, or launches something.

Don't use it for your own company (/company-context) or a single factual question ("what does X charge?"), which you can answer directly.

Inputs

Required: the competitor's name and website. If the name is ambiguous, confirm before you start.

Recommended: context/company/ and context/icp/ (so you can judge the threat against your own buyer), any existing dossier to refresh, and the questions the user cares about most (pricing, outbound, a feature).

Paths. Write to context/competitors/MMYY-<competitor-slug>.md. With two or more dossiers done, add context/competitors/MMYY-landscape.md. Agency or consultant? Swap context/ for clients/<client>/context/ throughout.

Tools. Web search and page fetching cover most of it. Exa helps find similar companies and clean page text; Firecrawl helps with pricing and comparison pages. Paid SEO and tech-stack tools are optional: if you don't have one, say so in that dimension rather than guessing. On a large site, list the pages first and only read the ones that matter (product, pricing, positioning, customers).

The 13 dimensions

  1. Company: founding, funding, headcount, leadership.
  2. Product: core offer, key features, what changed recently.
  3. ICP: who they sell to, judged from their case studies and logos.
  4. Pricing: model, tiers, entry price, what's gated behind sales.
  5. Reviews: themes in G2, Capterra or Trustpilot praise and complaints, with counts.
  6. Content: what they publish, how often, which topics.
  7. Launches: what they've shipped in the last 12 months.
  8. Search and AI visibility: the topics they rank or get cited for.
  9. Tech stack: tools visible on the site, if you can see them.
  10. Hiring: open roles by team, which signal where they're investing.
  11. Go-to-market: self-serve, sales-led or both; channels; partnerships.
  12. LinkedIn and social: founder and company activity, recurring themes.
  13. Paid advertising: ads visible in public ad libraries, angles they test.

Steps

  1. Confirm scope. Name, URL, and what the user wants to learn. Produces: a one-line brief.
  2. Research each dimension in the order above. Note the source and date for each finding. If a dimension needs a tool you don't have, write [Not available: needs X] and move on.
  3. Tag confidence. [VERIFIED], [INFERRED], [ESTIMATED], [UNAVAILABLE]. Aim for at least half verified.
  4. Assess strengths and weaknesses against your ICP, not in the abstract.
  5. Set a threat level: primary (same buyer, same problem, often in deals), enterprise tier (same problem, bigger buyer), direct ICP (same buyer, adjacent problem), watch (early or stealth), low, or defunct. Explain the call in two sentences.
  6. Write the executive summary last, in 2 to 3 short paragraphs.
  7. List data gaps with the action that would fill each one.
  8. If you have 2 or more dossiers, write a landscape file: threat table, feature comparison, where each competitor is weak, and 3 to 5 recommendations. Cite the dossiers rather than repeating them.
  9. Hand off to /positioning, which uses the competitor set as its list of alternatives.

Output shape

Title the file # Competitor research: [Name]. Then: a recent-changes line (on a refresh), executive summary, threat level, a section per dimension with inline (Source: X) notes, strengths and weaknesses, data gaps, and a sources table at the end with URL, access date and confidence per dimension.

What good looks like

  • All 13 dimensions present, each either filled or marked with why it's empty.
  • Major claims (funding, size, pricing) have more than one source.
  • Review themes come with counts, not adjectives.
  • The threat level would make sense to your sales team.
  • A refresh updates the existing file and notes what changed, rather than creating a duplicate.

Mistakes to avoid

  • Copying their marketing claims as fact. Note the claim, then the evidence.
  • Guessing pricing that's behind "contact sales".
  • Reporting old news as current. Date every finding.
  • A weakness list that's really a wish list ("their UX is bad") with no evidence.
  • Restating every dossier inside the landscape file.

Chain

Part of the free five-skill chain: /icp-research → competitor-research → /tov-guidelines → /positioning → /messaging. The other six context skills (company context, win-loss, founder POV, brand kit, funnel and goals) are in the paid context plugin ($19.99, link in the README).

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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).

The English summary is being prepared. Showing the original description.

matteotitta/repo-structure-in-house68Updated Oct 21, 2026

level

Free

Score your Claude Code environment on a fun 0-10 ladder (Tourist → Swarm) calibrated to the quickstart's 4 systems — Context, Skills, Integrations, Orchestration. Two front doors - an interactive quiz (zero setup, shareable) or a silent scan of your repo. Outputs a next-level roadmap plus a branded HTML dashboard or a paste-anywhere ASCII card. The default mastery skill of this quickstart. Triggers - "level", "what's my claude code level", "claude code level quiz", "assess my setup", "how good is my setup", "claude code maturity"

The English summary is being prepared. Showing the original description.

matteotitta/repo-structure-in-house68Updated Oct 21, 2026

Builds a product messaging library from your positioning, your website and customer evidence: a description, the status quo and alternatives, pain points with their knock-on consequences, capabilities, functional, emotional and social benefits, branded features, the cost of doing nothing, common objections with responses, and core messaging blocks (tagline, elevator pitch, value props, proof, per-audience lines). Every claim sourced. Triggers: "product messaging", "messaging library", "messaging framework", "value props", "capabilities and benefits", "what are our differentiators in words". Run after /positioning. Not for choosing the position itself (use /positioning).

The English summary is being prepared. Showing the original description.

matteotitta/repo-structure-in-house68Updated Oct 21, 2026

Develops B2B SaaS positioning from your ICP, competitor and win-loss evidence. Maps what buyers compare you to, chooses between leading with a category or a problem, picks a primary and secondary anchor and up to three defensible differentiators, lays out 2 to 4 worked positioning options with a comparison canvas so you can decide, then locks the chosen one and tests it (clarity ladder, guarantee test). Triggers: "positioning", "how do we position", "what category are we in", "how do we differentiate from", "our homepage is confusing", "positioning options". Run before /messaging. Not for taglines or a messaging library (use /messaging).

The English summary is being prepared. Showing the original description.

matteotitta/repo-structure-in-house68Updated Oct 21, 2026

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).

The English summary is being prepared. Showing the original description.

matteotitta/repo-structure-in-house68Updated Oct 21, 2026

See all skills by matteotitta

Report a problem with this skill