| name | create-eval |
| description | Generate project-specific service-eval skill. NOT for running existing evals or adversarial audits. |
| when_to_use | create eval, create service-eval criteria, scaffold service-eval skill |
| user-invocable | true |
Create service-eval
Generate .claude/skills/service-eval/SKILL.md for the current project.
The service-eval skill runs periodically to read logs, verify
correctness, and generate improvement specs when issues are found. It
is the routine-health pass; for adversarial pre-publication review,
see cto-eval (code), ceo-eval (demo), and hacker-eval (security/red-team).
Process
- Read CLAUDE.md, README, specs/, ARCHITECTURE.md, docs/
- Identify what this project does and what "correct" means
- Ask user: what does "good" look like? What does "best" look like?
- Ask user about known failure modes
- Logs: check ops skill, /srv/log, /var/log, or ask
- Write
.claude/skills/service-eval/SKILL.md with:
- Log locations and what to grep for
- Health checks (pass/fail criteria from logs)
- When to generate improvement specs (to specs/ or .ship/)
Rules
- ALWAYS read project docs before generating
- NEVER include generic criteria — derive everything from the project
- NEVER generate without asking the user first
- ALWAYS express assertions as programmatically checkable (grep counts,
thresholds, exit codes) — NEVER "looks healthy" / "works well"
- ALWAYS sanity-check the generated eval against real log samples before declaring it done