Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with executable examples and a clear sequence, and it correctly offloads detail to a real reference file. It loses points for repeated relay/maxConcurrency guidance and for inlining API-reference detail that duplicates the reference file.
Suggestions
De-duplicate the relay/maxConcurrency and llm-rubric-provider rules: state them once in the Relay section and Troubleshooting, and remove the repeated restatements in Configuration Structure and Best practices.
Move the Common Assertion Types table and provider/CLI reference detail into references/promptfoo_api.md, keeping only a short pointer and the most-used types inline in SKILL.md.
Add an explicit validation checkpoint before the first eval run, e.g. preview with the echo provider or run `npx promptfoo@latest eval -j 1` on one test case to confirm the config loads.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with tight code blocks and high-value gotchas, but the relay/maxConcurrency and llm-rubric-provider rules are repeated across Configuration Structure, Relay section, Troubleshooting, and Best practices, so it sits below the lean level-5 anchor yet above the padded level-3 anchor. | 4 / 5 |
Actionability | Provides copy-paste-ready YAML and Python plus specific commands ('npx promptfoo@latest eval --filter-metadata category=math') covering common cases, matching the fully-executable anchor; not below because examples are concrete and complete rather than pseudocode. | 5 / 5 |
Workflow Clarity | The init → configure → run → view sequence is clear with a Troubleshooting error→fix section and an echo-provider preview loop, but the main eval flow lacks an explicit 'validate config before first run' checkpoint, placing it below the level-5 anchor with explicit validation. | 4 / 5 |
Progressive Disclosure | Clear section structure with one-level-deep references to the real references/promptfoo_api.md and scripts/metrics.py, but a substantial amount of API/assertion-table detail is inlined in SKILL.md and duplicated in the reference file, so it is above the level-3 'should be separate is inline' anchor but below the cleanly-split level-5 anchor. | 4 / 5 |
Total | 17 / 20 Passed |