agentleFS
vredinvredin/vredin-CC-Harness/.claude/skills/value-prop/SKILL.md

value-prop

Skill9 starsChanged 4 months agoNo licenceView on GitHub

Builds the strongest testable value proposition for one chosen customer segment. Feed it a /market-research result file or a plain description of a segment and its main Jobs. It pulls out the success criteria the segment cares about most, lays down a Job Map plus Delivery Chain to reason over, generates value hypotheses by sweeping a catalog of value mechanics over that map, screens each one for buildability, cost, working unit economics and competitive win, then orders the survivors with RICE and puts forward a lead proposition alongside a fallback — each carrying the three highest-priority Riskiest Assumption Test cards plus a PRD-ready implementation spec that feeds /product-requirements. Two modes: Quick (default, offline) and Deep (subagents plus web competitor mining). Plain language, English by default.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

24 rules. About 0 are common, 20 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈20

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.