A stack extends what Dryft does, adds skills and workflows for a kind of work, or both. Every version listed here is an exact GitHub release that was reviewed before it appeared.
Dryft works without stacks. Each kind adds something different, and all use the same contract for validation, installation, updates and removal.
Adds a capability to Dryft itself, such as a search provider the brain can use. Providers run only after you trust the exact digest of what you installed, and only when you select them.
Brings skills, hooks, knowledge and templates for one kind of work, like research or shipping software. Knowledge arrives as candidates you review, never as approved notes.
Extends Dryft and adds the workflow that uses it, such as a search provider bundled with a literature review skill. The trust requirements for both parts apply.
The popular tab ranks stacks by GitHub stars. Each count shows when it was fetched. Dryft does not report installation counts.
No featured stacks yet. The Dryft team selects which stacks to feature.
Every version is reviewed separately, including stacks published by Dryft. You still need to trust the exact digest before hooks or providers can run.
dryft stack install <stack-id> --inspectA public repository with stack.json at its root, and a published release whose tag is the stack's version, like v1.2.0.
Sign in with GitHub. We confirm you control the repository, resolve the tag to its commit and read stack.json from that commit.
Review downloads the release, validates it with Dryft, tests it with no production credentials and checks every disclosure against what the stack does.
The registry records the commit, the archive digest and the content digest. The Dryft CLI refuses to install anything that does not match.