company-intel
Research a company, industry, or competitor set using web search and seven analytical lenses
Install / Use
npx skills add deanpeters/Product-Manager-Skills --skill company-intelInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Education & ResearchSupported Platforms
Tags
Our assessment of company-intel
company-intel scores 92/100 on our quality scale, 95th of 421 Education & Research skills we index (top 23%).
Its SKILL.md is 32 KB long, well organised into 53 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so company-intel is actively maintained.
- Our last check on 2026-10-05 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
company-intel compared with similar skills
All 4 of these similar skills score higher than company-intel; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| company-intel (this skill)by deanpeters | 92 | 7.1k | 3mo ago | SKILL.md |
| last30days-skillby mvanhorn | 100 | 68.0k | today | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install company-intel?
- Run
npx skills add deanpeters/Product-Manager-Skills --skill company-intel. The install tabs above show the steps for each supported agent. - Which AI agents does company-intel work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is company-intel safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is company-intel still maintained?
- The repository was last updated about 3 months ago, so company-intel is actively maintained.
Skill content
View source on GitHubname: 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"
Purpose
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.
Input
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.
Key Concepts
Four Entry Points
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:
- 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)
- Identifies 3-5 likely competitors based on that research, citing why each is a competitor (direct, adjacent, substitute, or emerging disruptor)
- 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?"
- 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.
Seven Research Lenses
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 competitors, substitutes, emerging disruptors. Where differentiation is won or lost.
Lens 5 — Rising Trends and Strategic Concerns Market trends, regulatory forces, technology shifts (especially AI and automation), operational constraints, buyer expectation changes, threats from consolidation or commoditization.
Lens 6 — How Product Management Works Here Product-led vs sales-led vs service-led behavior. Centralized vs federated product structures. Platform vs solution orientation. Roadmap and innovation posture. Compliance or governance overhead. Discovery maturity, data maturity, experimentation maturity, AI maturity. Cross-functional friction. Label inferences clearly.
Lens 7 — Strategic Signals Three signal types — always check all three:
- Patent activity: Recent filings and grants via patent databases. Technology domains, R&D clusters, gaps between patent activity and public product narrative.
- Hiring signals: Roles open in volume, skills and tools in job descriptions, seniority being hired, language that reveals product culture (discovery, outcomes, AI-native, regulatory, experimentation).
- Leadership changes: C-suite and product leadership arrivals or departures in the last 12-18 months. Origin of new leaders (platform companies, consulting, competitors). New CPO, CTO, or CDO roles created, eliminated, or restructured. Board-level changes.
Sharp heuristics for reading the product organization specifically:
- CPO/VP Product tenure: a new product leader hired in the last 12-18 months almost always means the prior approach failed — read what they were hired from (platform company? consultancy? competitor?) as the intended correction.
- PM job postings as culture documents: how they define the PM role — outcome language vs. feature/roadmap language, discovery expectations, who PMs report to — reveals how product actually works there better than any About page.
- Employee-review themes: clusters around "roadmap chaos," "priorities change weekly," or "product vs. engineering tension" are Lens 6 evidence — community-tier confidence, labeled, but often the earliest honest signal.
Reading organizational distress (optional deepening, for engagement or partnership prep). When the intel supports a conversation with the company — a partnership, a sales motion, a job interview — add the distress read: what's the most likely presenting problem (what they'd say is wrong) versus the probable underlying problem (what the evidence suggests is actually wrong)? Was there a trigger event — missed guidance, a failed launch, a reorg, a new executive inheriting a mess? Calibrate the distress level: doing fine and optimizing → knows something's wrong → in trouble and doesn't know it yet. Label the whole read as Inference; it's the most useful and least certain section in the file.
Key Distinctions to Maintain
Always be disciplined about these — collapsing them produces shallow analysis:
- market vs segment
- buyer vs user
- product vs service
- business outcome vs product outcome vs output
- strategy vs tactics
- discovery vs delivery
- platform vs application
- signal vs assumption
- revenue growth vs market share growth vs customer lifetime value improvement vs cost reduction
Tensions Worth Surfacing
Highlight conflicts and tradeoffs wherever they appear:
- growth vs compliance
- scale vs customization
- digital self-service vs high-touch service
- standardization vs domain-specific workflow
- innovation vs legacy burden
- AI ambition vs governance reality
- customer value vs internal efficiency
- short-term revenue vs long-term platform investment
Why This Works
- Web-grounded: Uses live search, not training-data recall — output includes citations
- PM-native: Every section connects to product management implications, not just business facts
- Composable: Stable output format that downstream skills can parse and consume
- Repeatable: Same input next quarter produces fresh intel — the delta is the story
- Signal-driven: Strategic signals (patents, hiring, leadership) are often the most honest data available — they reveal what a company is actually doing, not what it says it's doing
Anti-Patterns
- Not a Wikipedia summary: Push past "what they do" to "what this means for product decisions"
- Not financial analysis: Focus is product strategy and commercial dynamics, not valuation or stock picks
- Not a prompt generator: The output is actual research with citations, not prompts for a future session
- Not a one-time exercise: Design for quarterly refresh — run it again, compare the delta
Research Expectations
Use web search actively. This skill requires live data gathering, not recall from training data. Search for and cite:
- Investor relations materials, annual reports, earnings transcripts
- Company product pages and official strategy pages
- Regulatory disclosures and filings
- Patent databases (Google Patents, USPTO)
- Company careers pages and job aggregators (LinkedIn, Indeed, Glassdoor)
- Executive appointment announcements and leadership change coverage
- Industry analysts (Gartner, Forrester, IDC) and reputable news coverage
Cite sources. Every factual claim should include a source. Use the library's canonical evidence
labels from autonomous-investigation: Fact
(source-supported), Inference (evidence-based interpretation), Assumption (working guess).
When you're inferring — especially on Lens 6 (PM culture) and Lens 7 (strategic signals) — show the
basis: "Inference based on [evidence]."
Source priority ladder. Primary (filings, earnings calls, investor docs) → credible secondary (major business press, trade publications) → community (Glassdoor, review sites, forums — lower confidence) → inferred signals (job postings, announcements). State where each claim sits.
**Recency matte
Truncated for display — read the full file on GitHub.
Related Skills
last30days-skill
68.0kAI agent skill that researches any topic across Reddit, X, YouTube, HN, Polymarket, and the web - then synthesizes a grounded summary
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
