market-scan
Skill334 starsChanged 3 months agoMITView on GitHub
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.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- TrueScrape/truescrapetheir own version, first seen Nov 8, 2026
- Latifox/find-me-saastheir own version, first seen Sep 6, 2026
- tjdwls101010/Harness-of-Minervinitheir own version, first seen Aug 18, 2026
- Lengros/bennutheir own version, first seen Jul 8, 2026
- InfiniteRoomLabs/agent-opstheir own version, first seen Jun 23, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- Latifox/find-me-saas★ 10same name
- Lengros/bennu★ 2same name
- tjdwls101010/Harness-of-Minervini★ 1same name
- InfiniteRoomLabs/agent-ops★ 0same name
- TrueScrape/truescrape★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- start-hereSkill
- strategy-and-roadmapSkill
- who-is-this-forSkill
- talk-to-usersSkill
- positioning-and-storySkill
- beyond-the-wrapperSkill
- value-prop-that-convertsSkill
- the-homepageSkill
- time-to-first-valueSkill
- first-50-usersSkill
- launch-itSkill
- market-to-devs-sell-to-buyersSkill
- pricingSkill
- founder-led-salesSkill
- founder-led-contentSkill
- know-if-its-workingSkill
- review-the-workSkill
- growth-loopsSkill
- research-the-marketSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Start from the brief: Read docs/gtm-cofounder/founder-brief.md: the rivals ("what do they use instead"), the "why you", the villain, and …
- Distinctive: line 27
Report deltas, not descriptions: Do not summarize each competitor.
- Distinctive: line 61
If the market has shifted under you and you're not sure what it means for positioning, reach out to me on LinkedIn.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 revisitmarket-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 todocs/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 todocs/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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

