vstack-s1-select — Claude Code skill for choosing checks
The vstack-s1-select Claude Code skill selects verification methods and assurance tiers for system properties. It splits obligations by property and weighs scale, code ownership, and failure impact.
MIT ★ 89 updated 2026-11-16
/plugin marketplace add hao-ai-lab/vstack
/plugin install vstack@hao-ai-lab-vstackWhat vstack-s1-select does
The skill builds an obligation matrix and assigns verification methods and assurance tiers to individual properties. It considers difficulty, bounded or unbounded scale, code ownership, change rate, and failure severity. Promises about ledgers, protocols, computation, alignment, and fallback behavior are linked to the supporting rows.
It needs control, data, and boundary maps plus verified S0 anchors with hashes. The property owner approves the scope. S4 and S5 are required; S6 may be skipped only for new code intended for deductive proof. No general-purpose checker comes with the skill.
The checks cover hazardous transitions and consumer preconditions, and gaps must appear in the guarantee matrix. Each guarantee is capped by its weakest supporting evidence. Missing maps send the work back to S0; tangled orchestration can be split behind a small interface before proof work begins.
What it helps with
- split verification obligations by property rather than module
- choose assurance tiers based on scale and failure impact
- map system promises to supporting evidence
- find gaps in the guarantee matrix and route missing maps back to S0
Example prompts for the agent
- Split this component's obligations by property and select verification methods.
- Build a guarantee matrix from the S0 control, data, and boundary maps.
- Find hazardous transitions and consumer preconditions without an obligation.
How to install vstack-s1-select
1Plugin marketplace
/plugin marketplace add hao-ai-lab/vstack/plugin install vstack@hao-ai-lab-vstackThis installs the whole vstack plugin with all its skills
2Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-s1-select -a claude-code3Manually: put the files in place
~/.claude/skills/vstack-s1-select/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vstack-s1-select/
1Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-s1-select -a codex2Manually: put the files in place
.agents/skills/vstack-s1-select/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-s1-select -a cursor2Manually: put the files in place
.cursor/skills/vstack-s1-select/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hao-ai-lab/vstack skills/vstack-s1-select2Manually: put the files in place
.github/skills/vstack-s1-select/SKILL.md1Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-s1-select -a gemini-cli2Platform CLI
gemini skills install https://github.com/hao-ai-lab/vstack --path skills/vstack-s1-selectManually: put the files in place
.devin/skills/vstack-s1-select/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vstack-s1-select
How do I install vstack-s1-select in Claude Code?
Add the marketplace with /plugin marketplace add hao-ai-lab/vstack, then install the plugin with /plugin install vstack@hao-ai-lab-vstack.
What does vstack-s1-select do?
It divides system obligations by property, then selects verification methods and assurance tiers. It connects guarantees to evidence and records gaps in the matrix.
What does vstack-s1-select need to run?
It needs control, data, and boundary maps, plus verified S0 anchors with hashes. The property owner approves the scope.
Source text
SKILL.md · MIT
--- name: vstack-s1-select description: "Choose verification tools and assurance tiers per property using state, scale, ownership and consequences." --- # S1 — Split obligations and select methods Read [Layer 0: shared operating rules](../../docs/layer-0.md), this stage and the assigned input bundle. ## Role and write scope The coordinator owns the design and obligation matrix; the property owner approves the scope. ## 1. Input Control, data and boundary maps and verified anchors from S0, with hashes. ## 2. Procedure 1. Use [method selection](../../docs/method-selection.md). Split by property, not module or processor type. 2. Record each obligation's difficulty, finite or unbounded scale, code ownership, change rate and failure severity. 3. Map ledger, protocol, computation, alignment and fallback guarantees. Identify which row supports each promise and which is weakest. 4. Record each property's tier, rationale, available tools and skipped stages. Require S4 and S5. Skip S6 only for new code destined for deductive proof. ## 3. Exit checks - Manually check that every hazardous transition and consumer precondition has an obligation. - Account for every gap in the guarantee matrix; no generic checker is bundled. - Record scope and design approval. Limit each guarantee to its weakest supporting evidence. ## 4. Rollback Missing maps return to S0. If no small clean proof core exists, propose the smallest interface separation before proving tangled orchestration code. Use [a rollback ticket](../../templates/rollback.md). ## Concrete Examples PD KV slot reuse is a state-machine obligation: finite exploration finds interleavings; an arbitrary-scale claim needs a corresponding design-model theorem plus explicit model/code alignment.
© Hao AI Lab · MIT · hao-ai-lab/vstack