Scores a research output against the 5-criteria rubric via Sonnet.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add dbc-oduffy/coordinator-claude --skill eval-output --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Eval Output?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dbc-oduffy-eval-output)More formats (shields.io, HTML) on the badges page.
---
name: coordinator:eval-output
description: "Scores a research output against the 5-criteria rubric via Sonnet."
---
# Evaluate Research Output
## Usage
/coordinator:eval-output <path-to-research-output>
## Process
1. Read the eval rubric at `${CLAUDE_PLUGIN_ROOT}/pipelines/deep-research/eval-rubric.md`
2. Read the research output at the provided path
3. Dispatch a Sonnet agent (model: sonnet, tools: Read, WebFetch, Write) with:
- The rubric
- The research output
- Instruction to: read the output, sample 3-5 cited URLs via WebFetch to verify citation accuracy, score each of the 5 criteria with a 0.0-1.0 score and 2-3 sentence justification, provide overall pass/marginal/fail grade
4. Present the scores to the PM
## Notes
- This is a post-hoc quality check, not a gate. Use it to calibrate prompt improvements.
- Start by running it on recent pipeline outputs to establish a baseline.
- Anthropic found a single LLM call with a single prompt was most consistent.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...