一键导入
prompt-evaluator
Triggers: "prompt evaluator", "score this prompt", "is this prompt good", "rubric this", "judge this output", "rewrite this prompt".
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Triggers: "prompt evaluator", "score this prompt", "is this prompt good", "rubric this", "judge this output", "rewrite this prompt".
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Triggers: "business ops", "draft proposal", "draft invoice", "vendor compare", "lead intake", "follow-up draft", "meeting summary", "offer review".
Triggers: "compress this", "context bloat", "weekly rollup", "compression strategy", "summary preserving wikilinks".
Triggers: "memory architect", "design memory", "shape the taxonomy", "what type is this", "where does this note belong", "memory lifecycle".
Triggers: "vault engineer", "fix vault", "vault structure", "vault diagnostics", "frontmatter migration", "broken wikilinks".
Triggers: "provider adapter", "13 fields", "activate codex", "activate gemini", "wire local llama", "provider neutral".
Triggers: "migration plan", "migration apply", "what would Round 8 do", "migration rollback", "inventory the repo".
| name | prompt-evaluator |
| description | Triggers: "prompt evaluator", "score this prompt", "is this prompt good", "rubric this", "judge this output", "rewrite this prompt". |
| when_to_use | When the user wants a prompt scored against the rubric, or wants a rewrite proposed. Pure analysis; never auto-applies. |
| inputs | [{"prompt_path":"$VAULT/50-Prompts/<name>.md or arbitrary path"},{"fixture_path":"harness/fixtures/<name>.yml (optional)"},{"rewrite_axis":"brevity | format | persona | safety (optional)"}] |
| steps | ["Read the prompt + the matching fixture (if any) + the user-profile.","Run harness ab if both incumbent + candidate exist; otherwise score one-arm.","Score on the rubric (helpfulness / brevity / format), 1-5 each.","Identify the top failure mode (banned phrases / over-tokens / format-miss).","If rewrite_axis is set, generate one candidate variant in 50-Prompts/<name>.candidate-N.md.","Append a Reflexion lesson via harness reflect (≤ 80 chars)."] |
| tools | ["Read","Write","Bash(harness ab:*,harness reflect:*,harness traces:*)"] |
| failure_modes | ["prompt has no `validated_against:` → suggest /ralph-experiment first","rubric judge unavailable (no ANTHROPIC_API_KEY) → defer with clear error","candidate auto-promoted to incumbent without user approval → REFUSE; HIGH-risk"] |
| last_validated | "2026-05-09T00:00:00.000Z" |
| metrics | {"invocations":0,"success_rate":null,"mean_tokens":null} |
| prerequisites | ["recall"] |
| is_prerequisite_of | [] |
| links | ["[[docs/AB_HARNESS.md]]","[[04_Harnesses/eval-rubric.md]]","[[harness/harness/judge.py]]"] |
| tags | ["skill","specialist","prompt","evaluation"] |
The role you assume when judging prompts (incumbent or candidate). Discipline: never auto-promote; always cite the rubric scores; always attribute failures to one or two causes (not a vague "this is bad").
Given the day-1 fixture harness/fixtures/code-review.yml and the
incumbent seed/50-Prompts/code-review.md, the skill must:
harness ab (or one-arm score if no candidate exists).rewrite_axis: brevity is set, generate
50-Prompts/code-review.candidate-N.md with the preamble removed.Output is a Markdown report ≤ 30 lines.