Skip to content

Guide · Agent skill

How to use the Supervisor Review Queue agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The Supervisor Review Queue skill gives an AI agent a structured approval queue for a law clinic. When a professor has chosen a formal review queue during setup, student drafts, memos and client letters wait in a list until the professor approves, edits then approves, or returns them with a note. This guide explains what the skill does, how to install it, how to trigger it and what it needs to run.

Supervisor Review Queueanthropics/claude-for-legal · Apache-2.0

Quick start

  1. 1Download the ZIP. Download the supervisor-review-queue ZIP from this page.
  2. 2Unzip into a skills folder. Unzip into ~/.claude/skills/ for personal use, or into .claude/skills/ inside a project folder.
  3. 3Confirm the clinic setup. Make sure a configured claude-for-legal plugin has a legal-clinic CLAUDE.md at ~/.claude/plugins/config/claude-for-legal/legal-clinic/ with the supervision style set to formal review queue.
  4. 4Add the queue file. Place references/review-queue.yaml with your queue entries where the skill can read it.
  5. 5Ask for the queue. Request what is waiting for review, or run /legal-clinic:supervisor-review-queue.
  6. 6Act on an item. Approve, edit then approve, or return the item with a note. Each action is logged.

What is an agent skill and what does this one do?

An agent skill is a folder containing a SKILL.md file and any supporting files. Once installed, an AI agent can load it and follow its instructions when a request matches the skill's description.

This skill shows the professor what is waiting for review, sorted by urgency and by student. It supports three actions on an item: approve, edit then approve, and return with a note. Every action is logged. If the clinic chose a different supervision style, the skill stays dormant and only explains how to switch.

  • Default view: pending items grouped by urgency (deadline-sensitive first, then standard) with a breakdown by student.
  • Approve: status changes to approved, the student is notified and the action is logged.
  • Edit then approve: the professor edits inline, the edited version is approved, and the original is kept in the log so the student can see the diff.
  • Return: the item goes back to the student with a note, and the student revises and resubmits.
  • The agent does not approve work on its own. The professor approves.

Install the skill from the ZIP

Download the ZIP for the skill from this page. Unzip it into one of two locations, depending on how you want to use it.

For a personal setup, unzip into ~/.claude/skills/. For a single project, unzip into that project's .claude/skills/ folder.

Alternatively, you can upload the ZIP in the Claude apps under Settings → Capabilities → Skills.

  • Personal: ~/.claude/skills/
  • Project only: .claude/skills/ inside the project folder
  • Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Check the requirements before you start

The skill depends on two things. First, a configured claude-for-legal plugin with a legal-clinic CLAUDE.md file at ~/.claude/plugins/config/claude-for-legal/legal-clinic/. The CLAUDE.md file records the clinic's supervision style. Second, a references/review-queue.yaml file that holds the queue entries.

The skill does not run scripts and does not use the network, according to its listing.

  • Configured claude-for-legal plugin with legal-clinic CLAUDE.md at ~/.claude/plugins/config/claude-for-legal/legal-clinic/
  • references/review-queue.yaml holding the queue entries
  • Files in the skill: SKILL.md and references/review-queue.yaml
  • Runs scripts: no. Uses network: no.

Trigger the skill with a request or a command

You can invoke the skill with its slash command. The skill also accepts natural requests when the professor wants to see what is waiting for review, approve, edit then approve, or return an item.

The skill's argument hint lists three forms: --approve ID, --return ID 'note', and --edit ID.

  • Natural request: ask the agent what is waiting for review in the queue.
  • Command to see the queue: /legal-clinic:supervisor-review-queue
  • Command to approve an item: /legal-clinic:supervisor-review-queue --approve Q-003
  • Command to return an item with a note: /legal-clinic:supervisor-review-queue --return Q-004 "Check the service requirement — local rules changed"
/legal-clinic:supervisor-review-queue --approve Q-003

Read the queue entries

Each entry in references/review-queue.yaml has an ID, a type, the client, the student, a submission timestamp, any flags, the path to the document, and a status. Types are intake, draft, memo, status and client-letter. Status is pending, approved, edited-approved or returned.

Flags record the rule that caught the item and a short detail, such as a court filing that is always queued.

  • id: for example Q-001
  • type: intake, draft, memo, status or client-letter
  • status: pending, approved, edited-approved or returned
- id: Q-001 type: "draft" # intake | draft | memo | status | client-letter client: "[name or ID]" student: "[name]" submitted: [timestamp] flags: - rule: "Court filing" detail: "Eviction answer — always queued" content_path: "[path to the document]" status: "pending" # pending | approved | edited-approved | returned

Use the skill to spot teaching patterns

The skill treats the queue as data. A pattern in returns, such as a student repeatedly missing the same requirement, is a prompt for a coaching conversation. A pattern in edits, such as demand letters that are consistently too long, is something to carry into a /ramp update for the next semester.

The skill does not replace case rounds, one-on-ones or watching students in action. It is a gate for work product only.

  • Returns that repeat for one student suggest a coaching conversation.
  • Edits that repeat across students suggest a /ramp update for next semester.

What people use it for

  • A professor checks which deadline-sensitive items, such as a court filing, are waiting before starting the day's reviews.
  • A professor returns a student's client letter with a note asking the student to check a service requirement.
  • A professor edits a student's memo inline and approves the edited version, keeping the original in the log so the student can see what changed.
  • A clinic administrator reviews the log to document that a licensed professional reviewed student work before it went to a client or court.
  • A professor reviews the by-student breakdown to see which students are queueing many items and may need a check-in.

Frequently asked questions

How do I install the supervisor-review-queue skill?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.

What does the supervisor review queue skill require?

It requires a configured claude-for-legal plugin with a legal-clinic CLAUDE.md file at ~/.claude/plugins/config/claude-for-legal/legal-clinic/, and a references/review-queue.yaml file holding the queue entries. According to its listing, it runs no scripts and uses no network.

Is the supervisor review queue skill free?

The source material for this page does not state pricing or licence terms beyond the listing's Apache-2.0 licence. Check the licence file in the repository for the terms that apply.

Why is the skill not doing anything in my clinic?

The skill only activates when the supervision style in the legal-clinic CLAUDE.md is set to formal review queue. If it is set to another style, the skill stays dormant and explains how to switch. Edit the Supervision style entry in CLAUDE.md to change it.

Does the agent approve student work automatically?

No. The skill states that the professor approves. The agent shows pending items and carries out the action the professor chooses, and it is not a substitute for legal review.

How does this compare to other clinic supervision methods?

The skill is one of three supervision models the clinic can choose at setup. A formal queue gates work product before it reaches clients or courts. Clinics that supervise through case rounds and one-on-ones do not need this skill, and it will stay inactive for them.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if your law clinic has chosen a formal review queue and you want student drafts, memos and client letters held until you approve, edit or return them, with every action logged. Pick a different approach if your clinic supervises through case rounds and one-on-ones, because the skill will stay inactive for you, or if you expect the agent to approve work automatically, which it does not do.

Download the skill