market-research
Market-research conducts competitive analysis, market sizing, and investor due diligence with sourced evidence and decision-oriented recommendations. Activate it when evaluating market opportunities, comparing competitors, vetting investors before outreach, building TAM estimates, or pressure-testing business theses. The skill emphasizes fact-based findings over marketing narratives, flags stale data, includes contrarian evidence, and translates research into actionable decisions rather than summaries alone.
git clone --depth 1 https://github.com/affaan-m/ECC /tmp/market-research && cp -r /tmp/market-research/.cursor/skills/market-research ~/.claude/skills/market-researchSKILL.md
# Market Research Produce research that supports decisions, not research theater. ## When to Activate - researching a market, category, company, investor, or technology trend - building TAM/SAM/SOM estimates - comparing competitors or adjacent products - preparing investor dossiers before outreach - pressure-testing a thesis before building, funding, or entering a market ## Research Standards 1. Every important claim needs a source. 2. Prefer recent data and call out stale data. 3. Include contrarian evidence and downside cases. 4. Translate findings into a decision, not just a summary. 5. Separate fact, inference, and recommendation clearly. ## Common Research Modes ### Investor / Fund Diligence Collect: - fund size, stage, and typical check size - relevant portfolio companies - public thesis and recent activity - reasons the fund is or is not a fit - any obvious red flags or mismatches ### Competitive Analysis Collect: - product reality, not marketing copy - funding and investor history if public - traction metrics if public - distribution and pricing clues - strengths, weaknesses, and positioning gaps ### Market Sizing Use: - top-down estimates from reports or public datasets - bottom-up sanity checks from realistic customer acquisition assumptions - explicit assumptions for every leap in logic ### Technology / Vendor Research Collect: - how it works - trade-offs and adoption signals - integration complexity - lock-in, security, compliance, and operational risk ## Output Format Default structure: 1. executive summary 2. key findings 3. implications 4. risks and caveats 5. recommendation 6. sources ## Quality Gate Before delivering: - all numbers are sourced or labeled as estimates - old data is flagged - the recommendation follows from the evidence - risks and counterarguments are included - the output makes a decision easier
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
>
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
>
Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
>