agentleFS
UnfoldCRO-OrganizationUnfoldCRO-Organization/cro-agent-skills/skills/idea-validator/SKILL.md

idea-validator

Skill0 starsChanged 22 days agoMITView on GitHub

Stress-test a new business, product or SaaS idea: users, pain, competitors, cost, distribution, riskiest assumption, cheapest validation experiment. Use for "validate this idea", "new product idea", "would this work". NOT agency decisions (founder-strategy).

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prd-generator and prompt-engineer.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dhzrxSkill

    prd-generator

    Generate comprehensive Product Requirements Documents with AI PM best practices for new features and products

    Also in 3 projects that use this

  • JeffallanSkill

    prompt-engineer

    Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot learning, creating system prompts with personas and guardrails, building JSON/function-calling schemas, or developing prompt evaluation frameworks to measure and improve model performance.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Write directly and specifically.

    line 29
  2. Distinctive:

    Never reveal client secrets or personally identifying data unnecessarily.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 12 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.

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

idea-validator

Purpose

Stress-test new business and software ideas. Use concrete evidence and project-specific constraints. Do not claim work was executed, tested, legally approved, or verified unless it actually was.

Activation

Activate when the request concerns stress-test new business and software ideas. Read relevant project instructions first. When current laws, platform APIs, or tool capabilities matter, check authoritative current sources.

Procedure

  1. Define users and pain points.
  2. Map competitors and substitutes.
  3. Estimate cost and distribution.
  4. List highest-risk untested assumption.
  5. Design inexpensive validation experiment.

Verification gate

  • State what was examined, what was not accessible, and any assumptions.
  • Separate confirmed findings, risks, recommendations, and unverified hypotheses.
  • For development, require relevant automated tests and manual checks before marking complete.
  • Provide exact file paths/line references, data sources, or legal citations when appropriate.
  • Report blockers and proposed fixes by severity. Never silently change production systems.

the agency editorial and safety rules

  • Write directly and specifically. No generic AI fluff, em dashes, exaggerated claims, artificial case studies, unnecessary dividers, or fabricated proof.
  • Never reveal client secrets or personally identifying data unnecessarily. Use redacted examples and placeholders.
  • Seek explicit approval before sending external communication, changing production, deploying code, deleting data, or conducting active security tests.
  • For regulated legal or tax conclusions, provide research support, not a claim of professional sign-off.

Deliverable template

  1. Scope and context, 2. Evidence and findings, 3. Prioritized action plan, 4. Validation/acceptance criteria, 5. Uncertainties or approvals needed. Adapt format to the actual request rather than forcing five headings.

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.