company-intel
Skill0 starsChanged 8 months agoMITView on GitHub
Deep research on any company by scanning their public website to extract customers, partners, case studies, testimonials, key metrics, and competitive positioning. Produces a polished 1-slide PowerPoint summary. Use when: research a company, find customers, who are their customers, company research, company overview, customer list, company intel, customer logos, competitive research on company, scan website for customers.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- nishant-Tiwari24/crackedtheir own version, first seen Nov 8, 2026
- deanpeters/Product-Manager-Skillstheir own version, first seen Oct 25, 2026
- NinjaSln-labs/agent-skillstheir own version, first seen Oct 2, 2026
- SpiderIQ/skillstheir own version, first seen Aug 20, 2026
- agrivisionai/claude-skillstheir own version, first seen Jul 14, 2026
- DIAL-Studio/pm-agent-harness-kittheir own version, first seen Jul 8, 2026
Used with
Projects with it also use positioning-workshop, proto-persona and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nandanosqlSkillpositioning-workshop
Facilitate a guided positioning session that walks through target customer, problem, category, benefit, and differentiation using April Dunford's methodology with adaptive questions.
Also in 4 projects that use this
nandanosqlSkillproto-persona
Create hypothesis-driven user personas before doing full research. Uses behavioral attributes, goals, and frustrations to model target users quickly for early-stage alignment.
Also in 3 projects that use this
Dragoon0xSkillroadmap-planning
Build and communicate a product roadmap that balances customer needs, business goals, and team capacity. Covers outcome-driven planning, stakeholder communication, and roadmap hygiene. Use when planning quarters, aligning stakeholders on direction, or when the roadmap feels like a feature wishlist.
Also in 3 projects that use this
huntsyeaSkilljobs-to-be-done
Applies Bob Moesta's demand-side thinking and Jobs-to-be-Done framework to help product teams understand why customers switch, hire, and fire products. Use when conducting switch interviews, drawing forces diagrams, writing job statements, mapping demand timelines, understanding the struggling moment, analyzing why customers hire or fire your product, exploring passive or active looking behavior, researching JTBD, or when user mentions Bob Moesta, demand-side thinking, big hire, little hire, push/pull/anxiety/habit, or the four forces of progress.
Also in 3 projects that use this
- +4 more from nandanosql
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- deanpeters/Product-Manager-Skills★ 7.7ksame name
- DIAL-Studio/pm-agent-harness-kit★ 12same name
- CodeAlive-AI/ceo-ai-os★ 9same name
- nishant-Tiwari24/cracked★ 5same name
- agrivisionai/claude-skills★ 1same name
- NinjaSln-labs/agent-skills★ 1same name
- SpiderIQ/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
If only a company name is provided, search the web to find their official website URL before proceeding.
- Distinctive: line 46
Use web fetch tools to retrieve content from the company's website.
- Distinctive: line 74
Only include customers that are explicitly featured (logo, case study, testimonial, or named reference)
- Distinctive: line 75
Do not infer or guess customers that are not visibly shown
- Distinctive: line 82
Create a brief company profile from the website content:
- Distinctive: line 95
Look at the customer list and identify patterns:
- Very specific: line 105
Use the ppt-deck-generator skill or python-pptx to create a polished 2-slide executive deck.
- Very specific: line 148
Use ppt-deck-generator color palette (navy dark_bg header, Microsoft blue accent, teal highlights)
- Distinctive: line 151
No dark text on dark backgrounds
- Distinctive: line 171
Enhanced by: Run on multiple competitors to build a comparative customer map
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Company Intel (SCOUT Framework)
Research any company by scanning their public website and produce a polished 1-slide PowerPoint showing who their customers are, key metrics, positioning, and notable quotes. SCOUT turns a URL into an executive-ready company intelligence slide in minutes.
When to Use
- Pre-meeting research on a prospect, partner, or competitor
- Building a competitive landscape and need to understand who companies sell to
- Identifying potential co-sell or partner opportunities by mapping customer overlap
- Preparing account intelligence for a sales call
- Creating a quick company overview slide for an internal briefing
- Researching a company before a partnership or investment conversation
What You'll Need
Critical inputs (ask if not provided):
- Company name OR website URL (either one is sufficient)
If only a company name is provided, search the web to find their official website URL before proceeding. If only a URL is provided, extract the company name from the site.
Always ask the user if they have not provided at least one of these. Do not proceed without a company name or URL.
Nice-to-have:
- Specific focus area (e.g., "just customers", "pricing", "positioning")
- Industry or segment context
- Your company name (for overlap analysis)
SCOUT Framework
| Step | What It Does | Key Output |
| Scan | Fetch the company's homepage and key pages (customers, about, pricing) | Raw page content |
| Capture | Extract customer logos, names, testimonials, case studies, metrics | Structured customer list |
| Outline | Summarize the company's positioning, value prop, and key claims | Company profile |
| Uncover | Identify notable patterns: customer segments, industries, company sizes | Customer segmentation |
| Tabulate | Compile everything into a polished 2-slide deck using ppt-deck-generator | 2-slide PPTX |
Process
Step 1: SCAN - Fetch Public Website Data
Use web fetch tools to retrieve content from the company's website. Target these pages in order:
- Homepage - Usually has a "trusted by" logo bar and hero positioning
- Customers page -
/customers,/case-studies,/stories,/clients - About page -
/about,/about-us,/company - Pricing page -
/pricing(optional, for context)
What to look for on each page:
- Logo bars (usually near the top or bottom: "Trusted by", "Used by", "Our Customers")
- Case study links (company names in titles, quotes with names and titles)
- Testimonial quotes with person name, role, and company
- Metrics claims ("100M+ users", "10,000+ companies", "$1B+ processed")
- Partner logos or integration badges
- Industry mentions or segment descriptions
Step 2: CAPTURE - Extract Customer Intelligence
From the scanned pages, build a structured list:
Customer Extraction Table:
| # | Customer Name | Source | Evidence Type | Quote or Detail |
| 1 | [Name] | Homepage logo bar | Logo | - |
| 2 | [Name] | Case study page | Case study + quote | "[Quote]" - [Person], [Title] |
| 3 | [Name] | Testimonial | Quote | "[Quote]" - [Person], [Title] |
Rules:
- Only include customers that are explicitly featured (logo, case study, testimonial, or named reference)
- Do not infer or guess customers that are not visibly shown
- Capture the person's name and title if available (from testimonials)
- Note the evidence type: Logo only, Case study, Testimonial quote, Named reference
- Sort by prominence (case studies and quotes first, then logos)
Step 3: OUTLINE - Build Company Profile
Create a brief company profile from the website content:
| Field | What to Capture |
| Company Name | Official name |
| Tagline | Their main headline or positioning statement |
| What They Do | 1-2 sentence description of their product/service |
| Key Metrics | Any numbers they claim (users, customers, revenue, uptime, etc.) |
| Target Audience | Who they sell to (based on messaging and customer list) |
| Notable Claims | Key differentiators or bold statements from the site |
Step 4: UNCOVER - Analyze Customer Patterns
Look at the customer list and identify patterns:
- By company size: Are they selling to startups, mid-market, or enterprise?
- By industry: What verticals appear most (tech, finance, healthcare, etc.)?
- By use case: What problems do the case studies highlight?
- Customer count tiers: How many logos vs. case studies vs. testimonials?
- Notable names: Any Fortune 500, well-known brands, or surprising customers?
Step 5: TABULATE - Generate 2-Slide PPTX
Use the ppt-deck-generator skill or python-pptx to create a polished 2-slide executive deck.
Slide 1: Company Overview and Positioning
+------------------------------------------------------------------+
| [COMPANY NAME] Company Intelligence Brief [Date] |
+------------------------------------------------------------------+
| [300K+] [150+] [140M] [26] [16] [SOC 2] |
| GTM Teams Providers AI Runs Customers Cases Compliance |
+------------------------------------------------------------------+
| | |
| WHAT THEY DO | POSITIONING |
| [Description paragraph] | [Tagline and value prop] |
| | |
| KEY CAPABILITIES | TARGET BUYERS |
| - Capability 1 | Role 1 - Context |
| - Capability 2 | Role 2 - Context |
| - Capability 3 | Role 3 - Context |
+------------------------------------------------------------------+
| "[Best quote]" - Person, Title [Segment] [Segment] |
+------------------------------------------------------------------+Slide 2: Customer Evidence Map
+------------------------------------------------------------------+
| [COMPANY NAME] Customer Evidence Map [Date] |
| 26 CUSTOMERS | 16 CASE STUDIES | 10 LOGO FEATURES |
+------------------------------------------------------------------+
| Customer Key Result Contact |
| ------- ---------- ------- |
| [8 case studies with results [8 case studies with results |
| and contact names per column] and contact names per column]|
| |
+------------------------------------------------------------------+
| ALSO FEATURED (LOGOS AND PARTNERS) |
| [Logo 1] [Logo 2] [Logo 3] [Logo 4] [Logo 5] ... [Logo 10] |
+------------------------------------------------------------------+Slide Design Rules:
- Use
ppt-deck-generatorcolor palette (navy dark_bg header, Microsoft blue accent, teal highlights) - Segoe UI font family throughout, minimum 9pt for any text
- High contrast: dark text on white/light backgrounds, white text on navy only
- No dark text on dark backgrounds
- Slide 1 left column (45%): Company overview and capabilities
- Slide 1 right column (55%): Positioning and target buyers
- Slide 2: Two-column customer grid with colored dots, key results in blue, contact names in gray
- Bottom strips on both slides: navy background with white/teal text only
Output
Save to:
outputs/company-intel-[company-name]-[YYYY-MM-DD].md(structured research notes)outputs/company-intel-[company-name]-[YYYY-MM-DD].pptx(2-slide exec deck)
Deliverables:
- Customer Extraction Table: Full list of identified customers with evidence type and quotes
- Company Profile: Positioning, metrics, target audience, and key claims
- Customer Pattern Analysis: Segmentation by size, industry, and use case
- 2-Slide PPTX: Slide 1 = Company overview and positioning, Slide 2 = Full customer evidence map
Chain Connections
- Feeds into:
battle-scanner(competitive customer overlap analysis),partner-blueprint(partner customer mapping),gtm-exec-plan(competitive landscape section) - Enhanced by: Run on multiple competitors to build a comparative customer map
- Pairs with:
competitive-exec-brieffor full competitive intelligence package
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

