qte77/researching-market
plugins/market-research/skills/researching-market/SKILL.md
Integrate Phase 0 and Phase 1A outputs into TAM/SAM/SOM sizing, buyer personas, and market entry signals. Run after `analyzing-source-project` and `researching-industry-landscape` (Phase 1B).
$ install --global
skillsauthnpx skillsauth add qte77/claude-code-plugins researching-marketInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 28, 2026, 6:50 AM129.7s1 file scanned
SKILL.md
- name:
- researching-market
- description:
- Integrate Phase 0 and Phase 1A outputs into TAM/SAM/SOM sizing, buyer personas, and market entry signals. Run after `analyzing-source-project` and `researching-industry-landscape` (Phase 1B).
- compatibility:
- Designed for Claude Code
- stability:
- development
- allowed-tools:
- Read, Write, Glob, Grep, WebSearch, WebFetch, Agent
- argument-hint:
- [market-or-product-category]
Researching Market (Phase 1B)
Target: $ARGUMENTS
Phase 1B of the GTM pipeline. Depends on Phase 0 and Phase 1A. Integrates technical capability and competitive intelligence into strategic market sizing and buyer analysis.
Mode Awareness
Read config/mode.md before starting:
concise— Top-down TAM estimate, one primary persona, bullet entry signalsdetailed— Bottom-up + top-down sizing, 2-3 personas with full profiles, trend projectionsconservative— Use published analyst figures, conservative growth ratesambitious— Build bottom-up case for expansive TAM, highlight adjacencies
Inputs
results/phase-0/capability-profile.md— Source project capabilitiesresults/phase-1a/competitor-map.md— Competitive landscapeconfig/targets.md— Target market segmentsconfig/comments_research.md— Research scope constraintsconfig/mode.md— Style and approach settings
Workflow
- Read Phase 0 and Phase 1A outputs — Synthesize capability and competitive signals
- Define addressable market — Scope TAM, SAM, SOM with methodology
- Size the market — Use cited sources; state assumptions explicitly
- Build buyer personas — Role, pain points, budget authority, buying triggers
- Assess entry signals — What evidence suggests this is the right moment to enter?
- Identify risks — Market timing, regulatory, adoption barriers
- Validate against criteria — Check
config/validation_criteria.mdPhase 1B gates
Output
Write to results/phase-1b/:
market-analysis.md
# Market Analysis
## Market Sizing
### TAM (Total Addressable Market)
- Estimate: $[X]B
- Methodology: [top-down / bottom-up]
- Source: [URL, year]
### SAM (Serviceable Addressable Market)
- Estimate: $[X]B
- Scope: [geography, segment, use case]
### SOM (Serviceable Obtainable Market — Year 1-3)
- Estimate: $[X]M
- Assumptions: [list]
## Growth Rate
- [X]% CAGR through [year] — Source: [URL]
## Buyer Personas
### Persona: [Name/Role]
- Title: [job title]
- Pain: [primary pain point]
- Budget authority: [Yes/No/Influence]
- Buying trigger: [what prompts purchase decision]
## Market Entry Signals
- [Signal] — Strength: [High/Medium/Low]
## Risks
- [Risk] — Likelihood: [H/M/L] — Mitigation: [approach]
Rules
- Explicitly state all sizing assumptions — no unexplained numbers
- Every market size figure must have a source and year
- Personas must be grounded in target segments from
config/targets.md - Integrate Phase 0 capability signals into entry signal rationale
Related Skills
qte77/writing-readme
documentation
VerifiedTrustedCommunity
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
1SKILL.mdUpdated Apr 19, 2026
qte77/auditing-readme
development
VerifiedTrustedCommunity
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.
1SKILL.mdUpdated Apr 19, 2026
qte77/researching-website-design
development
VerifiedTrustedCommunity
Analyzes industry websites for design patterns, layout, typography, and content strategies using first-principles thinking. Use when researching website design, UI patterns, or competitive design analysis.
1SKILL.mdUpdated Apr 18, 2026
qte77/auditing-website-usability
development
VerifiedTrustedCommunity
Audits website usability for UX optimization, covering forms, navigation, validation, and microcopy. Use when reviewing user experience, task completion flows, or interface friction points.
1SKILL.mdUpdated Apr 18, 2026