本文へ移動
cccskills
無料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).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

Step 3 of the suggested chain: /company-context → /icp-research → competitor-research → /win-loss → /expert-pov → /tov-guidelines → /brand-kit → /positioning → /messaging → /funnel-strategy → /goals.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

brand-kit

無料

Extracts a company's visual identity from screenshots (best) or its website (fallback) and writes a DESIGN.md brand file: machine-readable tokens for colours, typography, spacing, corner radius and logo usage, plus short prose explaining how and when to use each, and a list of do's and don'ts. Any later page, deck, carousel or ad can read the tokens instead of guessing. Triggers: "brand kit", "brand guidelines", "extract our brand", "design tokens", "colours and fonts from", "visual identity", "DESIGN.md". Not for tone of voice (use /tov-guidelines) or messaging (use /messaging).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Researches a company from its website and public sources and writes a company profile: what it sells, who buys it, traction, funding, team, hiring, tech stack, key people, red flags and the gaps you still need to fill, every claim tagged with a source and a confidence level. Use it as the first file in a marketing context folder, or to prep a discovery call or qualify a prospect. Triggers: "company research", "company background", "company context for", "qualify this prospect", "discovery call prep", "account brief", or a company URL handed over for research. Not for competitor analysis (use /competitor-research) or customer profiles (use /icp-research).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Draws out a founder's or expert's point of view: what they believe about their market that others don't, the hot takes they'd defend, the stories behind them, and their taste. Generates interview questions, works from answers, a live call or existing content, and ends with ranked One Big Idea candidates for thought leadership and positioning. Triggers: "expert POV", "founder POV", "one big idea", "OBI", "contrarian beliefs", "what makes our founder different", "thought leadership foundation", "founder interview questions". Feeds /positioning and /tov-guidelines. Not for writing posts or articles, and not for brand voice rules (use /tov-guidelines).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Works out a company's go-to-market motion (product-led, sales-led or hybrid) from its website and pricing, then maps the funnel stage by stage: a definition, strategy, leading inputs the team controls, lagging outputs with targets, cadence and owner for each stage, MQL, SQL and PQL criteria, post-sale stages, closed-lost re-entry paths and backward funnel maths from a revenue target. Triggers: "funnel strategy", "funnel stages", "pipeline stages", "PLG vs SLG", "lead qualification criteria", "map our sales process", "how do leads flow". Feeds /goals. Not for setting the target itself (use /goals).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

goals

無料

Turns a target someone has already committed to (a board plan, an annual plan, a contract) into a plan the team can measure: KPIs in three tiers with a guardrail for each, a baseline from real data, monthly pacing with lag and seasonality, and two or three channels chosen from how your ICP actually searches and buys. Writes context/goals/MMYY-scope.md and context/goals/measurement.md. It never invents the target. Triggers: "set our goals", "what are our KPIs", "revenue target and pacing", "which channels and what targets", "write the scope file", "are we on track". Run after /funnel-strategy. Not for designing funnel stages (use /funnel-strategy).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

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

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

matteotitta のスキルをすべて見る

このスキルの問題を報告する