agentry/drafter
Drafts a QuickAgent from a description, searching the registry and the web; AI Review reads every result first.
Built into Agentry. The application runs this package itself; it is published here so you can read how it works. Its README says what Agentry gives it beyond its manifest.
Declared capabilities
Ships knowledge: drafting-guide (211.3 KB), in the release archive under knowledge/<name>/, scanned with the version.
Capabilities are the author's declaration and the basis for policy and scanning. The registry cannot enforce them at run time. Your runtime should.
MCP servers & tools
agentry run serves exactly the tools this contract declares, through a per-run MCP gateway. An undeclared capability is a tool that does not exist at run time.
Tools the runner grants
| Manifest declaration | Tool(s) granted |
|---|---|
| (always) | write_report — reports → the run's output folder |
| (always) | list_inputs, read_input, search_inputs — operator-provided input files, read-only |
MCP servers involved
- QuickAgent Tools — the runner's companion server, served through a per-run Docker MCP Gateway; its tool surface is exactly the table above.
In an embedded install
Installed into an existing coding agent (agentry install), the same contract maps to the host's built-in tools — enforcement there is the host's. Allowed tools: none declared (host defaults apply).
Install
agentry install agentry/drafter@1.15.4git clone https://secureagentry.net/agentry/drafter.gitgit clone ssh://git@git.secureagentry.net/agentry/drafter.gitclaude-skill is this agent's default target, so the flag is not needed.
knowledge/drafting-guide/wiki/manifest/knowledge-accepts.md
---
title: The person's knowledge at run time
type: guide
summary: When a QuickAgent asks the person to attach a knowledge pack of their own at run time (knowledge.accepts), how to write its prompt, and what goes into the instructions instead. A draft never ships a pack.
sources: [web:https://docs.secureagentry.net/quickagents/, web:https://docs.secureagentry.net/knowledge/]
updated: 2026-10-05
---
# The person's knowledge at run time
A knowledge pack is a folder of pages compiled from documents, which a run reads with three tools, `knowledge_list`, `knowledge_search` and `knowledge_read`. A QuickAgent can ask the person to attach one of their own packs to each run. That is the manifest's `knowledge` field, a field of the manifest itself and never under `capabilities` [src: web:https://docs.secureagentry.net/quickagents/; web:https://docs.secureagentry.net/knowledge/].
## When to ask for one
Declare `knowledge.accepts` only when the QuickAgent needs the person's own pack at run time because the facts it works from are theirs and change: their runbooks, their style guide, their product's documentation, their policies.
What holds for every run goes into the instructions instead, in `## Background`. That includes what you learned while drafting from packs the person gave you: write it into the instructions in your own words, and ask for a pack at run time only when the facts will have changed by the next run, or differ from person to person.
## How to write it
`{"accepts": {"prompt": "…"}}`:
- `prompt`: one plain line of at most 300 characters saying what to attach ("Your team's runbooks, if you have them"). It is shown to the person only, in the run setup's Knowledge step; the agent never sees it.
- `"required": true` only when the QuickAgent cannot work without one. Otherwise leave `required` out, and the person may skip the step.
Attaching a pack is the person's own grant, as adding a file is, so `accepts` adds nothing to the contract [src: web:https://docs.secureagentry.net/quickagents/].
The instructions' `## Steps` then start from the attached knowledge: list the packs, read each one's index, then search and read the pages the task needs, and say what to do when no pack is attached and it was optional.
## Never ships
**Never declare `ships`.** It would put a pack inside the QuickAgent's own release. A draft never ships a pack, and the person's packs stay theirs. Your drafting guide is not the person's either: it never leads to `knowledge.accepts`, and its pages never go in a draft's `sources`.