Draft QueueCAUTION
A framework for building agentic apps
Overview
A framework for building agentic apps
5977febf67f1OBSERVED · 2026-10-14What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: draft-queue description: Use when queuing, reviewing, editing, opening, or sending email drafts requested by organization teammates, including Slack @agent-native intake. --- # Draft Queue The draft queue is for teammate-requested emails that need the owner to review before sending. It is durable SQL data in `queued_email_drafts`, not compose application state. ## Rules - Use `queue-email-draft` when a teammate asks the agent to prepare an email for an organization member. - The requester and reviewer must both be members of the active organization. `requireQueueContext` throws if there's no active org, or if the caller isn't a member — both surface as plain errors, not empty results. - Slack requests should queue drafts, not send raw emails. - Slack intake is the agent's Slack connection. It's set up and switched on in Settings › Channels › Slack (`navigate --settingsSection=slack`); Mail's Draft requests group there links to the queue. - `queue-email-draft` returns `reviewUrl`; include that URL when replying to Slack so the owner can open the exact draft. - Slack intake verifies the sender email via Slack `users.info` when the app has `users:read.email`, and passes verified sender name/email into the agent context. If that scope is missing, Slack intake cannot resolve a real email and will not queue anything — tell the requester to ask an admin to grant `users:read.email` rather than guessing their address from their Slack display name. - Managed Slack installs request `users:read.email` through the generated OAuth manifest; an existing install must be reconnected after the scope is granted. Legacy bot-token installs must add the scope in Slack manually. - `ownerEmail` accepts more than an exact email: `resolveOrgMemberEmail` also matches an unambiguous local-part prefix (e.g. `"jane"` matches `[email protected]` if she's the only `jane*` member). If more than one member matches the prefix, the action throws listing all org member emails instead of guessing — pass the full email in that case. - Use `send-queued-drafts` only when the queued draft owner explicitly asks to send. - Use `open-queued-draft` when the user wants to manually tweak a queued draft in the compose panel. ## Status Lifecycle And Access A queued draft moves through `queued -> in_review -> sent`, or `-> dismissed` at any point before `sent`. Rules enforced in `server/lib/queued-drafts.ts`: - **Ownership is strict.** Only the `ownerEmail` (or an org `owner`/`admin` role) can call `update-queued-draft`, `open-queued-draft`, or `send-queued-drafts` for a given draft — `requireQueuedDraft(id, {ownerOnly: true})` rejects the original requester from editing or sending it, even though they created it. - **Sent drafts are frozen.** `updateQueuedDraft` throws `"Sent queued drafts cannot be edited."` if `status` is already `sent` and the caller isn't also setting it to `sent` again. Don't retry an edit on a sent draft — create a new `queue-email-draft` instead. - **`open-queued-draft` transitions status to `in_review`** and copies the draft into a real `compose-{id}` application-state entry (auto-appending the *owner's* configured signature, not the requester's). It also blocks opening a draft that is already `sent` or `dismissed`. - **`send-queued-drafts --all=true`** sends every `queued` or `in_review` draft assigned to the caller (default limit 50, capped 50) by delegating to the real `send-email` action per draft — each send still requires the standard approval gate. Partial failures are reported per-draft in `{ sent, failed }` rather than aborting the whole batch; report both lists back to the user. - Queueing a draft for someone else fires a best-effort in-app notification to the owner (skipped when self-queuing); a failed notify does not fail the queue action itself. ## Actions | Action | Purpose | | ----------------------------- | ----------------------------------------------------------------------- | | `list-org-members` | Resolve valid organization members for `ownerEmail` | | `queue-email-draft` | Create a queued draft for a member to review | | `list-queued-drafts` | List active, sent, dismissed, review, or requested drafts | | `update-queued-draft` | Edit queued draft fields or set status | | `open-queued-draft` | Open a queued draft as `compose-{id}` | | `send-queued-drafts` | Send one queued draft or all active drafts assigned to the current user | | `navigate --view=draft-queue` | Open the queue UI | ## Typical Flow 1. Resolve the target reviewer with `list-org-members` if the user gave a name. 2. Call `queue-email-draft` with `ownerEmail`, recipients, subject, body, and context. 3. Tell the requester it was queued and include the returned `reviewUrl`. For review: 1. Call `list-queued-drafts --scope=review --status=active`. 2. Use `update-queued-draft` for tone/content changes. 3. Use `open-queued-draft` for manual compose edits, or `send-queued-drafts` when the owner asks to send.
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (5)
.agents/skills/an
.agents/skills/content-product-development
.agents/skills/design-exploration
.agents/skills/turn-into-app
.agents/skills/visual-edit
Gates applied: no_behavioural_pass.
5977febf67f1full audit observations/trust-audit/skill/builderio__draft-queue.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-14 | 5977febf67f1 | CAUTION | B | 89 | first audit |
Questions
What does the Draft Queue skill do?
A framework for building agentic apps
Is Draft Queue safe to install?
With care. The audit graded it B (89/100) and found 5 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Draft Queue access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (5977febf67f1), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/builderio/draft-queue/)
Not your listing, or something out of date? Claim or update your listing.