Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/spinout
Use when extracting a project into its own repo — a venture spinout (e.g. a product leaving its incubator repo) or a sanitized content-snapshot fork. Guided 5-step runbook: target sphere + path, confidentiality/sanitize check, copy + fresh git init, SNAPSHOT-FREEZE marker in the source repo, remotes + registration. Trigger on 'spin out X', 'extract this into its own repo', 'fork X sanitized'.
Passed 11 of 19 test cases with the skill, and 7 of 19 without it.
and 5 more in the full report
6 fixed7 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am initiating a spinout for `experimental/ai-sandbox`. What are the two valid extraction types I can choose from during Phase 1?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies venture-spinout and sanitized-snapshot as the two extraction types | Missed | Passed |
The instructions your model reads when the skill loads.
This is a 5-phase interactive runbook, not a CLI wrapper. Automate only after 2-3 hand-runs have stabilized the pattern — spinout is a low-frequency, high-stakes operation (new remote, fresh history, a frozen marker left behind in the source repo), and premature scripting bakes wrong defaults (wrong sphere, wrong sanitize scope, wrong remote layout) into something expensive to undo. See #730 / H2.
Read skills/_shared/bootstrap-gate.md and execute the gate check. If the gate is CLOSED, invoke skills/bootstrap/SKILL.md and wait for completion before proceeding. If the gate is OPEN, continue to Phase 1.
Ask via AskUserQuestion (per .claude/rules/ask-via-tool.md AUQ-001):
CLAUDE.md (e.g. ~/.claude/CLAUDE.md) for the "Verzeichnis = Account" mapping (private vs. org vs. ventures trees, or whatever the host documents) and offer those as options.venture-spinout (a product leaving its incubator repo, gets a live remote and its own backlog) or sanitized-snapshot (a frozen, sanitized fork of content/code with no independent forward development expected).Do not proceed to Phase 2 without explicit confirmation of all three.
Checklist:
Inertness declaration pattern: infra-coupled scripts that will simply run empty in the new repo without their source tokens/infra (not broken, just inert there) get TABULATED in the FORK-NOTES (Phase 4) rather than silently deleted — deletion loses information a future maintainer needs; the table makes the inertness an explicit, reviewable fact.
git subtree split or git filter-repo. No shared history travels with the spinout by design; the new repo starts clean.node_modules, dist, .git, lockfile-derived caches).git init fresh in the destination.README.md / CLAUDE.md (or AGENTS.md on Codex CLI): source repo, source path, extraction date, extraction type.test cases passed, vs 7 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.