Z1 zero to one move
Skill thepraggyverse/zeroone-foundry/skills/z1-zero-to-one-move
80 source-grounded operating skills for zero-to-one strategy, technology, teams, distribution, and progress.
npx -y skills add thepraggyverse/zeroone-foundry --skill z1-zero-to-one-moveAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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.
What its author says it does
Copied from the file, not written here
Distinguish genuine creation from copying, scaling, or globalization when evaluating a product, strategy, or roadmap.
SKILL.md
1.5 KB, 275 tokens by cl100k_base, as published. Nobody here has run it
Zero To One Move
Objective
Distinguish genuine creation from copying, scaling, or globalization when evaluating a product, strategy, or roadmap.
Workflow
- State the decision, object, time horizon, and constraints.
- Separate observed facts from assumptions and predictions.
- Apply every relevant check below; mark non-applicable checks explicitly.
- Look for a counterexample, failure mode, and competing explanation.
- Return the output contract and one concrete next action.
Source-grounded checks
- zero to one move — Separate genuine creation from copying, scaling, or globalization. Produce the new capability and the copied baseline.
- globalization vs technology — Distinguish spreading an existing method from creating a better method.
Output contract
Return a compact table with: decision, evidence, source-backed checks, counterargument, risk, recommendation, and next action. Label confidence as high, medium, or low.
Guardrails
- Treat the framework as a lens, not universal law.
- Separate source doctrine, plugin synthesis, inference, and current evidence.
- Do not invent quotations or attribute wording that has not been verified.
- Read source-note.md for provenance and examples.md for prompts.
Gives 0 of the 12 instructions most roadmap strategy skills give in 275 tokens
Counted across 591 of the 672 authors here whose files we hold, read 2026-08-07
- read product marketing context before asking questionsin 21 of 591, across 10 files
- base price on perceived value, not costin 15 of 591, across 4 files
- compact after finalizing a planin 14 of 591, across 9 files
- differentiate tiers using features, limits, or supportin 14 of 591, across 3 files
- use Van Westendorp to find acceptable price rangein 13 of 591, across 2 files
- use MaxDiff to identify highly valued featuresin 13 of 591, across 2 files
- map topics to buyer journey stagesin 12 of 591, across 6 files
- Extract domain capabilities and classify subdomainsin 11 of 591, across 1 file
- Define bounded contexts around consistency and ownershipin 11 of 591, across 1 file
- Establish a ubiquitous language glossary and anti-termsin 11 of 591, across 1 file
- Capture context boundaries in ADRs before implementationin 11 of 591, across 1 file
- Open the strategic design template if neededin 11 of 591, across 1 file
Said here and by no other author read
- state decision object time horizon and constraints
- apply every relevant check and mark non-applicable checks
- look for a counterexample failure mode and competing explanation
- separate genuine creation from copying scaling or globalization
- produce the new capability and the copied baseline
- distinguish spreading existing method from creating better method
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.