agentleFS
Aizaz-NoorAizaz-Noor/Agent-Startup-Skills/skills/market-scout/SKILL.md

market-scout

Skill2 starsChanged 7 months agoMITView on GitHub

Market research and validation agent. Analyzes competitors, identifies target users, and validates product-market fit before any code is written. Triggers on: market research, competitor analysis, validate idea, target audience.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before starting any new SaaS project

    line 18
  2. Distinctive:

    When validating a pivot or new feature direction

    line 19
  3. Distinctive:

    When the user says "is this idea worth building?"

    line 20
  4. Distinctive:

    Ask the user ONE question: "What specific problem does this solve, and for whom?" Do not proceed until you have a clear answer.

    line 25
  5. Distinctive:

    Do not proceed until you have a clear answer.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Market Scout — Research & Validation Agent

Purpose

Prevent building products nobody wants by conducting structured market research before a single line of code is written.

When to Use

  • Before starting any new SaaS project
  • When validating a pivot or new feature direction
  • When the user says "is this idea worth building?"

Process

Step 1: Problem Extraction

Ask the user ONE question: "What specific problem does this solve, and for whom?" Do not proceed until you have a clear answer.

Step 2: Competitor Landscape

Research and present a table of 3-5 existing solutions:

CompetitorWhat They DoPricingKey Weakness
Example CoSolves X for Y$29/moPoor UX for Z

Step 3: Unique Value Proposition

Based on competitor weaknesses, articulate what makes THIS product different in one sentence. Format: "Unlike [competitor], we [unique advantage] for [target user]."

Step 4: Target User Persona

Define the primary user:

  • Role: (e.g., "Solo freelance designer")
  • Pain Point: (e.g., "Spends 3 hours/week on invoicing")
  • Budget: (e.g., "Willing to pay $10-20/month to save time")
  • Current Solution: (e.g., "Using spreadsheets manually")

Step 5: Risk Assessment

Identify 2-3 key risks:

  • Market risk (is there demand?)
  • Technical risk (can we build this?)
  • Monetization risk (will people pay?)

Output

Produce a market_brief.md file with all sections above.

Exit Criteria

  • Problem is clearly defined
  • At least 3 competitors are identified
  • UVP is articulated
  • Target persona is defined
  • Risks are listed with mitigations

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.