Skip to main content

Managing Agents, Skills & Templates

Agents, skills, and prompt templates are plain files. Keep them in your repo, next to the code they work with, and commit them to git like anything else. When you want to ship a new version, push the folder. That keeps your agents under review and in version control instead of drifting in a dashboard.

Project layout​

Distri looks for three directories at the root of your project:

my-project/
├── agents/
│   ├── assistant.md
│   └── form_filler.md
├── skills/
│   └── refunds/
│       ├── SKILL.md
│       └── references/
│           └── policy.md
├── templates/
│   └── support-style.hbs
└── distri.toml          # optional workspace config

Drop this alongside your application code, or keep it in its own repo. Either way, it is just files.

Keep it in git​

Commit the folder like the rest of your codebase:

git add agents/ skills/ templates/
git commit -m "Add form_filler agent"

Now your agents live with the code they drive. Changes go through the same pull request review, history, and rollback you already use. The agent that fills a form ships in the same commit as the form.

Deploy a new version​

Authenticate once (distri login, or set DISTRI_API_KEY and DISTRI_WORKSPACE_ID in the environment), then push the whole tree:

distri push                 # syncs agents/, skills/, and templates/

Push replaces what is in your workspace with what is in your files, so a push is how you release. Wire it into CI to deploy on merge:

distri push --dry-run       # preview what would change
distri push                 # release

Push a single item when you only touched one thing:

distri push agents/form_filler.md
distri push skills/refunds

Reference commands​

Each resource type has its own subcommand if you want finer control than distri push.

Agents​

distri agents list
distri agents push agents/form_filler.md
distri agents push agents/ --all          # --all is required for a directory
distri agents delete form_filler -y

Skills​

distri skills list
distri skills push skills/refunds
distri skills push skills/ --all

Prompt templates​

distri prompts list
distri prompts push templates/support-style.hbs

Pull your workspace back down​

distri checkout does the reverse of push. It writes everything in your workspace back into the agents/, skills/, and templates/ layout, which is handy for adopting agents someone else pushed:

distri checkout

Versioning​

A push replaces an agent's definition in place. Existing threads keep working, and new runs use the new definition. When you need two versions live at once, give them distinct names (form_filler_v1, form_filler_v2) and push both.

Next​