competitive-intelligence

AUTO-TRIGGER: Apply this skill when the user mentions a company they are interviewing with, preparing for an interview at, or researching for a job application. Trigger phrases include: "I have an interview at," "I'm interviewing with," "tell me about [company]," "research [company] for me," "what do I need to know about [company]," or any request to prepare for a specific company meeting or interview. Also trigger when the user shares a company name alongside a job title, job posting, or recruiter name -- these signals indicate interview prep. Do NOT trigger for general industry research, trend analysis, or news requests that are not tied to a specific company and interview.

Jump to install

Repository: modest-curator478/claude-skills
Last source activity: March 29, 2026 at 21:28
Detected SKILL.md language: English
Stars: 4
Forks: 3

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/modest-curator478/claude-skills --skill competitive-intelligence

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

intent-data-activation

AUTO-TRIGGER: Apply this skill when the user is working with intent data signals from ZoomInfo, Bombora, G2, 6sense, Demandbase, or any similar platform, and needs to operationalize those signals into CRM workflows, campaign enrollment, rep alerts, or account prioritization. Trigger phrases include: "intent data," "ZoomInfo intent," "Bombora signals," "G2 buyer intent," "in-market accounts," "activating intent," "intent signals aren't doing anything," "we're paying for intent data but not using it," "how do I route intent accounts," "intent-based campaigns," or any situation where the user has intent data and needs to turn it into action. Also trigger when the user is evaluating which intent signals to act on, designing CRM workflows to handle signal ingestion, or trying to measure whether their intent activation is producing results. Do NOT trigger for general ABM strategy, ZoomInfo data enrichment questions, or lead scoring without intent signals. This skill is specifically about the workflow layer betwee

2026-03-30

win-loss-analysis

AUTO-TRIGGER: Apply this skill when the user wants to run, structure, or improve a win/loss analysis program. Trigger phrases include: "win/loss analysis," "why are we losing deals," "why do we win," "lost deal analysis," "closed lost reasons," "competitive losses," "deal debrief," "why did we lose to [competitor]," "what does sales say about why we lose," "our closed lost data is useless," "I want to interview lost prospects," or any situation where the user is trying to understand the patterns behind deal outcomes. Also trigger when the user has win/loss data they need to synthesize, or when they want to turn win/loss findings into changes to ICP, messaging, pricing, or channel strategy. Do NOT trigger for general competitive intelligence, battlecard creation, or sales coaching. This skill is specifically about the structured diagnostic practice of analyzing deal outcomes and feeding the findings back into GTM decisions.

2026-03-30

marketing-qbr

AUTO-TRIGGER: Apply this skill when the user is preparing for a quarterly business review where they will present marketing performance to executive leadership. Trigger phrases include: "QBR," "quarterly business review," "presenting to the CEO," "presenting to the CRO," "quarterly marketing review," "how do I present last quarter's results," "the quarter was below expectations," "preparing my Q review," "how do I present pipeline attribution," "leadership wants to see what marketing produced," or any situation where the user is preparing to account for marketing performance to senior leadership on a recurring basis. Also trigger when the user needs to handle a QBR where results missed targets, where attribution is contested, or where leadership is likely to question the ROI of specific programs. Do NOT trigger for the marketing budget defense conversation (use marketing-budget-defense for situations where funding is at risk), or for one-time presentations that are not part of a recurring review cycle. This

2026-03-30

View all from this repository

name	competitive-intelligence
version	1.0.0
description	AUTO-TRIGGER: Apply this skill when the user mentions a company they are interviewing with, preparing for an interview at, or researching for a job application. Trigger phrases include: "I have an interview at," "I'm interviewing with," "tell me about [company]," "research [company] for me," "what do I need to know about [company]," or any request to prepare for a specific company meeting or interview. Also trigger when the user shares a company name alongside a job title, job posting, or recruiter name -- these signals indicate interview prep. Do NOT trigger for general industry research, trend analysis, or news requests that are not tied to a specific company and interview.
allowed-tools	["Read","Write","WebSearch","WebFetch"]

Competitive Intelligence: Interview Prep Briefs

This skill runs automatically when the user is preparing for an interview or researching a specific company for a job application. Always search the web before writing anything. Do not rely on training data for company information.

HOW TO SET UP THIS SKILL

Replace the [PLACEHOLDER] sections below with your own background before adding this file to your Claude Project. The more specific you are about your background and target roles, the more relevant the talking points and questions Claude generates will be.

Who This Person Is

Name: [Your full name]

Target roles: [List 3-5 role titles you are actively applying for]

Background: [2-3 sentences summarizing your core expertise, years of experience, key tools, and functional areas.]

Typical interview process for your roles: [Describe the typical stages you encounter, e.g.:

Recruiter screen
Hiring manager
Panel interview
Take-home exercise]

Step 1: Search First

When this skill triggers, immediately run web searches on the company. Do not write the brief until you have current information from the web.

Required searches:

Company name + "news [current year]"
Company name + "funding" or "acquisition" or "PE"
Company name + your functional area
Company name + "reviews" or "Glassdoor"
Company name + job title if provided

Run additional searches if gaps remain.

Step 2: Build the Intel Brief

Deliver the output in this exact format.

COMPANY INTEL BRIEF [Company Name] Prepared: [Today's date] Role: [Role title if provided, otherwise "Not specified"]

WHAT THEY DO [2-3 sentences. Plain language. What product or service, who they sell to, what problem they solve. No marketing speak.]

OWNERSHIP AND FINANCIAL CONTEXT [Public or private. PE-backed, VC-backed, or bootstrapped. Any recent funding rounds, acquisitions, or notable financial events. If PE-backed, name the firm if known.]

Output Rules

No em dashes. Use commas or periods.
Describe the company factually. No marketing language.
If information is not found, say "not found." Do not fill gaps with guesses.
Cite sources by name when referencing specific claims.
Deliver the full brief in one response.

competitive-intelligence

Source facts

Install options

Review the source files

More from this repository

More from this repository

Competitive Intelligence: Interview Prep Briefs

HOW TO SET UP THIS SKILL

Who This Person Is

Step 1: Search First

Step 2: Build the Intel Brief

Output Rules

Competitive Intelligence: Interview Prep Briefs

HOW TO SET UP THIS SKILL

Who This Person Is

Step 1: Search First

Step 2: Build the Intel Brief

Output Rules