respond-to-eval · git:20261106.a8c8716 · 2026-11-06 · sha256 e9b1b65452ad9c2d

respond-to-eval git:20261106.a8c8716A

Immutable. This exact content never changes and is served at /api/v1/blob/e9b1b65452ad9c2d.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_dkqohiybtzrioryx/e9b1b65452ad9c2d3e3e3ecc0a8abaa6a513b06d6cd30e7da94205b36b6cbd60.json

Then /plugin install respond-to-eval@markdownregistry-dkqohiybtzrioryx in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: respond-to-eval
description: Turn student course evaluations (free-text + numeric) into an actionable teaching-improvement plan — the teaching analogue of /respond-to-referees. Clusters comments into themes, separates signal from noise, classifies each theme Keep / Change / Investigate / Out-of-scope, and drafts concrete changes mapped to the syllabus and slide decks. Use when user says "respond to my evals", "what do these course evaluations tell me", "turn my teaching feedback into a plan", or after a semester's evals arrive.
---
<!-- Generated by scripts/sync-agent-skills.py from .claude/skills/respond-to-eval/SKILL.md. Do not edit: change the source and re-run the script. -->

# respond-to-eval

This skill's instructions live in [`.claude/skills/respond-to-eval/SKILL.md`](../../../.claude/skills/respond-to-eval/SKILL.md).
Read that file now and follow it, with the files it points to. Read [`AGENTS.md`](../../../AGENTS.md)
first if you have not already.

It was written for Claude Code. Running it from Codex, Antigravity or another agent:

- **Arguments.** Where it says `$ARGUMENTS`, use what the user asked for.
- **Claude Code agents.** Where a step hands work to an agent in `.claude/agents/` (through the
  `Agent` or `Task` tool), do that step where it appears in the procedure: never later, and never
  skip it. A step that gates what follows still gates it (`/commit` runs its verifier before it
  commits). Read the agent's file for what the step checks.
- **Fresh context.** If the step needs a context that has not seen your work, for example a claim
  verifier that must never see the draft, run it in a separate session or worker that has not
  seen the draft, if your tool can start one, and give it only what the step says to pass. If it
  cannot, do the step yourself, mark every result it produced *not independently verified*, and
  tell the user to repeat that check in Claude Code (`/verify-claims` for citations) before
  relying on it.
- **Claude Code settings.** `allowed-tools`, `model`, `effort`, `argument-hint` and
  `disable-model-invocation` in the source's frontmatter configure Claude Code. Ignore them.
- **Guards.** Claude Code's guard hooks do not run for you. Follow the rules in `AGENTS.md`
  yourself; the git pre-commit gate and CI still apply to your commits.