Venture idea simulation

Skill ryuzo-k/yomira/skills/venture-idea-simulation

Simulate likely reactions to a new business idea, product concept, API, SaaS, service, or launch plan. Use when validating whether a venture direction may attract buyers, users, agencies, enterprises, or technical communities.From its SKILL.md

Install

npx -y skills add ryuzo-k/yomira --skill venture-idea-simulation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 359 tokens by cl100k_base, as published. Nobody here has run it

Venture Idea Simulation

Purpose

Use this skill to test a business idea before overbuilding or overlaunching.

This is not a market-size calculation. It is a reaction simulation:

who gets it immediately
who thinks it is fake, obvious, or a prompt wrapper
who would pay and why
what proof they need
what pricing feels plausible
which first segment is closest to money

Context Collection

Extract:

product/service/API idea
buyer/user candidates
pricing hypothesis
distribution channels
existing assets
founder credibility
alternatives being considered
what "success" means
time/cash goal

If the idea is vague, first ask for the artifact the market will see: landing page, offer, demo, X post, DM, or one-paragraph product description.

API Use

Use Yomira with:

{
  "artifact": {
    "type": "venture_concept",
    "content": "CONCRETE PRODUCT/OFFER DESCRIPTION"
  },
  "objective": "Decide which launch segment, pricing, and positioning to test first.",
  "audience": {
    "description": "Likely buyer/user segments and where they encounter the idea."
  },
  "simulation": {
    "target_n": 80,
    "max_agent_voices": 10,
    "max_output_tokens": 18000
  }
}

Output

Return:

first segment to sell to
segments that are curious but unlikely to pay
high-ticket angles
self-serve angles
proof needed before payment
likely pricing resistance
raw voices that reveal actual buying motives
next experiment to run

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most product growth skills give in 359 tokens

Counted across 728 of the 1,010 authors here whose files we hold, read 2026-08-07

Read product marketing context before asking questionsin 24 of 728, across 18 files
Define the ideal customer profilein 21 of 728, across 3 files
Document a rollback plan before deploymentin 21 of 728, across 12 files
Analyze the codebase to understand the productin 19 of 728, across 1 file
Ask clarifying questions about the value propositionin 19 of 728, across 1 file
Search for companies matching the criteriain 19 of 728, across 1 file
Look for signals of immediate needin 19 of 728, across 1 file
Assign a fit score from one to tenin 19 of 728, across 1 file
Identify the target decision-maker rolein 19 of 728, across 1 file
Suggest a personalized contact strategyin 19 of 728, across 1 file
Provide conversation starters for outreachin 19 of 728, across 1 file
Format results in a scannable markdown templatein 19 of 728, across 1 file

Said here and by no other author read

ask for a concrete artifact if the idea is vague
extract the product idea and buyer candidates
extract the pricing hypothesis and distribution channels
extract existing assets and founder credibility
extract alternatives being considered
extract the success definition and time goal

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.