Stats
Actions
Tags
From workflow-tools
This skill should be used when creating or editing documents, diagrams, handover docs, PEPs, or any substantial written output. Also activates when the user says "evaluate this", "run in a loop until good", "rate this out of 10", "is this 10/10", "loop until fixed", "keep improving", or asks for iterative quality improvement on any output.
How this skill is triggered — by the user, by Claude, or both
Slash command
/workflow-tools:self-evaluatingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run a quality check on documents, diagrams, and written output before presenting. Iterate when the result is not good enough.
Run a quality check on documents, diagrams, and written output before presenting. Iterate when the result is not good enough.
Score each dimension 1-10:
| Dimension | What to check |
|---|---|
| Accuracy | Everything factually correct based on the code? No guesses stated as facts. |
| Clarity | Someone with basic context can follow without re-reading? |
| Completeness | Obvious gaps or missing pieces? |
| Natural voice | Reads like a human wrote it? (Apply writing-naturally skill criteria) |
For diagrams only, add:
| Dimension | What to check |
|---|---|
| Visual flow | Clear start and end points? No spaghetti? |
| Labels | Every arrow and connection labelled? |
| Accessibility | Someone with no system knowledge can follow the flow? |
When the user asks to "loop until 10/10" or similar, keep iterating until all scores hit 8+. State what improved between iterations.
npx claudepluginhub denisraison/claude-plugins --plugin workflow-toolsReviews brainstorms, plans, PRDs for clarity, completeness, specificity, YAGNI violations, vagueness, and gaps before workflow handoff. Scores criteria and flags blocking issues.
Scores own output 0-10 across 5 task-appropriate dimensions before emitting. Used as a pre-emit gate for complex work where grade-inflation is a risk.
Refines brainstorm and plan documents by assessing clarity, completeness, specificity, YAGNI, and scope issues, then auto-fixes minor problems or proposes substantive changes before next workflow steps.