acquisition-channel-ad…
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
Research a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills.
$ npx -y skills add deanpeters/Product-Manager-Skills --skill company-intel --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/company-intelContext preview
The summary Claude sees to decide when to auto-load this skill.
Research a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills.
name: company-intel argument-hint: "[company, industry, or competitor set]" description: Research a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills. intent: >- Act as a research engine that builds deep, structured understanding of companies, industries, and competitor sets through **seven analytical lenses** — financial landscape, market offer, product portfolio, competitive dynamics, rising trends, PM implications, and strategic signals (patents, hiring, leadership). Produces a stable, structured output that downstream skills consume to generate battlecards, SWOT analyses, positioning statements, PESTEL assessments, and market sizing. Supports four entry points: single company, industry/sector, named competitor set, or company + "discover my competitors" (researches the company first, identifies likely competitors, confirms the list, then runs the full competitor set analysis). type: workflow best_for: - "Building deep company or industry knowledge before a client engagement or workshop" - "Generating structured research that feeds battlecards, SWOT, positioning, or PESTEL" - "Running a competitive scan across 3-5 companies with cross-company comparison" - "Refreshing intel quarterly on companies you track" scenarios: - "Run company-intel on [company or their domain, e.g. helix-motion.com]" - "Give me intel on the clinical data management industry" - "Compare [Company A], [Company B], and [Company C]" - "Run company-intel on [company] competitors" - "Refresh my intel on [company] — what's changed since last quarter?" theme: market-intelligence estimated_time: "30-60 min"
Research engine that builds deep, structured understanding of companies, industries, and competitor sets. Produces a stable output format that you can hand off to other skills and agents to generate battlecards, SWOT analyses, positioning statements, PESTEL assessments, market sizing, and workshop content.
This is not a generic encyclopedia lookup. Every section pushes toward commercial understanding, product implications, and actionable intelligence. The output is a research primitive — structured data other skills consume — not a final deliverable.
**Works best with:** The research target: a company, an industry, or a set of competitors. **Also useful:** The downstream use (battlecard, SWOT, positioning, market sizing) so the research emphasizes the right lenses, plus any constraints on depth or recency.
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.
**Arriving empty-handed? That works too.** The workflow opens by asking for the target and what the intel will feed.
**Example invocation:** `Research Figma and its top 3 competitors — output feeds a positioning workshop next week.`
The skill auto-detects entry point from the user's input. If ambiguous, ask one clarifying question: "Is this about a specific company, an industry, or a set of competitors?"
**Single Company** — User names a company (e.g., "Helix Motion Systems," "Brightwater Biologics" — or any real company). Produce the full 11-section output for that company.
**Industry/Sector** — User names an industry, sector, or niche (e.g., "clinical data management," "embedded finance," "upstream oil and gas"). Establish broad industry context, narrow into the segment, and connect findings to PM implications. Use the same 11-section structure adapted for sector-level analysis.
**Named Competitor Set** — User names 2-5 companies (e.g., "Compare Helix Motion, Northfield Automation, and Corvid Industrial"). Produce individual 11-section outputs for each company, then add a **Section 12: Cross-Company Comparison** that synthesizes across the set.
**Discover Competitors** — User names a company plus the word "competitors" (e.g., "helix-motion.com competitors" or "Helix Motion Systems competitors"). The skill: 1. Researches the named company first — enough to understand what it does, who it serves, and what market it plays in (a lightweight pass through Lenses 1-4) 2. Identifies 3-5 likely competitors based on that research, citing why each is a competitor (direct, adjacent, substitute, or emerging disruptor) 3. Presents the list for confirmation: "Based on my research, [Company]'s closest competitors appear to be [A, B, C, D, E]. Want me to run the full competitor set on these, or adjust the list first?" 4. Once confirmed, proceeds with the Named Competitor Set flow — full 11-section output for each company plus Section 12 cross-company comparison
The user can also provide a URL instead of a company name (e.g., "helix-motion.com"). The skill should resolve the URL to the company, research accordingly, and proceed.
---
These lenses structure all analysis. Apply every lens to every entry point.
**Lens 1 — Financial Landscape and Business Outcomes** How the entity makes money. Major revenue streams and cost drivers, margin pressures, growth levers, retention and expansion dynamics, capital intensity, seasonal or cyclical patterns, major risks to performance.
**Lens 2 — Market Offer and Business Model** How the entity creates and captures value. Target markets, buyers, users, influencers, administrators, and blockers. How segments differ. Multi-sided or multi-stakeholder dynamics.
**Lens 3 — Product Portfolio and Product Outcomes** Major offers, product families, services, platforms, channels. Bundled solutions, ecosystem plays. Digital versus human-assisted components. Legacy versus emerging offers. Distinction between business line, offer, product, feature set, service layer, and enabling platform.
**Lens 4 — Competitive Dynamics** Direct competitors, adjacent com
77 battle-tested PM frameworks, ready for Claude, Codex, ChatGPT, and any agent that can read structured knowledge.
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead…
Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
Map evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next tranche of growth comes from,…
The protocol behind every investigation skill. Use when AI research must proceed without you: search-plan gate, Fact/Inference/Assumption labels, confidence…