Handoff Inbox Drain logo

Handoff Inbox Drain

Organization
escoffier-labs
handoff-inbox-drain

Use when draining a Brigade handoff review inbox - triage drafts with allowlist-bound Brigade handoff commands, grounded edits that cite on-disk content, archive-only retention, and reinforce-in-place when ingest already matched a known fact (#724). Never delete, remove, or prune.

Overview

Publisherescoffier-labs
Repositorybrigade
Skill namehandoff-inbox-drain
Stars
82
Forks
9
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by escoffier-labs on GitHub. Read the source before you install it.

Installation

Install the Handoff Inbox Drain AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/escoffier-labs/brigade/tree/main/src/brigade/templates/skills/handoff-inbox-drain
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/escoffier-labs/brigade.git /tmp/brigade
mkdir -p .claude/skills
cp -r /tmp/brigade/src/brigade/templates/skills/handoff-inbox-drain .claude/skills/handoff-inbox-drain
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Handoff Inbox Drain in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Handoff Inbox Drain on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Handoff Inbox Drain is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

handoff-inbox-drain

Drain a handoff review inbox with judgment, without owning a scheduler. Brigade stays invoke-only; this skill is the allowlist-bound agent recipe for triage.

When this applies

  • A handoff draft inbox has pending or reviewed items to triage.
  • An operator schedules a headless harness (claude -p, codex exec, or equivalent) against this skill.
  • You are reinforcing existing memory, not inventing a parallel corpus.

Allowlist

Work only through this allowlist of Brigade surfaces and local reads:

  • brigade handoff list
  • brigade handoff show <id>
  • brigade handoff archive <id>
  • brigade handoff closeout (when the workspace supports it)
  • brigade handoff lint / brigade handoff doctor for health checks
  • Read/Grep of on-disk handoff files, memory/cards/, and related indexes already present in the target

Bash is scoped to those brigade handoff … commands only. Do not expand into arbitrary filesystem writes, remote APIs, unscoped shell, or tools outside this allowlist. Stay inside the handoff inbox / memory/cards/ roots; do not follow .. or symlinks out of those trees.

Grounded-edit rules

Every edit must be grounded. You must cite existing on-disk content (handoff body, card text, or index entry) before changing anything. Prefer reinforce-in-place: edit or refresh only what you can verify against a local source of truth. Date-bumps alone are not grounded edits.

Retention (never delete)

  • Never delete handoff drafts or memory cards.
  • Never remove inbox items by destructive filesystem ops.
  • Never prune archives, queues, or card trees.
  • Archive only: uncertain or done items go through archive/closeout paths, or a needs-human file the operator already uses.

Reinforce over duplicate (#724)

brigade ingest --promote-cards reinforces an existing card on exact content fingerprint match and inboxes near-match or opposite-polarity proposals for review. When draining the inbox:

  1. Search existing cards and recent handoffs for the same fact or decision.
  2. If ingest already proposed a near-match reinforce or contradiction, honor that routing — do not create a sibling card.
  3. If a close match exists without an ingest proposal, reinforce that card (cite the on-disk source) instead of creating a sibling.
  4. If unsure, leave the draft for human review rather than splitting the corpus.

Process

  1. List pending drafts with the allowlist commands.
  2. For each item, read the on-disk handoff and related cards.
  3. Triage: archive noise, closeout completed review, reinforce an existing card when the fact matches, or park uncertain items for a human.
  4. Capture outcomes against handoff-inbox-drain when verification is part of the run.
  5. Stop when the inbox is drained or only needs-human items remain.

Failure paths

  • Missing inbox or handoff source config: stop. Report the missing path/config; do not invent an inbox or create one.
  • Empty inbox / no pending drafts: exit cleanly with "nothing to drain"; do not invent work.
  • Malformed handoff entry (unreadable frontmatter, missing id, broken body): skip that item, leave it for a human, continue with the rest. Never rewrite a malformed file just to make the loop continue.

Out of scope

  • session-sweep (blocked on #466)
  • Scheduler or model-dispatch integration
  • Automatic card creation without an on-disk citation

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Handoff Inbox Drain AI skill do?

Use when draining a Brigade handoff review inbox - triage drafts with allowlist-bound Brigade handoff commands, grounded edits that cite on-disk content, archive-only retention, and reinforce-in-place when ingest already matched a known fact (#724). Never delete, remove, or prune.

Why use Handoff Inbox Drain on TypingMind?

Because you install it once and use it with any model. Handoff Inbox Drain is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Handoff Inbox Drain in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/escoffier-labs/brigade/tree/main/src/brigade/templates/skills/handoff-inbox-drain. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Handoff Inbox Drain?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Handoff Inbox Drain?

As many as you like. As long as a model supports skills, you can use Handoff Inbox Drain with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Handoff Inbox Drain AI skill free?

Yes. It is published on GitHub by escoffier-labs under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇