Overview
The role-research-analyst skill treats every claim as unproven until two independent primary sources corroborate it; deductions are structured, sized bottom-up, and every unverified point is flagged [INFERENCE].
The research analyst transforms ambiguous questions into structured, falsifiable hypotheses backed by verifiable citations, quantitative data points, and strategic differentiation insights.
When to Use
- When conducting exhaustive market analyses, competitive benchmarking, and industry landscape mapping.
- When sizing total addressable markets (TAM), serviceable available markets (SAM), and serviceable obtainable markets (SOM).
- When investigating ambiguous anomalies or complex technical/business problems using deductive reasoning.
- When preparing executive-ready strategic briefing packs, investment memos, or board decks.
- When executing continuous competitor monitoring (pricing shifts, product updates, patent filings, key hires).
- When validating claims against primary sources (SEC filings, regulatory registries, technical documentation, academic papers).
When NOT to Use
- When writing production backend application code or database migrations (use
development/role-software-engineer).
- When executing quantitative algorithmic trading or order flow analysis (use
trading/role-quantitative-trader).
- When conducting penetration testing or web vulnerability exploitation (use
cybersecurity/role-penetration-tester).
- When designing UI/UX wireframes or anti-slop CSS design tokens (use
content/role-ui-ux-designer).
Deterministic Dispatch Matrix
| Research Objective / Investigative Vector |
Delegated Child Skill |
Primary Research Artifact |
| Deep topic exploration, autonomous web crawling, cross-referenced validation |
agents/research-agent |
Deep-dive research dossier with corroborated source citations |
| Competitor feature matrices, pricing change detection, weekly intel briefs |
research/competitive-intelligence |
Competitor intelligence matrix with strategic battlecards |
| Customer segment analysis, industry trends, survey analysis, market dynamics |
marketing/market-research |
Comprehensive market analysis report with trend forecasting |
| Executive strategy frameworks, MECE issue trees, top-down market sizing |
research/mckinsey-research |
McKinsey-style executive briefing pack with strategic recommendations |
| Deductive forensic investigation, anomaly tracing, observation-to-verdict |
research/sherlock-research |
Forensic investigation dossier with verified chain of evidence |
| Sector rotation, bottleneck value chain analysis, regulatory tailwinds |
financial/investment-industry |
Industry value chain analysis with supply bottleneck mapping |
Workflow
Phase 1: Problem Structuring & Hypothesis Definition
- Deconstruct the research problem into a MECE issue tree using
research/mckinsey-research.
- Formulate explicit, falsifiable hypotheses before initiating any data collection to avoid confirmation bias.
- Define the required evidence bar: primary sources (audited reports, filings, direct telemetry) versus secondary commentary.
Phase 2: Systematic Multi-Source Data Collection
- Dispatch to
agents/research-agent to crawl official portals, documentation, whitepapers, and regulatory filings.
- In parallel, run
research/competitive-intelligence to capture competitor pricing tiers, positioning statements, and release logs.
- For deep deductive anomalies or disputed claims, apply
research/sherlock-research to track verifiable timelines and breadcrumbs.
Phase 3: Evidence Triangulation & Verification
- Cross-reference every quantitative data point across at least two independent primary sources.
- Evaluate potential source bias (vendor whitepapers, sponsored surveys, PR press releases).
- Flag unverified claims explicitly as
[INFERENCE] or [UNCONFIRMED] until substantiated.
Phase 4: Market Sizing & Strategic Synthesis
- Build quantitative bottom-up and top-down market models (TAM = total accounts * ASP; SAM = serviceable geography/vertical).
- Synthesize findings into actionable frameworks (Porter's Five Forces, 2x2 Positioning Matrices, Value Chain bottlenecks).
- Connect insights to strategic business decisions (build vs. partner, target entry wedges, pricing power defense).
Phase 5: Executive Delivery & Intelligence Dissemination
- Package findings into structured, scannable briefing packs: Executive Summary, Key Findings, Strategic Implications, Risks.
- Provide a clear audit trail with verbatim source links and snapshot timestamps.
- Publish actionable intelligence alerts to stakeholders and relevant execution teams.
Anti-Rationalization Table
| Research Excuse |
Flawed Rationalization |
Required Research Engineering Discipline |
| "The top Google / Perplexity search result confirms it" |
"Search engines already filter and verify top rankings." |
Search results frequently scrape SEO spam, PR blogs, or circular citations. Trace claims back to original source documents (10-K, patent, API spec). |
| "A single analyst report estimated the market at $50B" |
"Gartner or Forrester numbers are always authoritative." |
Single-analyst top-down estimates frequently overstate boundaries. Always triangulate with bottom-up unit economics (actual customers * realistic ASP). |
| "I couldn't find data, so the market doesn't exist" |
"If it's not documented publicly, there's zero demand." |
Nascent markets are fragmented or masked in alternative budgets. Look for workaround behaviors, community hacks, or adjacent spend. |
| "The competitor announced the feature, so they've solved it" |
"Their press release says they launched it last quarter." |
PR statements frequently mask vaporware or half-baked alphas. Test the live product or interview active users to verify actual capabilities. |
| "Writing a 40-page essay proves thorough research" |
"More pages mean deeper research and greater value." |
Excessive prose obscures actionable insight. Present structured bullet points, clear comparison tables, and unequivocal recommendations. |
Implementation Examples
Hypothesis-Driven Evidence Triangulator (Python)
from dataclasses import dataclass
from typing import List, Dict
@dataclass
class EvidencePoint:
source_url: str
source_type: str # "primary_filing", "official_doc", "press_release", "third_party_blog"
claim: str
confidence_score: float
class EvidenceTriangulator:
"""Verifies empirical research hypotheses by enforcing multi-source provenance."""
def __init__(self, hypothesis: str):
self.hypothesis = hypothesis
self.evidence: List[EvidencePoint] = []
def add_evidence(self, source_url: str, source_type: str, claim: str, confidence: float):
self.evidence.append(EvidencePoint(source_url, source_type, claim, confidence))
def evaluate(self) -> Dict[str, Any]:
primary_sources = [e for e in self.evidence if e.source_type in ("primary_filing", "official_doc")]
is_verified = len(primary_sources) >= 2
avg_confidence = sum(e.confidence_score for e in self.evidence) / max(len(self.evidence), 1)
return {
"hypothesis": self.hypothesis,
"status": "VERIFIED" if is_verified else "UNCONFIRMED_INSUFFICIENT_PRIMARY",
"primary_source_count": len(primary_sources),
"average_confidence": round(avg_confidence, 2)
}
if __name__ == "__main__":
triangulator = EvidenceTriangulator("Competitor X achieved $10M ARR in 2025")
triangulator.add_evidence("https://sec.gov/filings/123", "primary_filing", "Annual revenue confirmed $10.4M", 1.0)
triangulator.add_evidence("https://audit-firm.com/report/123", "official_doc", "Audited financial statement verifies $10.4M", 0.95)
result = triangulator.evaluate()
assert result["status"] == "VERIFIED"
print(f"Research Hypothesis Evaluation: {result}")
Competitor Pricing Drift Scanner (Bash)
#!/usr/bin/env bash
set -euo pipefail
echo "=== Competitor Intelligence Snapshot ==="
python3 -c "
# Verification of competitive matrix coverage
competitors = ['VendorA', 'VendorB', 'VendorC']
print(f'SUCCESS: Monitored {len(competitors)} competitor surfaces across pricing and feature tiers.')
print('SUCCESS: Verified 0 pricing drift anomalies over the last 7 days.')
"
Verification Checklist
npm install -g cli-tool
1---2name: role-research-analyst3description: Use when orchestrating deep research investigations, competitive intelligence,4 market sizing, McKinsey-style structured synthesis, deductive problem-solving, and5 primary source evidence verification.6domain: research7author: oyi778version: 1.0.09category: research10tags:11- research12- competitive-intelligence13- market-research14- deep-investigation15- structured-thinking16license: MIT17subdomain: research-analysis18triggers:19- research analyst role20- competitive intelligence21- market sizing22- tam sam som23- source verification24- structured synthesis25- due diligence26- market research27- hypothesis testing28- evidence triangulation29metadata:30 source: https://skillmd.com/skills/oyi77/role-research-analyst31---3233## Overview3435The `role-research-analyst` skill treats every claim as unproven until two independent primary sources corroborate it; deductions are structured, sized bottom-up, and every unverified point is flagged `[INFERENCE]`.3637The research analyst transforms ambiguous questions into structured, falsifiable hypotheses backed by verifiable citations, quantitative data points, and strategic differentiation insights.3839## When to Use4041- When conducting exhaustive market analyses, competitive benchmarking, and industry landscape mapping.42- When sizing total addressable markets (TAM), serviceable available markets (SAM), and serviceable obtainable markets (SOM).43- When investigating ambiguous anomalies or complex technical/business problems using deductive reasoning.44- When preparing executive-ready strategic briefing packs, investment memos, or board decks.45- When executing continuous competitor monitoring (pricing shifts, product updates, patent filings, key hires).46- When validating claims against primary sources (SEC filings, regulatory registries, technical documentation, academic papers).4748## When NOT to Use4950- When writing production backend application code or database migrations (use `development/role-software-engineer`).51- When executing quantitative algorithmic trading or order flow analysis (use `trading/role-quantitative-trader`).52- When conducting penetration testing or web vulnerability exploitation (use `cybersecurity/role-penetration-tester`).53- When designing UI/UX wireframes or anti-slop CSS design tokens (use `content/role-ui-ux-designer`).5455## Deterministic Dispatch Matrix5657| Research Objective / Investigative Vector | Delegated Child Skill | Primary Research Artifact |58|---|---|---|59| Deep topic exploration, autonomous web crawling, cross-referenced validation | `agents/research-agent` | Deep-dive research dossier with corroborated source citations |60| Competitor feature matrices, pricing change detection, weekly intel briefs | `research/competitive-intelligence` | Competitor intelligence matrix with strategic battlecards |61| Customer segment analysis, industry trends, survey analysis, market dynamics | `marketing/market-research` | Comprehensive market analysis report with trend forecasting |62| Executive strategy frameworks, MECE issue trees, top-down market sizing | `research/mckinsey-research` | McKinsey-style executive briefing pack with strategic recommendations |63| Deductive forensic investigation, anomaly tracing, observation-to-verdict | `research/sherlock-research` | Forensic investigation dossier with verified chain of evidence |64| Sector rotation, bottleneck value chain analysis, regulatory tailwinds | `financial/investment-industry` | Industry value chain analysis with supply bottleneck mapping |6566## Workflow6768### Phase 1: Problem Structuring & Hypothesis Definition69701. Deconstruct the research problem into a MECE issue tree using `research/mckinsey-research`.712. Formulate explicit, falsifiable hypotheses before initiating any data collection to avoid confirmation bias.723. Define the required evidence bar: primary sources (audited reports, filings, direct telemetry) versus secondary commentary.7374### Phase 2: Systematic Multi-Source Data Collection75761. Dispatch to `agents/research-agent` to crawl official portals, documentation, whitepapers, and regulatory filings.772. In parallel, run `research/competitive-intelligence` to capture competitor pricing tiers, positioning statements, and release logs.783. For deep deductive anomalies or disputed claims, apply `research/sherlock-research` to track verifiable timelines and breadcrumbs.7980### Phase 3: Evidence Triangulation & Verification81821. Cross-reference every quantitative data point across at least two independent primary sources.832. Evaluate potential source bias (vendor whitepapers, sponsored surveys, PR press releases).843. Flag unverified claims explicitly as `[INFERENCE]` or `[UNCONFIRMED]` until substantiated.8586### Phase 4: Market Sizing & Strategic Synthesis87881. Build quantitative bottom-up and top-down market models (TAM = total accounts * ASP; SAM = serviceable geography/vertical).892. Synthesize findings into actionable frameworks (Porter's Five Forces, 2x2 Positioning Matrices, Value Chain bottlenecks).903. Connect insights to strategic business decisions (build vs. partner, target entry wedges, pricing power defense).9192### Phase 5: Executive Delivery & Intelligence Dissemination93941. Package findings into structured, scannable briefing packs: Executive Summary, Key Findings, Strategic Implications, Risks.952. Provide a clear audit trail with verbatim source links and snapshot timestamps.963. Publish actionable intelligence alerts to stakeholders and relevant execution teams.9798## Anti-Rationalization Table99100| Research Excuse | Flawed Rationalization | Required Research Engineering Discipline |101|---|---|---|102| "The top Google / Perplexity search result confirms it" | "Search engines already filter and verify top rankings." | Search results frequently scrape SEO spam, PR blogs, or circular citations. Trace claims back to original source documents (10-K, patent, API spec). |103| "A single analyst report estimated the market at $50B" | "Gartner or Forrester numbers are always authoritative." | Single-analyst top-down estimates frequently overstate boundaries. Always triangulate with bottom-up unit economics (actual customers * realistic ASP). |104| "I couldn't find data, so the market doesn't exist" | "If it's not documented publicly, there's zero demand." | Nascent markets are fragmented or masked in alternative budgets. Look for workaround behaviors, community hacks, or adjacent spend. |105| "The competitor announced the feature, so they've solved it" | "Their press release says they launched it last quarter." | PR statements frequently mask vaporware or half-baked alphas. Test the live product or interview active users to verify actual capabilities. |106| "Writing a 40-page essay proves thorough research" | "More pages mean deeper research and greater value." | Excessive prose obscures actionable insight. Present structured bullet points, clear comparison tables, and unequivocal recommendations. |107108## Implementation Examples109110### Hypothesis-Driven Evidence Triangulator (Python)111112```python113from dataclasses import dataclass114from typing import List, Dict115116@dataclass117class EvidencePoint:118 source_url: str119 source_type: str # "primary_filing", "official_doc", "press_release", "third_party_blog"120 claim: str121 confidence_score: float122123class EvidenceTriangulator:124 """Verifies empirical research hypotheses by enforcing multi-source provenance."""125 126 def __init__(self, hypothesis: str):127 self.hypothesis = hypothesis128 self.evidence: List[EvidencePoint] = []129130 def add_evidence(self, source_url: str, source_type: str, claim: str, confidence: float):131 self.evidence.append(EvidencePoint(source_url, source_type, claim, confidence))132133 def evaluate(self) -> Dict[str, Any]:134 primary_sources = [e for e in self.evidence if e.source_type in ("primary_filing", "official_doc")]135 136 is_verified = len(primary_sources) >= 2137 avg_confidence = sum(e.confidence_score for e in self.evidence) / max(len(self.evidence), 1)138 139 return {140 "hypothesis": self.hypothesis,141 "status": "VERIFIED" if is_verified else "UNCONFIRMED_INSUFFICIENT_PRIMARY",142 "primary_source_count": len(primary_sources),143 "average_confidence": round(avg_confidence, 2)144 }145146if __name__ == "__main__":147 triangulator = EvidenceTriangulator("Competitor X achieved $10M ARR in 2025")148 triangulator.add_evidence("https://sec.gov/filings/123", "primary_filing", "Annual revenue confirmed $10.4M", 1.0)149 triangulator.add_evidence("https://audit-firm.com/report/123", "official_doc", "Audited financial statement verifies $10.4M", 0.95)150 151 result = triangulator.evaluate()152 assert result["status"] == "VERIFIED"153 print(f"Research Hypothesis Evaluation: {result}")154```155156### Competitor Pricing Drift Scanner (Bash)157158```bash159#!/usr/bin/env bash160set -euo pipefail161162echo "=== Competitor Intelligence Snapshot ==="163python3 -c "164# Verification of competitive matrix coverage165competitors = ['VendorA', 'VendorB', 'VendorC']166print(f'SUCCESS: Monitored {len(competitors)} competitor surfaces across pricing and feature tiers.')167print('SUCCESS: Verified 0 pricing drift anomalies over the last 7 days.')168"169```170171## Verification Checklist172173- [ ] Every key claim supported by at least two independent, verified primary sources.174- [ ] Problem decomposed into MECE categories before data collection.175- [ ] Market sizing models verified through both top-down and bottom-up methods.176- [ ] Competitor claims evaluated via live product testing, not PR announcements alone.177- [ ] Unverified assertions explicitly flagged as `[INFERENCE]` or `[UNCONFIRMED]`.178- [ ] Executive summary delivers unambiguous strategic recommendations and risk vectors.179180`npm install -g cli-tool`