Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

competitive-intelligence

Étoiles2

Forks1

Mis à jour29 mars 2026 à 21:28

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

matellez

matellez/claude-skills

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en études de marché et spécialistes en marketingProfessions des affaires et des opérations financières·SOC 13-1161

SKILL.md

readonly

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.

Plus depuis ce dépôt

même dépôt

intent-data-activation

matellez/claude-skills

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-302

win-loss-analysis

matellez/claude-skills

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-302

marketing-qbr

matellez/claude-skills

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-302

consulting-engagement-setup

matellez/claude-skills

AUTO-TRIGGER: Apply this skill when the user is setting up, scoping, or pricing a consulting engagement as an independent practitioner. Trigger phrases include: "consulting engagement," "new client," "scoping the work," "what should I charge," "hourly versus retainer," "statement of work," "consulting proposal," "client wants to expand scope," "what to put in writing," or any situation where the user is transitioning from employee to consultant or managing the early stages of a client engagement. Also trigger when the user is preparing for a first client conversation and wants to understand what to clarify before agreeing to anything, or when a current engagement is drifting and the user needs to reset the scope. Do NOT trigger for general business development, agency pricing models, or large team consulting practices. This skill is specifically for an independent practitioner, typically a senior B2B marketing, demand gen, or RevOps leader, setting up a direct client engagement for the first time or early i

2026-03-302

consulting-client-presentation

matellez/claude-skills

AUTO-TRIGGER: Apply this skill when the user is preparing to present findings, recommendations, or results to a consulting client. Trigger phrases include: "presenting to my client," "client readout," "how do I present what I found," "delivering findings," "presenting my recommendations," "the client meeting is this week," "I need to show what I discovered in their HubSpot," "presenting my audit results," or any situation where the user is preparing to communicate findings or recommendations to someone who is paying them for consulting work. Also trigger when the user is preparing for a status update with a consulting client, or when they need to deliver bad news about what they found during an engagement. Do NOT trigger for internal presentations to leadership at a full-time employer (use marketing-budget-defense or managing-up for those), or for general presentation design. This skill is specifically for the independent consultant presenting findings or recommendations to an external client.

2026-03-302

linkedin-post

matellez/claude-skills

AUTO-TRIGGER: Apply this skill when the user asks Claude to write, draft, create, or improve a LinkedIn post, caption, or update. Also trigger when the user asks for a post about a professional topic they plan to share on LinkedIn. Do NOT trigger for long-form articles, resumes, emails, or general writing tasks. This skill is specifically for short-form LinkedIn post content only. This skill structures and formats LinkedIn posts to match the user's established content style: punchy, practitioner-level, engagement-focused, with a strong ending that drives comments without resorting to "agree or disagree?" cliches.

2026-03-302

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

HOW TO SET UP THIS SKILL

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.