Ports functionality from 10+ separate plugins into ECC so users only need one plugin installed. Consolidates: pr-review-toolkit, feature-dev, commit-commands, hookify, code-simplifier, security-guidance, frontend-design, explanatory-output-style, and personal skills. New agents (8): code-architect, code-explorer, code-simplifier, comment-analyzer, conversation-analyzer, pr-test-analyzer, silent-failure-hunter, type-design-analyzer New commands (9): commit, commit-push-pr, clean-gone, review-pr, feature-dev, hookify, hookify-list, hookify-configure, hookify-help New skills (8): frontend-design, hookify-rules, github-ops, knowledge-ops, lead-intelligence, oura-health, pmx-guidelines, remotion Enhanced skills (8): article-writing, content-engine, market-research, investor-materials, investor-outreach, x-api, security-scan, autonomous-loops — merged with personal skill content New hook: security-reminder.py (pattern-based OWASP vulnerability warnings on file edits) Totals: 36 agents, 69 commands, 128 skills, 29 hook scripts
3.6 KiB
name, description, origin
| name | description | origin |
|---|---|---|
| market-research | Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Use when the user wants market sizing, competitor comparisons, fund research, technology scans, or research that informs business decisions. | ECC |
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
- Every important claim needs a source.
- Prefer recent data and call out stale data.
- Include contrarian evidence and downside cases.
- Translate findings into a decision, not just a summary.
- 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:
- executive summary
- key findings
- implications
- risks and caveats
- recommendation
- sources
Domain-Specific Research Context
When researching specific verticals, collect domain-specific signals:
Prediction Markets
Key metrics: Volume, open interest, user count, market categories Regulatory landscape: CFTC (US), FCA (UK), global patchwork Key players: Polymarket, Kalshi, Robinhood (event contracts), Metaculus, Manifold
DeFi / Structured Products
Key concepts: Vaults, exotic options, baskets, LP positions, DLMM Key players: Cega, Ribbon Finance, Opyn, OrBit Markets Chain-specific context matters (Solana vs Ethereum vs L2s)
AI Agent Security
Key concepts: Agent permissions, tool poisoning, prompt injection, OWASP LLM Top 10 Key players: Invariant Labs, Backslash, Dam Secure, Cogent Security, Entire, Pillar Security
General Research Practices
- For investor due diligence: produce a 200-300 word dossier with fund overview, relevant investments, thesis alignment, suggested angle, and red flags
- For competitive analysis: always include "so what" for each finding relative to the user's venture
- For market sizing: follow TAM/SAM/SOM with explicit growth rate (CAGR with source), key drivers, and key risks
- For technology research: cover architecture (not marketing), trade-offs, adoption signals (GitHub stars, npm downloads, TVL if DeFi), and integration complexity
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
- no filler paragraphs or generic market commentary
- contrarian/risk perspective explicitly included