Z1 handoff
80 source-grounded operating skills for zero-to-one strategy, technology, teams, distribution, and progress.
npx -y skills add thepraggyverse/zeroone-foundry --skill z1-handoffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 24 days oldThe repository was created 24 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
Create a concise source-aware continuation artifact with decisions, evidence, open questions, and next skill.
SKILL.md
1.4 KB, 265 tokens by cl100k_base, as published. Nobody here has run it
Handoff
Objective
Create a concise source-aware continuation artifact with decisions, evidence, open questions, and next skill.
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
- handoff — Produce a source-aware continuation artifact with decisions, open questions, and next skill.
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.
- Read handoff-template.md for the workflow-specific template.
Gives 0 of the 12 instructions most agent orchestration skills give in 265 tokens
Counted across 742 of the 995 authors here whose files we hold, read 2026-08-07
- Reference existing artifacts by path or URLin 53 of 742, across 25 files
- Run the full test suite after integrating changesin 51 of 742, across 19 files
- Dispatch one agent per independent problem domainin 50 of 742, across 17 files
- Verify fixes do not conflictin 45 of 742, across 13 files
- Include a suggested skills section in the documentin 45 of 742, across 17 files
- Redact sensitive informationin 41 of 742, across 11 files
- Save to the temporary directory of the operating systemin 39 of 742, across 10 files
- Tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
- Spot check agent changes for systematic errorsin 34 of 742, across 7 files
- Write a handoff document summarising the current conversationin 31 of 742, across 6 files
- Assign each agent a specific scopein 23 of 742, across 8 files
- Provide specific scope and clear goalin 23 of 742, across 5 files
Said here and by no other author read
- State the decision, constraints, and time horizon
- Apply every relevant check
- Mark non-applicable checks explicitly
- Look for a counterexample or competing explanation
- Return the output contract
- Separate source doctrine from inference
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.