davepoon/buildwithclaude / plugins/all-skills/skills/competitor-research
competitor-research
VerifiedResearch competitor products, launch history, and acquisition evidence from public sources or supplied materials. Use when evaluating growth claims, comparing competitors, or choosing growth experiments. Produces a cited brief that separates observations, attributed claims, estimates, and hypotheses.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.1 KB |
| SKILL.md | skill md | 6.7 KB |
| references/evidence.md | markdown | 3.1 KB |
| references/report-template.md | markdown | 1.0 KB |
references/report-template.md
View on GitHub# Competitor brief structure
Adapt length to the task. Omit empty sections rather than padding the report.
1. **Finding and scope:** domain/product, research question, user's context, as-of date, public-web or supplied-materials mode.
2. **Product and business model:** audience, task, positioning, price/unit, free-to-paid boundary, sources and dates.
3. **Timeline:** event date, event, source, what it proves, uncertainty. Earliest observed activity is not founding.
4. **Channel evidence:** channel, observed asset/activity, traffic or conversion evidence if available, what remains unknown.
5. **Experiments:** up to three, each grounded in a cited observation, with hypothesis, prerequisites, small test, success measure and review/stop condition.
6. **Gaps:** unresolved claims and the smallest additional evidence needed. Explicitly distinguish unobserved from absent.
Keep citations near claims. Use clear labels for company claims and provider estimates. A short complete brief with honest gaps is better than an unsupported exhaustive report.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |