[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MJFMMCG1WZVR38T40TP3Q":3,"skill-same:01M71MJFMMCG1WZVR38T40TP3Q":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M71MJFMMCG1WZVR38T40TP3Q","competitive-brief",null,"Research competitors and generate a positioning and messaging comparison with content gaps, opportunities, and threats. Use when building sales battlecards, when finding positioning gaps and messaging angles competitors haven't claimed, or when a competitor makes a move and you need to assess the impact.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcompetitive-brief\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcompetitive-brief\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"competitive","competitive brief","brief","sales","comparison","use","assess","competitor","competitors","marketing","generate","work","battlecards","you","when","positioning","impact","knowledge","move","messaging","2026-11-10 10:56:23",false,"---\nname: competitive-brief\ndescription: \"Research competitors and generate a positioning and messaging comparison with content gaps, opportunities, and threats. Use when building sales battlecards, when finding positioning gaps and messaging angles competitors haven't claimed, or when a competitor makes a move and you need to assess the impact.\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"marketing\u002Fskills\u002Fcompetitive-brief\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\n---\n# Competitive Brief\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nResearch competitors and generate a structured competitive analysis comparing positioning, messaging, content strategy, and market presence.\n\n## Trigger\n\nUser runs `\u002Fcompetitive-brief` or asks for a competitive analysis, competitor research, or market comparison.\n\n## Inputs\n\nGather the following from the user:\n\n1. **Competitor name(s)** — one or more competitors to analyze (required)\n\n2. **Your company\u002Fproduct context** (optional but recommended):\n   - What you sell and to whom\n   - Your positioning or value proposition\n   - Key differentiators you want to highlight\n\n3. **Focus areas** (optional — if not specified, cover all):\n   - Messaging and positioning\n   - Product and feature comparison\n   - Content and thought leadership strategy\n   - Recent announcements and news\n   - Pricing and packaging (if publicly available)\n   - Market presence and audience\n\n## Research Process\n\nFor each competitor, research using web search:\n\n1. **Company website** — homepage messaging, product pages, about page, pricing page\n2. **Recent news** — press releases, funding announcements, product launches, partnerships (last 6 months)\n3. **Content strategy** — blog topics, resource types, social media presence, webinars, podcasts\n4. **Review sites and comparisons** — third-party comparisons, analyst mentions, customer review themes\n5. **Job postings** — hiring signals that indicate strategic direction (optional)\n\n### Research Sources\n\nGather intelligence from these categories of sources:\n\n#### Primary Sources (Direct from Competitor)\n- **Website**: homepage, product pages, pricing, about page, careers\n- **Blog and resource center**: content themes, publishing frequency, depth\n- **Social media profiles**: messaging, engagement, content strategy\n- **Product demos and free trials**: UX, features, onboarding experience\n- **Webinars and events**: topics, speakers, audience engagement\n- **Press releases and newsroom**: announcements, partnerships, milestones\n- **Job postings**: hiring signals that reveal strategic priorities (e.g., hiring for a new product line or market)\n\n#### Secondary Sources (Third-Party)\n- **Review sites**: G2, Capterra, TrustRadius, Product Hunt — customer sentiment themes\n- **Analyst reports**: Gartner, Forrester, IDC — market positioning and category placement\n- **News coverage**: TechCrunch, industry publications — funding, partnerships, narrative\n- **Social listening**: mentions, sentiment, share of voice across social platforms\n- **SEO tools**: keyword rankings, organic traffic estimates, content gaps\n- **Financial filings**: revenue, growth rate, investment areas (for public companies)\n- **Community forums**: community forums (e.g. Reddit, Discourse), industry chat groups (e.g. Slack communities) — user sentiment\n\n### Research Cadence\n- **Deep competitive analysis**: quarterly (full research across all sources)\n- **Competitive monitoring**: monthly (scan for new announcements, content, messaging changes)\n- **Real-time alerts**: ongoing (set up alerts for competitor brand mentions, press, job postings)\n\n## Competitive Brief Structure\n\n### 1. Executive Summary\n- 2-3 sentence overview of the competitive landscape\n- Key takeaway: your biggest opportunity and biggest threat\n\n### 2. Competitor Profiles\n\nFor each competitor:\n\n#### Company Overview\n- What they do (one-sentence positioning)\n- Target audience\n- Company size\u002Fstage indicators (funding, employee count if available)\n- Key recent developments\n\n#### Messaging Analysis\n- Primary tagline or headline\n- Core value proposition\n- Key messaging themes (3-5)\n- Tone and voice characterization\n- How they describe the problem they solve\n\n#### Product\u002FSolution Positioning\n- How they categorize their product\n- Key features they emphasize\n- Claimed differentiators\n- Pricing approach (if publicly available)\n\n#### Content Strategy\n- Blog frequency and topics\n- Content types produced (ebooks, webinars, case studies, tools)\n- Social media presence and engagement approach\n- Thought leadership themes\n- SEO strategy observations (what terms they appear to target)\n\n#### Strengths\n- What they do well\n- Where their messaging resonates\n- Competitive advantages\n\n#### Weaknesses\n- Gaps in their messaging or positioning\n- Areas where they are vulnerable\n- Customer complaints or criticism themes (from reviews)\n\n### 3. Messaging Comparison Matrix\n\n| Dimension | Your Company | Competitor A | Competitor B |\n|-----------|-------------|--------------|--------------|\n| Primary tagline | ... | ... | ... |\n| Target buyer | ... | ... | ... |\n| Key differentiator | ... | ... | ... |\n| Tone\u002Fvoice | ... | ... | ... |\n| Core value prop | ... | ... | ... |\n\n(Include user's company only if they provided their positioning context)\n\n### 4. Content Gap Analysis\n- Topics your competitors cover that you do not (or vice versa)\n- Content formats they use that you could adopt\n- Keywords or themes they own vs. opportunities they have missed\n\n### 5. Opportunities\n- Positioning gaps you can exploit\n- Messaging angles your competitors have not claimed\n- Audience segments they are underserving\n- Content or channel opportunities\n\n### 6. Threats\n- Areas where competitors are strong and you are vulnerable\n- Trends that favor their positioning\n- Recent moves that could shift the market\n\n### 7. Recommended Actions\n- 3-5 specific, actionable recommendations based on the analysis\n- Quick wins (things you can act on this week)\n- Strategic moves (longer-term positioning or content investments)\n\n## Analysis Frameworks\n\n### Messaging Comparison Frameworks\n\n#### Value Proposition Comparison\n\nFor each competitor, document:\n- **Promise**: what they promise the customer will achieve\n- **Evidence**: how they prove the promise (data, testimonials, demos)\n- **Mechanism**: how their product delivers on the promise (the \"how it works\")\n- **Uniqueness**: what they claim only they can do\n\n#### Narrative Analysis\n\nIdentify each competitor's story arc:\n- **Villain**: what problem or enemy they position against (status quo, legacy tools, complexity)\n- **Hero**: who is the hero in their story (the customer? the product? the team?)\n- **Transformation**: what before\u002Fafter do they promise?\n- **Stakes**: what happens if you do not act?\n\nThis reveals positioning strategy and emotional appeals.\n\n#### Messaging Strengths and Vulnerabilities\n\nFor each competitor's messaging, assess:\n- **Clarity**: can a first-time visitor understand what they do in 5 seconds?\n- **Differentiation**: is their positioning distinct or generic?\n- **Proof**: do they back up claims with evidence?\n- **Consistency**: is messaging consistent across channels?\n- **Resonance**: does their messaging address real customer pain points?\n\n### Content Gap Analysis Methodology\n\n#### Content Audit Comparison\n\nMap content across competitors by:\n\n| Topic\u002FTheme | Your Content | Competitor A | Competitor B | Gap? |\n|-------------|-------------|--------------|--------------|------|\n| [Topic 1] | Blog post, ebook | Blog series, webinar | Nothing | Opportunity for B |\n| [Topic 2] | Nothing | Whitepaper | Blog post, video | Gap for you |\n| [Topic 3] | Case study | Nothing | Case study | Parity |\n\n#### Content Type Coverage\n\n| Content Format | You | Comp A | Comp B | Comp C |\n|----------------|-----|--------|--------|--------|\n| Blog posts | Y | Y | Y | Y |\n| Case studies | Y | Y | N | Y |\n| Ebooks\u002FWhitepapers | N | Y | Y | N |\n| Webinars | Y | Y | Y | N |\n| Podcast | N | N | Y | N |\n| Video content | N | Y | Y | Y |\n| Interactive tools | N | N | N | Y |\n| Templates\u002FResources | Y | N | Y | N |\n\n#### Identifying Content Opportunities\n1. **Topics they cover that you do not**: potential gaps in your content strategy\n2. **Topics you cover that they do not**: potential differentiators to amplify\n3. **Formats they use that you do not**: format gaps that could reach new audiences\n4. **Audience segments they address that you do not**: underserved audiences\n5. **Search terms they rank for that you do not**: SEO content gaps\n\n#### Content Quality Assessment\n- Depth: surface-level or comprehensive?\n- Freshness: regularly updated or stale?\n- Engagement: do posts get comments, shares, links?\n- Production value: text-only or multimedia?\n- Thought leadership: original insights or rehashed content?\n\n### Positioning Strategy\n\n#### Positioning Statement Framework\n\nFor your company and each competitor, define (or reverse-engineer) their positioning statement:\n\n> For [target audience], [product\u002Fcompany] is the [category] that [key benefit\u002Fdifferentiator] because [reason to believe].\n\nExample:\n> For mid-market SaaS marketing teams, Acme is the campaign management platform that unifies planning and execution in one workspace because it is built on a single data model that eliminates tool fragmentation.\n\n#### Positioning Map\n\nPlot competitors on a 2x2 matrix using the two most important dimensions for your market:\n\nCommon axis pairs:\n- **Price vs. Capability** (low cost \u002F basic vs. premium \u002F full-featured)\n- **Ease of Use vs. Power** (simple \u002F limited vs. complex \u002F flexible)\n- **SMB Focus vs. Enterprise Focus** (self-serve \u002F individual vs. sales-led \u002F team)\n- **Point Solution vs. Platform** (does one thing well vs. does many things)\n- **Innovative vs. Established** (new approach vs. proven track record)\n\nIdentify which quadrant is underserved or where your differentiation is strongest.\n\n#### Category Strategy\n- **Create a new category**: if you do something genuinely different, define and own the category (high risk, high reward)\n- **Reframe the existing category**: change how buyers evaluate the category to favor your strengths\n- **Win the existing category**: compete directly on recognized criteria and out-execute\n- **Niche within the category**: own a specific segment, use case, or audience\n\n#### Positioning Pitfalls to Avoid\n- Positioning against a competitor rather than for a customer need\n- Claiming too many differentiators (pick 1-2 that matter most)\n- Using category jargon the customer does not use\n- Positioning on features rather than outcomes\n- Changing positioning too frequently (confuses the market)\n\n### Battlecard Creation\n\nA competitive battlecard is a one-page reference for sales and marketing teams. Include:\n\n#### Header\n- Competitor name and logo\n- Last updated date\n- Competitive win rate (if tracked)\n\n#### Quick Overview\n- What they do (one sentence)\n- Their target customer\n- Pricing model summary\n- Key recent developments\n\n#### Their Pitch\n- How they describe themselves\n- Their primary tagline\n- Their top 3 claimed differentiators\n\n#### Strengths (Be Honest)\n- Where they genuinely compete well\n- What customers like about them (from reviews)\n- Features or capabilities where they lead\n\n#### Weaknesses\n- Consistent customer complaints (from reviews)\n- Technical limitations\n- Gaps in their offering\n- Areas where customers report dissatisfaction\n\n#### Our Differentiators\n- 3-5 specific ways your product or approach is different\n- For each: the differentiator, why it matters to the customer, and proof\n\n#### Objection Handling\n| If the prospect says... | Respond with... |\n|------------------------|----------------|\n| \"[Competitor] does X too\" | \"Here is how our approach differs...\" |\n| \"[Competitor] is cheaper\" | \"Here is what that price difference gets you...\" |\n| \"I've heard good things about [Competitor]\" | \"They are strong at X. Where we differ is...\" |\n\n#### Landmines to Set\nQuestions to ask prospects early that highlight your advantages:\n- \"How do you currently handle [area where competitor is weak]?\"\n- \"How important is [capability you have that they lack]?\"\n- \"Have you considered [risk that your product mitigates]?\"\n\n#### Landmines to Defuse\nQuestions competitors might encourage prospects to ask you, with prepared responses.\n\n#### Win\u002FLoss Themes\n- Common reasons deals are won against this competitor\n- Common reasons deals are lost to this competitor\n- What types of prospects favor them vs. you\n\n#### Battlecard Maintenance\n- Review and update quarterly at minimum\n- Update immediately after major competitor announcements\n- Incorporate win\u002Floss feedback from sales team\n- Track which objection-handling responses are most effective\n\n## Output\n\nPresent the full competitive brief with clear formatting. Note the date of the research so the user knows the freshness of the data.\n\nAfter the brief, ask:\n\n\"Would you like me to:\n- Create a battlecard for your sales team based on this analysis?\n- Draft messaging that exploits the positioning gaps identified?\n- Dive deeper into any specific competitor?\n- Set up a competitive monitoring plan?\"\n","# Competitive Brief\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nResearch competitors and generate a structured competitive analysis comparing positioning, messaging, content strategy, and market presence.\n\n## Trigger\n\nUser runs `\u002Fcompetitive-brief` or asks for a competitive analysis, competitor research, or market comparison.\n\n## Inputs\n\nGather the following from the user:\n\n1. **Competitor name(s)** — one or more competitors to analyze (required)\n\n2. **Your company\u002Fproduct context** (optional but recommended):\n   - What you sell and to whom\n   - Your positioning or value proposition\n   - Key differentiators you want to highlight\n\n3. **Focus areas** (optional — if not specified, cover all):\n   - Messaging and positioning\n   - Product and feature comparison\n   - Content and thought leadership strategy\n   - Recent announcements and news\n   - Pricing and packaging (if publicly available)\n   - Market presence and audience\n\n## Research Process\n\nFor each competitor, research using web search:\n\n1. **Company website** — homepage messaging, product pages, about page, pricing page\n2. **Recent news** — press releases, funding announcements, product launches, partnerships (last 6 months)\n3. **Content strategy** — blog topics, resource types, social media presence, webinars, podcasts\n4. **Review sites and comparisons** — third-party comparisons, analyst mentions, customer review themes\n5. **Job postings** — hiring signals that indicate strategic direction (optional)\n\n### Research Sources\n\nGather intelligence from these categories of sources:\n\n#### Primary Sources (Direct from Competitor)\n- **Website**: homepage, product pages, pricing, about page, careers\n- **Blog and resource center**: content themes, publishing frequency, depth\n- **Social media profiles**: messaging, engagement, content strategy\n- **Product demos and free trials**: UX, features, onboarding experience\n- **Webinars and events**: topics, speakers, audience engagement\n- **Press releases and newsroom**: announcements, partnerships, milestones\n- **Job postings**: hiring signals that reveal strategic priorities (e.g., hiring for a new product line or market)\n\n#### Secondary Sources (Third-Party)\n- **Review sites**: G2, Capterra, TrustRadius, Product Hunt — customer sentiment themes\n- **Analyst reports**: Gartner, Forrester, IDC — market positioning and category placement\n- **News coverage**: TechCrunch, industry publications — funding, partnerships, narrative\n- **Social listening**: mentions, sentiment, share of voice across social platforms\n- **SEO tools**: keyword rankings, organic traffic estimates, content gaps\n- **Financial filings**: revenue, growth rate, investment areas (for public companies)\n- **Community forums**: community forums (e.g. Reddit, Discourse), industry chat groups (e.g. Slack communities) — user sentiment\n\n### Research Cadence\n- **Deep competitive analysis**: quarterly (full research across all sources)\n- **Competitive monitoring**: monthly (scan for new announcements, content, messaging changes)\n- **Real-time alerts**: ongoing (set up alerts for competitor brand mentions, press, job postings)\n\n## Competitive Brief Structure\n\n### 1. Executive Summary\n- 2-3 sentence overview of the competitive landscape\n- Key takeaway: your biggest opportunity and biggest threat\n\n### 2. Competitor Profiles\n\nFor each competitor:\n\n#### Company Overview\n- What they do (one-sentence positioning)\n- Target audience\n- Company size\u002Fstage indicators (funding, employee count if available)\n- Key recent developments\n\n#### Messaging Analysis\n- Primary tagline or headline\n- Core value proposition\n- Key messaging themes (3-5)\n- Tone and voice characterization\n- How they describe the problem they solve\n\n#### Product\u002FSolution Positioning\n- How they categorize their product\n- Key features they emphasize\n- Claimed differentiators\n- Pricing approach (if publicly available)\n\n#### Content Strategy\n- Blog frequency and topics\n- Content types produced (ebooks, webinars, case studies, tools)\n- Social media presence and engagement approach\n- Thought leadership themes\n- SEO strategy observations (what terms they appear to target)\n\n#### Strengths\n- What they do well\n- Where their messaging resonates\n- Competitive advantages\n\n#### Weaknesses\n- Gaps in their messaging or positioning\n- Areas where they are vulnerable\n- Customer complaints or criticism themes (from reviews)\n\n### 3. Messaging Comparison Matrix\n\n| Dimension | Your Company | Competitor A | Competitor B |\n|-----------|-------------|--------------|--------------|\n| Primary tagline | ... | ... | ... |\n| Target buyer | ... | ... | ... |\n| Key differentiator | ... | ... | ... |\n| Tone\u002Fvoice | ... | ... | ... |\n| Core value prop | ... | ... | ... |\n\n(Include user's company only if they provided their positioning context)\n\n### 4. Content Gap Analysis\n- Topics your competitors cover that you do not (or vice versa)\n- Content formats they use that you could adopt\n- Keywords or themes they own vs. opportunities they have missed\n\n### 5. Opportunities\n- Positioning gaps you can exploit\n- Messaging angles your competitors have not claimed\n- Audience segments they are underserving\n- Content or channel opportunities\n\n### 6. Threats\n- Areas where competitors are strong and you are vulnerable\n- Trends that favor their positioning\n- Recent moves that could shift the market\n\n### 7. Recommended Actions\n- 3-5 specific, actionable recommendations based on the analysis\n- Quick wins (things you can act on this week)\n- Strategic moves (longer-term positioning or content investments)\n\n## Analysis Frameworks\n\n### Messaging Comparison Frameworks\n\n#### Value Proposition Comparison\n\nFor each competitor, document:\n- **Promise**: what they promise the customer will achieve\n- **Evidence**: how they prove the promise (data, testimonials, demos)\n- **Mechanism**: how their product delivers on the promise (the \"how it works\")\n- **Uniqueness**: what they claim only they can do\n\n#### Narrative Analysis\n\nIdentify each competitor's story arc:\n- **Villain**: what problem or enemy they position against (status quo, legacy tools, complexity)\n- **Hero**: who is the hero in their story (the customer? the product? the team?)\n- **Transformation**: what before\u002Fafter do they promise?\n- **Stakes**: what happens if you do not act?\n\nThis reveals positioning strategy and emotional appeals.\n\n#### Messaging Strengths and Vulnerabilities\n\nFor each competitor's messaging, assess:\n- **Clarity**: can a first-time visitor understand what they do in 5 seconds?\n- **Differentiation**: is their positioning distinct or generic?\n- **Proof**: do they back up claims with evidence?\n- **Consistency**: is messaging consistent across channels?\n- **Resonance**: does their messaging address real customer pain points?\n\n### Content Gap Analysis Methodology\n\n#### Content Audit Comparison\n\nMap content across competitors by:\n\n| Topic\u002FTheme | Your Content | Competitor A | Competitor B | Gap? |\n|-------------|-------------|--------------|--------------|------|\n| [Topic 1] | Blog post, ebook | Blog series, webinar | Nothing | Opportunity for B |\n| [Topic 2] | Nothing | Whitepaper | Blog post, video | Gap for you |\n| [Topic 3] | Case study | Nothing | Case study | Parity |\n\n#### Content Type Coverage\n\n| Content Format | You | Comp A | Comp B | Comp C |\n|----------------|-----|--------|--------|--------|\n| Blog posts | Y | Y | Y | Y |\n| Case studies | Y | Y | N | Y |\n| Ebooks\u002FWhitepapers | N | Y | Y | N |\n| Webinars | Y | Y | Y | N |\n| Podcast | N | N | Y | N |\n| Video content | N | Y | Y | Y |\n| Interactive tools | N | N | N | Y |\n| Templates\u002FResources | Y | N | Y | N |\n\n#### Identifying Content Opportunities\n1. **Topics they cover that you do not**: potential gaps in your content strategy\n2. **Topics you cover that they do not**: potential differentiators to amplify\n3. **Formats they use that you do not**: format gaps that could reach new audiences\n4. **Audience segments they address that you do not**: underserved audiences\n5. **Search terms they rank for that you do not**: SEO content gaps\n\n#### Content Quality Assessment\n- Depth: surface-level or comprehensive?\n- Freshness: regularly updated or stale?\n- Engagement: do posts get comments, shares, links?\n- Production value: text-only or multimedia?\n- Thought leadership: original insights or rehashed content?\n\n### Positioning Strategy\n\n#### Positioning Statement Framework\n\nFor your company and each competitor, define (or reverse-engineer) their positioning statement:\n\n> For [target audience], [product\u002Fcompany] is the [category] that [key benefit\u002Fdifferentiator] because [reason to believe].\n\nExample:\n> For mid-market SaaS marketing teams, Acme is the campaign management platform that unifies planning and execution in one workspace because it is built on a single data model that eliminates tool fragmentation.\n\n#### Positioning Map\n\nPlot competitors on a 2x2 matrix using the two most important dimensions for your market:\n\nCommon axis pairs:\n- **Price vs. Capability** (low cost \u002F basic vs. premium \u002F full-featured)\n- **Ease of Use vs. Power** (simple \u002F limited vs. complex \u002F flexible)\n- **SMB Focus vs. Enterprise Focus** (self-serve \u002F individual vs. sales-led \u002F team)\n- **Point Solution vs. Platform** (does one thing well vs. does many things)\n- **Innovative vs. Established** (new approach vs. proven track record)\n\nIdentify which quadrant is underserved or where your differentiation is strongest.\n\n#### Category Strategy\n- **Create a new category**: if you do something genuinely different, define and own the category (high risk, high reward)\n- **Reframe the existing category**: change how buyers evaluate the category to favor your strengths\n- **Win the existing category**: compete directly on recognized criteria and out-execute\n- **Niche within the category**: own a specific segment, use case, or audience\n\n#### Positioning Pitfalls to Avoid\n- Positioning against a competitor rather than for a customer need\n- Claiming too many differentiators (pick 1-2 that matter most)\n- Using category jargon the customer does not use\n- Positioning on features rather than outcomes\n- Changing positioning too frequently (confuses the market)\n\n### Battlecard Creation\n\nA competitive battlecard is a one-page reference for sales and marketing teams. Include:\n\n#### Header\n- Competitor name and logo\n- Last updated date\n- Competitive win rate (if tracked)\n\n#### Quick Overview\n- What they do (one sentence)\n- Their target customer\n- Pricing model summary\n- Key recent developments\n\n#### Their Pitch\n- How they describe themselves\n- Their primary tagline\n- Their top 3 claimed differentiators\n\n#### Strengths (Be Honest)\n- Where they genuinely compete well\n- What customers like about them (from reviews)\n- Features or capabilities where they lead\n\n#### Weaknesses\n- Consistent customer complaints (from reviews)\n- Technical limitations\n- Gaps in their offering\n- Areas where customers report dissatisfaction\n\n#### Our Differentiators\n- 3-5 specific ways your product or approach is different\n- For each: the differentiator, why it matters to the customer, and proof\n\n#### Objection Handling\n| If the prospect says... | Respond with... |\n|------------------------|----------------|\n| \"[Competitor] does X too\" | \"Here is how our approach differs...\" |\n| \"[Competitor] is cheaper\" | \"Here is what that price difference gets you...\" |\n| \"I've heard good things about [Competitor]\" | \"They are strong at X. Where we differ is...\" |\n\n#### Landmines to Set\nQuestions to ask prospects early that highlight your advantages:\n- \"How do you currently handle [area where competitor is weak]?\"\n- \"How important is [capability you have that they lack]?\"\n- \"Have you considered [risk that your product mitigates]?\"\n\n#### Landmines to Defuse\nQuestions competitors might encourage prospects to ask you, with prepared responses.\n\n#### Win\u002FLoss Themes\n- Common reasons deals are won against this competitor\n- Common reasons deals are lost to this competitor\n- What types of prospects favor them vs. you\n\n#### Battlecard Maintenance\n- Review and update quarterly at minimum\n- Update immediately after major competitor announcements\n- Incorporate win\u002Floss feedback from sales team\n- Track which objection-handling responses are most effective\n\n## Output\n\nPresent the full competitive brief with clear formatting. Note the date of the research so the user knows the freshness of the data.\n\nAfter the brief, ask:\n\n\"Would you like me to:\n- Create a battlecard for your sales team based on this analysis?\n- Draft messaging that exploits the positioning gaps identified?\n- Dive deeper into any specific competitor?\n- Set up a competitive monitoring plan?\"\n",{"name":5,"tags":49,"tools":50,"source":51,"license":14,"description":7,"source_path":52,"source_commit":53},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","marketing\u002Fskills\u002Fcompetitive-brief","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcompetitive-brief",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add monoes\u002Fmonomind --skill competitive-brief",{"tool":69,"command":70},"bunx","bunx skills add monoes\u002Fmonomind --skill competitive-brief",{"tool":72,"command":73},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill competitive-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcompetitive-brief\u002FSKILL.md",true,[77],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,[83,109,142,167,192,219],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":108},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[90,91,92,93,94,95,96,41,40,97,98,99,100,101,102,103,104,105,106,107],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":125,"publishedAt":108},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[117,120],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[126,127,128,94,129,130,38,37,97,131,132,133,134,135,136,137,138,139,140,141],"writing","writing plans","plans","superpowers","implementation plan","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":146,"sourceHtmlUrl":147,"categories":148,"keywords":152,"publishedAt":108},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000031","产品经理",[135,153,154,155,156,41,157,38,158,159,35,134,160,161,162,163,164,165,29,166],"write spec","spec","user request","problem","acceptance","ask","vague","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":108},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000033","数据分析师",[97,135,178,179,180,181,41,29,38,182,183,184,185,35,186,187,188,189,190,191],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":204,"publishedAt":108},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[198,201],{"categoryNo":199,"categoryName":200,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":202,"categoryName":203,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[205,206,207,208,180,209,210,211,212,40,213,214,215,97,100,186,216,217,218,188],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":226,"publishedAt":108},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[225],{"categoryNo":202,"categoryName":203,"taxonomyType":21,"taxonomyTypeDesc":22},[207,227,228,229,230,231,232,180,233,234,131,235,236,237,100,186,238,239,188,240],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]