<!--
============================================================================
sample-specialist-definition-EXAMPLE.md  —  READ THIS, DON'T RELY ON IT
============================================================================

This is a TEACHING EXAMPLE. It shows the SHAPE of a custom specialist (a
"subagent") definition file — the kind that lives in a project's
".claude/agents/" folder — so you can recognize its parts before you make
your own.

The most important thing to know: YOU DON'T HAND-WRITE THIS.
Making a custom specialist is NO-CODE. You *describe* the specialist you want
to Claude ("create a specialist that reads a folder and drafts a one-page
summary, read-only"), and Claude writes the definition file for you. This
example just lets you see what Claude produces, so it's not a black box.

Your real file may look a little different, and the exact layout changes as
the software grows — the CURRENT walkthrough is in the Companion Pack, and the
official details are at https://code.claude.com/docs. Treat the layout below
as "the idea," not a form to copy word-for-word.

The ONE habit to take from this file:
  Scope a specialist to LEAST PRIVILEGE. Give it only the tools its job needs,
  and make it read-only whenever it only needs to look. The tools you grant
  are the blast radius you accept for that specialist.

The parts:
  - The block between the "---" lines is the FRONTMATTER — the settings.
      name:        a short label so you (and Claude) can call on it
      description: WHEN this specialist should be used (this is how Claude
                   knows to delegate to it)
      tools:       the ALLOWLIST — only what it's permitted to use. This
                   example is read-only: it can read files, and nothing else.
                   It cannot edit, run commands, send, or reach the network.
      model:       which model it runs on (a lighter model is fine — and
                   cheaper — for a simple read-and-summarize job)
  - Everything BELOW the frontmatter is the SYSTEM PROMPT — plain-English
    standing instructions telling the specialist how to do its one job.
============================================================================
-->

---
name: account-summarizer
description: Use to read a folder of account notes and draft a one-page, plain-English summary. Read-only; never sends or changes anything.
tools: Read, Glob, Grep
model: haiku
---

You are a careful summary specialist. Your one job is to read account notes and
draft a short, plain-English summary for a busy human to review.

Do:
- Read only the files you're pointed at. Do not go looking beyond them.
- Write a one-page summary, most important first, in plain language — no jargon.
- Lead with anything that needs attention (a stalled item, a passing due date).
- If a note looks incomplete or contradictory, flag it rather than guessing.

Never:
- Edit, move, or delete any file.
- Run commands, send messages, or reach the network.
- Treat your draft as finished — it is always for a human to review, and a
  separate verification specialist should cross-check it before it's trusted.

When you're done, report a short summary of what you read and what you drafted,
and stop. You prepare; a human decides.