Stack Builder
Create, validate and prepare standalone Dryft stacks for publication.
Before you install · 0.2.0
What it touches, and what it needs
The author declared these for this release, and review checked them against what the stack does, including what its skills ask the agent to do. They are declarations, not a sandbox.
About
A stack for creating your own stacks. It provides authoring and publishing skills plus starter templates to turn a workflow idea into a standalone bundle with skills, a manifest, a README and registry submission notes. The builder validates the result and can gather missing details in chat or Dryft UI. The publishing skill checks contract compliance, privacy, security and release metadata, then offers a GitHub release or a manual checklist and marketplace submission guidance.
Capabilities
- Reads files
Chosen stack source, Git history, Dryft contracts and bundled templates
Understand the stack, scaffold files, and review publication readiness, privacy and security.
Leaves your machine: Content read by the agent may be processed by the configured Claude or Codex service.
- Writes files
Chosen stack source directory and private local preparation/report files
Create stack files, make authorized fixes, and prepare validation reports, release notes and submission metadata.
Leaves your machine: No direct transfer from these writes; authorized publication is disclosed separately.
- Runs processes
Dryft CLI, Git, local search/scanning tools, and optional GitHub CLI
Validate stacks, inspect source/history, scan for sensitive content, and publish approved releases.
Leaves your machine: Remote Git/GitHub operations transmit the data described in the network disclosure.
- Uses the network
GitHub, GitHub source archives and referenced documentation
Check repositories/releases, verify published archives, and publish an explicitly authorized tag and release.
Leaves your machine: Repository identifiers and requests; authorized publication sends source, reachable Git history, tag metadata and release notes to GitHub. Authentication is used when required.
Prerequisites
Validate generated stacks and optionally run the local Dryft UI interview.
Required
Inspect repository state/history and create or push explicitly authorized release tags.
Required
Optional authenticated release publication; manual GitHub website publication is available.
Required for publishing and remote release verification; local stack creation works without it.
Executable hooks
No hooks. Nothing runs on session start or turn completion.
Supported agents
Claude Code and Codex
Release source and checksums
The Dryft CLI downloads this commit from GitHub, never a branch or a moving tag, and refuses the archive unless both digests match. A tag that moves later does not change this record.
Review notes
Reviewed the exact public GitHub commit archive, manifest, both skills, templates, prerequisites and data-flow disclosures. Safe archive validation and disposable installation with Claude/Codex projections and doctor passed on Linux x86_64/Python 3.12. No active hooks or providers. Fresh-host behavioral testing of the publishing workflow, macOS and native Windows remain unverified. Legacy repository links and original copyright notices are retained in the immutable release.
- 0.2.0
- v0.2.0
- a6278c0ed9eee846d2b6ea1ff5ad269f491bf16104dd74c2e0bc8a9f65032f24
- 532f799a00963079001ec5c1638a1eb6cd339d56876389db6bf1f2cd5f952c83
- v1
Versions
Every approved version, newest first. There are no automatic updates: use dryft stack update dryft-stack-builder to inspect and approve a newer one.
0.2.0Latest
dryft stack install dryft-stack-builder --version 0.2.0 --inspectCapabilities
- Reads files
Chosen stack source, Git history, Dryft contracts and bundled templates
Understand the stack, scaffold files, and review publication readiness, privacy and security.
Leaves your machine: Content read by the agent may be processed by the configured Claude or Codex service.
- Writes files
Chosen stack source directory and private local preparation/report files
Create stack files, make authorized fixes, and prepare validation reports, release notes and submission metadata.
Leaves your machine: No direct transfer from these writes; authorized publication is disclosed separately.
- Runs processes
Dryft CLI, Git, local search/scanning tools, and optional GitHub CLI
Validate stacks, inspect source/history, scan for sensitive content, and publish approved releases.
Leaves your machine: Remote Git/GitHub operations transmit the data described in the network disclosure.
- Uses the network
GitHub, GitHub source archives and referenced documentation
Check repositories/releases, verify published archives, and publish an explicitly authorized tag and release.
Leaves your machine: Repository identifiers and requests; authorized publication sends source, reachable Git history, tag metadata and release notes to GitHub. Authentication is used when required.
Prerequisites
Validate generated stacks and optionally run the local Dryft UI interview.
Required
Inspect repository state/history and create or push explicitly authorized release tags.
Required
Optional authenticated release publication; manual GitHub website publication is available.
Required for publishing and remote release verification; local stack creation works without it.
Executable hooks
No hooks. Nothing runs on session start or turn completion.
Supported agents
Claude Code and Codex