Skip to content
cccskills
FreePublished on GitHub

market-scan

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.

The English summary is being prepared. Showing the original description.

Works withLinkedIn

Run score Not tested

See how to install

Files included (1)

  • SKILL.md5.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Market scan (keep your read current)

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.

The core idea

research-the-market is the first full pass on the market: venues, launches, the problem in public, rivals, openings. This skill is the refresh after that, focused on what changed.

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.

Before you start: can your agent see the web?

  • If your agent can browse or search the web, it runs the scan for real: competitor homepages, changelogs, pricing pages, launch posts, and recent discussion.
  • If it can't, it runs the scan as an interview: it asks what you've noticed and where, and you paste in the pages. Same output, you're the browser. Say which mode you're in up front.

How to run this (for the agent)

  • Start from the brief. Read 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.
  • Scan the named rivals first, then the category. For each competitor in the brief, check: homepage headline and positioning, pricing, any rebrand or renamed category, funding or acquisition, and new capabilities that erase the founder's wedge. Then scan for new entrants and category-level shifts (a term everyone suddenly uses, a platform move, an AI or agent shift).
  • Report deltas, not descriptions. Do not summarize each competitor. Say what changed since the brief, and for each change, whether it strengthens, threatens, or is irrelevant to the founder's positioning. Rank by "does this move our position."
  • Tie every real change to an action. A rival adopting the founder's language means the wedge is eroding: route to 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.
  • Update the brief and roadmap. Rewrite the affected lines in 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.

What actually matters (and what doesn't)

Changes worth acting on:

  • A rival repositions onto your wedge or adopts your vocabulary. Your differentiation is eroding. Highest priority.
  • A new entrant is getting real traction in your exact lane.
  • The category gets renamed (buyers now search a different term than your copy uses).
  • A pricing norm shifts (a free tier appears or disappears, seat pricing becomes standard).

Noise to ignore:

  • Cosmetic rebrands, new logos, homepage redesigns with the same substance.
  • Feature announcements that don't touch your wedge.
  • Funding rounds that don't change what the product is or who it is for.

Mistakes that look reasonable

  • Reacting to a competitor's launch by copying it. Their move fits their strategy, not yours. Ask what it means for your wedge, not how to match it.
  • Scanning everything, changing nothing. A scan that doesn't update the brief or the roadmap was just anxiety with extra steps.
  • Treating a rival's marketing claim as fact. "Now with X" on a homepage is a positioning bet, not proof it works. Tag it [assumption].
  • Doing it constantly. Monthly, or on a real trigger (a rebrand, a new entrant), is plenty. Daily competitor-watching is procrastination dressed as diligence.

Your next 30 minutes

  • Tell your agent which mode you're in (it browses, or you paste).
  • List the rivals from your docs/gtm-cofounder/founder-brief.md. Scan each for a rebrand, repricing, or repositioning since you wrote it.
  • Write down only the changes that touch your wedge. Ignore the cosmetic ones.
  • For each real change, mark it strengthens / threatens / irrelevant, and the one action it triggers.
  • Update the affected lines in 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). If the market has shifted under you and you're not sure what it means for positioning, reach out to me on LinkedIn.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Position an AI product when everyone claims AI and skeptics call it "just a wrapper." Find the real wedge (data, workflow, trust, domain), make reliability the differentiator, answer "won't the big labs just build this," and stop leading with "AI-powered." Use when your AI or dev tool blends into a sea of similar demos, buyers doubt the accuracy, or you can't say why you win when the model is a commodity.

The English summary is being prepared. Showing the original description.

AIDevGTM/gtm-cofounder324Updated Oct 19, 2026

Get the first 50 real users through channels the user's ICP already uses. Use when the product shipped and nobody came, the user is "posting more" with no result, or is reaching for paid ads before product-market fit.

The English summary is being prepared. Showing the original description.

AIDevGTM/gtm-cofounder324Updated Oct 19, 2026

Build authority by teaching the problem space, not announcing features. Use when the user finds "marketing" distasteful and does none, publishes only product updates, or wants a sustainable content and GitHub-README strategy that developers actually respect.

The English summary is being prepared. Showing the original description.

AIDevGTM/gtm-cofounder324Updated Oct 19, 2026

Coach the user through actually selling: finding the champion and the buyer, running the first sales conversations, demoing their use case, handling "let me think about it," and closing the first paying customers yourself. Use when developers love it but nobody pays, you've never sold anything and freeze on the conversation, or deals keep stalling on "we'll think about it."

The English summary is being prepared. Showing the original description.

AIDevGTM/gtm-cofounder324Updated Oct 19, 2026

Turn hand-made first-50 traction into self-reinforcing acquisition loops, so the next 5,000 users come from usage, not founder hours. Use when growth stalls the moment the user stops pushing, every signup traces back to a DM or one launch spike, or they're reaching for "more channels" when the real gap is that using the product creates no new users.

The English summary is being prepared. Showing the original description.

AIDevGTM/gtm-cofounder324Updated Oct 19, 2026

Measure GTM with the metrics that matter (net developer retention, DREAM funnel) instead of vanity numbers. Use when the user has dashboards full of stars and pageviews but can't tell if go-to-market is working, or is optimizing acquisition over a leaky bucket.

The English summary is being prepared. Showing the original description.

AIDevGTM/gtm-cofounder324Updated Oct 19, 2026

See all skills by AIDevGTM

Report a problem with this skill