intelligence-collection-disciplines
Run competitive research like an intelligence agency: eight collection disciplines (OSINT to MASINT), signal-to-inference chains, and fusion
Install / Use
npx skills add deanpeters/Product-Manager-Skills --skill intelligence-collection-disciplinesInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Product ManagementSupported Platforms
Tags
Our assessment of intelligence-collection-disciplines
intelligence-collection-disciplines scores 89/100 on our quality scale, 27th of 60 Product Management skills we index (top 45%).
Its SKILL.md is 26 KB long, well organised into 19 sections and no 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 intelligence-collection-disciplines is actively maintained.
- Our last check on 2026-10-31 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-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
intelligence-collection-disciplines compared with similar skills
All 4 of these similar skills score higher than intelligence-collection-disciplines; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| intelligence-collection-disciplines (this skill)by deanpeters | 89 | 7.1k | 3mo ago | SKILL.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 |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install intelligence-collection-disciplines?
- Run
npx skills add deanpeters/Product-Manager-Skills --skill intelligence-collection-disciplines. The install tabs above show the steps for each supported agent. - Which AI agents does intelligence-collection-disciplines 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 intelligence-collection-disciplines 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 intelligence-collection-disciplines still maintained?
- The repository was last updated about 3 months ago, so intelligence-collection-disciplines is actively maintained.
Skill content
View source on GitHubname: intelligence-collection-disciplines description: "Run competitive research like an intelligence agency: eight collection disciplines (OSINT to MASINT), signal-to-inference chains, and fusion. Use when one-source research isn't enough." intent: >- Give product managers the intelligence community's collection playbook: eight independent disciplines, each with free and paid sources, signal-to-inference chains, and the PM artifact it feeds — then fuse them with confidence stacking so three weak signals become one strong conclusion. type: component theme: market-intelligence best_for:
- "Choosing which collection channels to run for a competitive or market question"
- "Turning raw public signals (patents, job posts, filings, web diffs) into defensible inferences"
- "Cross-validating a suspected competitor move across independent evidence channels" scenarios:
- "I think a competitor is building a platform play — how do I confirm it before their launch?"
- "My TAM slide got shredded — where do I find data that survives scrutiny?" estimated_time: "reference skill; a single-discipline pass takes 30-60 min"
Intelligence Collection Disciplines
Purpose
Stop doing competitive research like a term paper. The intelligence community solved this problem decades ago: they don't collect "data," they run collection disciplines — independent channels, each with its own sources, tradecraft, and blind spots — and then they fuse them. This skill gives product managers that playbook: eight disciplines, each telling you (1) what to collect, (2) where to collect it, (3) which signal → inference chains to run, and (4) which PM artifact it feeds (TAM/SAM/SOM, ICPs, personas, battle cards, roadmap bets, win/loss, positioning, pricing). One signal is an anecdote; three correlated signals from independent disciplines is intelligence.
Input
Works best with the six instantiation variables below — fill them once and every discipline becomes engagement-specific. Leave them blank and this stays a teaching artifact.
[TARGET] = The competitor, partner, or acquirer you're researching
[MARKET] = The category and its NAICS/SIC/NACE codes (or nearest equivalent)
[GEOGRAPHY] = Regions in scope, at COUNTRY level, not continent level
[BUYER] = Who signs the check (drives review sites, job titles, conferences)
[CAPABILITY] = The strategic move you suspect (platform play, market entry,
pricing shift, compliance land-grab, etc.)
[DECISION] = What this research will change (roadmap bet, positioning,
pricing, market entry, deal defense, ICP refresh)
If [DECISION] is blank, stop. Research without a decision is a hobby.
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an
appended ARGUMENTS: line — counts as variables already filled. Use it; don't re-ask.
Arriving empty-handed? That works too. Read the disciplines as a course in tradecraft, or ask the agent to walk the instantiation block with you one variable at a time.
Example invocation: Use intelligence-collection-disciplines — [TARGET]: Meridian Freight Systems, [CAPABILITY]: suspected move into warehouse robotics, [DECISION]: whether we accelerate our own integration roadmap.
Key Concepts
The Eight Disciplines
| Discipline | Intel Community Name | Plain English | Primary PM Artifact | |---|---|---|---| | 1. OSINT | Open Source Intelligence | Press, social, periodicals, analysts | Battle cards, positioning | | 2. FININT | Financial Intelligence | Filings, earnings calls, procurement | Battle cards, SOM capture rates | | 3. GEOINT/DEMOINT | Geospatial & Demographic Intelligence | Census, labor, trade, economic statistics | TAM/SAM/SOM, ICPs, personas | | 4. TECHINT | Technical Intelligence | Patents, technographics, changelogs | Roadmap bets | | 5. HUMINT | Human Intelligence | Talent moves, employee chatter, win/loss | Roadmap bets, battle cards | | 6. SIGINT | Signals Intelligence | Web diffs, pricing changes, job posts | Battle cards, pricing strategy | | 7. MASINT | Measurement & Signature | Supply chain, ops indicators | Threat assessment | | 8. All-Source Fusion | n/a | Cross-validation and confidence stacking | Everything above |
- Independence is the design. The disciplines matter because they fail differently: a press release can lie, but a customs record, a patent filing, and thirty job posts are three separate bureaucracies that would all have to be lying in the same direction.
- Signal → inference chains are the tradecraft: each observable signal maps to a bounded
interpretation, labeled per the
autonomous-investigationprotocol (Fact / Inference / Assumption). - What this is NOT: espionage. Every source below is published, filed, posted, or publicly observable. See Guardrails in Common Pitfalls.
Application
1. OSINT — The Journalist's Desk
What a good beat reporter knows before the press release drops.
| Source Type | Free | Paid | |---|---|---| | [TARGET] press & newsroom | Company newsroom pages, Google Alerts, PR Newswire feeds | Meltwater, Cision | | Industry periodicals | Trade publications, association newsletters, vertical Substacks for [MARKET] | Analyst subscriptions | | Analyst coverage | Gartner/Forrester press summaries, free webinar replays | Gartner, Forrester, IDC full reports | | Social & community | LinkedIn exec posts, Reddit, Hacker News, X | Brandwatch, Sprout listening | | Review sites | Whichever your [BUYER] reads: G2, Capterra, TrustRadius, app stores, Trustpilot | G2 Buyer Intent data | | Conference footprint | Session titles, sponsor tiers, booth size, speaker rosters at [MARKET] events | n/a | | Prediction markets | Polymarket, Kalshi, Metaculus, Manifold (crowd-priced odds on regulation, approvals, tech milestones relevant to [MARKET]) | n/a |
Signal → inference chains:
- [TARGET] exec suddenly posting about a new problem space → positioning pivot incoming (execs test messaging on social 3-6 months before launch)
- Sponsor tier jump at a [MARKET] conference → market entry or doubling down
- Review complaints clustering on one feature → their roadmap pressure point = your battle card ammo
- Analyst briefing requests (visible via analyst posts) → category creation attempt
- Webinar topics shifting → what they're teaching the market is what they're about to sell
- Sudden silence on a product line → sunset in progress
- Prediction-market odds moving on a regulation or milestone that gates [MARKET] → crowd-priced expectations for scenario planning; treat as a leading indicator of consensus, not ground truth, and check liquidity before trusting the number
Feeds: battle cards (objection handling from review mining), positioning (their words vs. customer words gap), win/loss context.
2. FININT — The Forensic Accountant
Follow the money. Companies lie in press releases. They lie less in filings, because lying there is a felony.
| Source Type | Free | Paid | |---|---|---| | Public filings | SEC EDGAR (US), Companies House (UK), BRIS and European e-Justice company search (EU), national securities regulators for [GEOGRAPHY] | AlphaSense, Sentieo | | Earnings calls | Company IR pages, Seeking Alpha transcripts | AlphaSense (search across calls) | | Private company signals | Crunchbase free tier, incorporation records, insolvency registers, beneficial-ownership registers where legally accessible | PitchBook, CB Insights | | Government spend & procurement | USAspending.gov, SAM.gov (US), TED and national procurement portals (EU), country platforms (MENA), development-bank procurement (World Bank, EBRD, AfDB, UNGM) | GovWin | | Competition & state-aid cases | European Commission merger/antitrust/state-aid databases; national competition authorities | n/a | | State & sovereign capital | Sovereign wealth fund reports, state-owned enterprise annual reports, PPP pipelines | n/a |
Signal → inference chains:
- Risk Factors section changes year-over-year in an annual filing → what genuinely scares them (they must disclose it)
- Segment reporting restructure → strategic reprioritization; follow which segment got promoted
- Earnings call Q&A dodges (analysts ask, execs deflect) → soft spot; probe it in your positioning
- New entity registrations or branches in [GEOGRAPHY] → market entry before any announcement
- Deferred revenue trends → actual sales momentum vs. stated momentum
- Merger filings → market definitions and named competitors, straight from [TARGET]'s own lawyers
- Sovereign fund or state-aid money backing [TARGET] → their runway math just changed; discount-pressure plays won't work
- Prior Information Notices and expressions of interest → tenders telegraphed 3-24 months out
Feeds: battle cards (financial stress = "they'll be desperate at quarter-end" plays), SOM capture rates (their revenue ÷ claimed customer count = deal size reality check, feeding the GEOINT/DEMOINT sizing recipe), account targeting (procurement award patterns).
3. GEOINT/DEMOINT — The Cartographer
The terrain map, not troop movement. Government statistics are free intelligence most PMs never open — and the backbone of every ICP, persona, and TAM that survives scrutiny.
| Source Type | Free | Paid | |---|---|---| | US market structure | Census Bureau (County Business Patterns, Economic Census, NAICS establishment counts), BEA | IBISWorld, Statista, Grand View Research | | US labor & buyers | BLS (occupation counts, wages, industry employment), FRED (macro conditions gating budgets) | TalentNeuron | | EU market structure | Eurostat, PRODCOM manufacturing statistics, national statistical institutes, ECB data | national data resellers | | EU trade flows | Eurostat COMEXT, Access2Markets, TARIC (tariffs, quotas, rules of origin) | Panjiva, S&P Global | | MENA regional | GCC-Stat, Arab Development Portal, ESCWA, Arab Monetary Fund, SESRIC | n/a | | MENA national | GASTAT (Saudi), FCSC (UAE), CAPMAS (Egypt), HCP (Morocco), and peers | n/a | | Global cross-check | World Bank Data and Enterprise Surveys, IMF country reports, OECD.Stat, UN Comtrade, ITC Trade Map | n/a |
Signal → inference chains:
- Establishment counts by industry code and employee band → the denominator for bottom-up TAM
- Regional industry concentration → where your SOM actually lives, and where field sales should live
- Occupation growth curves for your [BUYER] roles → is the population you sell to growing or shrinking
- Wage trends in buyer roles → willingness-to-pay ceiling shifts; pricing corridor validation
- Firmographic distributions (size bands, legal forms, sectors) → ICP boundaries drawn from data, not vibes
- Buyer-title prevalence by [GEOGRAPHY] → persona localization; the "VP of Product" you message in Boston is a "Head of Digital" in Frankfurt and may not exist in Riyadh
- Trade-flow shifts in product-specific codes → market entry or supply relocation before any announcement
The TAM/SAM/SOM Recipe (this discipline's signature dish):
TAM: Establishment counts for [MARKET] (Census/NAICS, Eurostat/NACE,
or national equivalent for [GEOGRAPHY])
× employment/spend benchmarks (BLS, Eurostat, trade associations)
(validate against two independent analyst reports; if they disagree by 3x, say so)
SAM: TAM filtered by your actual constraints: [GEOGRAPHY], segment, compliance
requirements, tech prerequisites (see TECHINT technographics),
local-content and vendor-registration eligibility where applicable
SOM: SAM × realistic capture rate derived from [TARGET] public filings via FININT
(their revenue ÷ their claimed customer count = deal size reality check)
Feeds: TAM/SAM/SOM (the backbone — see tam-sam-som-calculator), ICP definition, personas,
messaging localization, market entry prioritization, pricing corridor validation.
4. TECHINT — The Patent Examiner
*R&D leaves finger
Truncated for display — read the full file on GitHub.
Related Skills
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…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
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.
