Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Refresh the user's competitive and market context. Re-scan named rivals and the category for what changed since the brief was written (rebrands, repositioning, new entrants, pricing shifts, renamed categories) and update docs/gtm-cofounder/founder-brief.md and the roadmap with anything that moves positioning. Use on a cadence, or whenever a competitor rebrands, a new tool appears, or the user senses the market has shifted under them.
.claude/skills/aidevgtm-market-scan/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | 48% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 41% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 62% | 0% |
| case-10 | ✗→✓ | ▲ Improved | 18% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 40% | 0% |
> Positioning rots. The competitor you sized up six months ago has since rebranded, raised, repriced, or renamed the category. This is the habit that keeps your brief honest about the world outside it.
Use this when: a rival just rebranded or repositioned, a new tool is getting attention in your space, your docs/gtm-cofounder/founder-brief.md competitor answers are more than a quarter old, or you just have the feeling the ground moved and your messaging is answering last year's market.
Your docs/gtm-cofounder/founder-brief.md captured the market as it was the day you wrote it. Markets don't hold still. A scan re-checks the outside world against your brief and surfaces the deltas: what changed, and which changes actually threaten or help your positioning. Most don't matter. The scan's job is to find the two or three that do, not to produce a competitor spreadsheet.
docs/gtm-cofounder/founder-brief.md: the rivals ("what do they use instead"), the "why you", the villain, and the current positioning line. That's your baseline to compare against.positioning-and-story. A new pricing norm means revisit market-to-devs-sell-to-buyers. A dead competitor means an opening. No action, no reason to flag it.docs/gtm-cofounder/founder-brief.md (rivals, why-you, villain, positioning) with today's reality and the date, and add any positioning move it triggers to docs/gtm-cofounder/gtm-roadmap.md. Keep the tags honest: a competitor's public claim is [assumption] until you have checked it is real.Changes worth acting on:
Noise to ignore:
[assumption].docs/gtm-cofounder/founder-brief.md. Scan each for a rebrand, repricing, or repositioning since you wrote it.docs/gtm-cofounder/founder-brief.md (with the date) and add any positioning move to docs/gtm-cofounder/gtm-roadmap.md.Built from real dev-tool GTM experience, with frameworks from Adam Frankl (The Developer-Facing Startup) and Jakub Czakon (markepear.dev). When a framework can't make the call, that's what a human is for: The DevTool GTM Company.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 8,797 | 9,810 | +12% | 1 | 1 | 0% | 1,197 | 1,686 | +41% | 0 | 0 | — |
case-02 | fail→fail | 7,475 | 10,472 | +40% | 1 | 1 | 0% | 1,128 | 2,632 | +133% | 0 | 0 | — |
case-03 | pass→fail | 22,647 | 22,809 | +1% | 1 | 1 | 0% | 3,318 | 4,286 | +29% | 0 | 0 | — |
case-04 | pass→pass | 14,020 | 16,920 | +21% | 1 | 1 | 0% | 2,122 | 3,657 | +72% | 0 | 0 | — |
case-05 | pass→pass | 30,852 | 18,002 | -42% | 1 | 1 | 0% | 2,604 | 3,562 | +37% | 0 | 0 | — |
case-06 | fail→pass | 16,095 | 16,713 | +4% | 1 | 1 | 0% | 2,173 | 3,214 | +48% | 0 | 0 | — |
case-07 | fail→pass | 16,037 | 11,931 | -26% | 1 | 1 | 0% | 2,064 | 2,904 | +41% | 0 | 0 | — |
case-08 | pass→pass | 12,690 | 9,246 | -27% | 1 | 1 | 0% | 1,873 | 2,507 | +34% | 0 | 0 | — |
case-09 | fail→pass | 12,978 | 13,456 | +4% | 1 | 1 | 0% | 1,822 | 2,955 | +62% | 0 | 0 | — |
case-10 | fail→pass | 15,484 | 10,216 | -34% | 1 | 1 | 0% | 2,243 | 2,656 | +18% | 0 | 0 | — |
case-11 | fail→pass | 12,649 | 9,768 | -23% | 1 | 1 | 0% | 1,806 | 2,528 | +40% | 0 | 0 | — |
case-12 | fail→fail | 13,754 | 13,540 | -2% | 1 | 1 | 0% | 2,138 | 3,092 | +45% | 0 | 0 | — |
case-13 | fail→pass | 19,575 | 11,551 | -41% | 1 | 1 | 0% | 2,527 | 2,798 | +11% | 0 | 0 | — |
case-14 | fail→fail | 7,145 | 7,479 | +5% | 1 | 1 | 0% | 935 | 2,186 | +134% | 0 | 0 | — |
case-15 | fail→pass | 8,150 | 8,395 | +3% | 1 | 1 | 0% | 1,126 | 2,447 | +117% | 0 | 0 | — |
case-16 | fail→pass | 36,677 | 12,705 | -65% | 1 | 1 | 0% | 5,112 | 2,921 | -43% | 0 | 0 | — |
case-17 | fail→pass | 14,771 | 9,958 | -33% | 1 | 1 | 0% | 2,402 | 2,701 | +12% | 0 | 0 | — |
case-18 | fail→fail | 17,949 | 19,085 | +6% | 1 | 1 | 0% | 2,526 | 3,579 | +42% | 0 | 0 | — |
case-19 | fail→pass | 4,042 | 4,620 | +14% | 1 | 1 | 0% | 360 | 1,786 | +396% | 0 | 0 | — |
case-20 | fail→pass | 18,701 | 18,405 | -2% | 1 | 1 | 0% | 2,656 | 3,848 | +45% | 0 | 0 | — |
case-21 | fail→pass | 3,495 | 6,161 | +76% | 1 | 1 | 0% | 400 | 1,927 | +382% | 0 | 0 | — |
case-22 | fail→fail | 13,107 | 4,269 | -67% | 1 | 1 | 0% | 1,719 | 1,840 | +7% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 21 counted toward the lift figure. The other 1 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +50 percentage points is the difference between those two pass rates over the 21 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.