agentleFS
Sign inStart free
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/demand-validator/SKILL.md

demand-validator

Skill1 starsChanged 22 days agoMITView on GitHub

Designs staged demand tests when a business needs stronger evidence than stated interest before committing.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Use after identifying an opportunity but before a major launch, build or market entry commitment.

    line 9
  2. Distinctive:

    Create an assumption register and test cards with hypothesis, audience, stimulus, measure, threshold, risk and next action.

    line 26
  3. Distinctive:

    Test exposure and evidence strength are not overstated

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Demand Validator

When to use it

Use after identifying an opportunity but before a major launch, build or market entry commitment.

What Claude needs

  • Opportunity and target segment
  • Business context from client-context.md
  • Demand hypotheses and riskiest assumptions
  • Available test channels, time and capacity

Method

  1. Define the demand claim and observable behaviour that would support it.
  2. Rank assumptions by uncertainty and consequence using an assumption map.
  3. Design the smallest ethical test for each critical assumption.
  4. Set thresholds, comparison groups and stopping rules before testing.
  5. Separate signals of attention, intent, commitment and repeat behaviour.
  6. Specify how each result changes the next decision or test.

Output format

Create an assumption register and test cards with hypothesis, audience, stimulus, measure, threshold, risk and next action.

Quality checks

  • Tests measure behaviour relevant to real adoption
  • Thresholds are set before results are seen
  • Test exposure and evidence strength are not overstated

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.

Check your setup, free