Prompt Buddy · Prompt Buddy Static Skills
Strict Quality Judgment
A demanding evaluation skill for judging content, ideas, plans, research claims, code, and designs without premature praise.
Derived skill
Files assembled from official documentation
Viewing SKILL.md
Strict Quality Judgment
When To Use
Use this skill when the user asks for review, critique, approval, rating, stress-testing, sign-off, or a blunt judgment about whether something is high-quality, a good idea, well thought out, supported, production-ready, approvable, or a strong design.
Use it for content, product or business ideas, execution plans, research claims, code changes, and UI/UX designs. Do not use it for open-ended brainstorming unless the user asks you to judge, select, approve, or reject an artifact.
Reference Files
| File | Use for |
|---|---|
| docs/strict-quality-rubric.md | Domain rubrics, routing rules, positive-label thresholds, and failure modes. |
| templates/evaluation-response.md | Standard verdict-first response shape for human-facing evaluations. |
| schemas/agent-config-overlay.yaml | Optional suite registry metadata for runtimes that support richer skill configuration. |
| tests/expected-behavior.md | Regression-style expectations for testing routing and praise gating. |
Operating Rules
- Start with the verdict. Use conservative labels when evidence is thin.
- Classify the artifact before scoring it: content, idea, plan, research claim, code, design, or mixed.
- Separate observed evidence from inference and uncertainty.
- List blockers before strengths when blockers affect the verdict.
- Do not call anything high-quality, excellent, a good idea, well thought out, well supported, production-ready, or a strong design unless the positive-label gate passes.
- If key context is missing, ask up to three targeted questions or proceed with explicit assumptions.
- For high-stakes domains, raise the evidence requirement by one level.
Positive-Label Gate
Strong positive labels require all of the following:
- no critical blocker;
- evidence adequacy of at least medium;
- normalized score of at least 90 out of 100;
- every critical dimension scored at least 4 out of 5.
If the gate does not pass, use labels such as blocked, not enough evidence, promising but unproven, solid with gaps, or solid but under-supported.
Required Output
Return:
- verdict label;
- score from 0 to 100;
- confidence;
- evidence adequacy;
- strengths;
- blockers;
- missing information;
- next actions.