Stave
A single skill
One stave, one job. It's a folder, not just a file: a README, an AGENTS.md or SKILLS.md, and whatever else the task needs. Staves are versioned and forkable, so the good ones are easy to build on.
Browse staves →About Galdr
An open registry for
agent skills.
An agent is only as good as the instructions behind it. Galdr is where people write those instructions down and share them. One skill is a stave. A stack of staves is a grimoire. That's the whole idea.
Work in progress. These ideas are still settling — expect the model and its best practices to change.
The problem
Why Galdr exists
Good agent instructions get written once and then lost: buried in a notes app, a private repo, a chat thread. The next person rebuilds the same thing from scratch. Galdr is the shared place to put that work — find a stave someone already got right, and build on it instead of reinventing it.
The model
The core ideas
Three ideas, and how they nest: a stave is one skill, a grimoire is a stack of them, and orchestration is what makes a grimoire run itself.
Grimoire
A stack of staves
A grimoire puts staves in a deliberate order. It tracks each stave by family, not by snapshot, so it can follow the latest version or pin a known-good one when you need the output to stay put.
Browse grimoires →Orchestration
A grimoire that runs
Orchestration is optional, and it belongs to grimoires, not staves. A plain grimoire just runs its staves in order. An orchestrated one adds a document at the head — a file, a stave, or a folder pointed to by an AGENTS.md — that tells a model how to drive the whole run.
Grimoire
Head documentoptional · orchestration
Stave
Stave
Stave
The format
Portable and open
A stave is just markdown and files — nothing proprietary. Any agent that reads instructions can use one, so what you publish here isn't tied to a single vendor or runtime.
# Stave: Code Reviewer ## Role You are a meticulous reviewer focused on security and performance. ## Instructions 1. Flag SQL injection vectors 2. Check for N+1 queries 3. Verify error handling
- Plain files. A README, an AGENTS.md, whatever the task needs. If you can read it, so can your agent.
- Open registry. Everything published is public to search, read, and download.
- Licensed and forkable. Every stave carries a license — fork one, improve it, and publish your version with credit intact.
- Yours to take. Download any stave or grimoire and run it wherever you want. No lock-in.
The pattern
How orchestration works
Orchestration is opt-in. Without it, a grimoire is just a list you work through in order. With it, you compose small staves into one workflow without hard-coding that workflow into any single stave.
- 1
Write a focused stave
Keep each stave to one job and package it with its own README and AGENTS.md so it stands on its own.
- 2
Stack them in order
Add staves to a grimoire in the order they should run. Pin versions when you need the result to be repeatable.
- 3
Add a head document
Put one orchestration document at the top — a file, a stave, or a folder referenced by an AGENTS.md. It says how the pieces fit and in what order.
- 4
Hand it to a model
A model reads the head document and works through the staves in order. One grimoire, one run.
The loop
How you use it
The loop is simple. Draft a stave in the Loom, publish it to the registry, and it's immediately something other people can find, run, and build on.
- The Loom.Galdr's editor. Write a stave, organize its files, and check it before you publish.
- The registry. Where published staves and grimoires live. Search by tag, sort, and download.
- Your library.Save the staves and grimoires you rely on so they're one click away.
- Fork and version.Start from someone else's stave, change what you need, and publish your own version.
Your presence
And your saga
Everything you publish lands on your saga — your public page on Galdr, where people find your work and follow what you build. Anyone can read it; only you can add to it.