Content
77%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 well-structured with strong validation checkpoints and feedback loops, but the central fix step lacks concrete guidance and the objective is redundantly restated. Tightening the repetition and adding actionable fix techniques would raise the weaker dimensions.
Suggestions
Add concrete resolution techniques for the common issue types (e.g., replacing internal APIs with public equivalents, adding @NotNull annotations, using PsiElement-based APIs) instead of the abstract 'Resolve the specific issue'.
Remove the redundant restatement of the objective — keep it only in the frontmatter or a single 'Objective' line.
Optionally link a reference file cataloging common verifyPlugin issue types and their known fixes to deepen the core actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean with concrete commands and no over-explanation of known concepts, but the objective is restated three times (frontmatter, opening line, and 'Objective' section), which could be trimmed. | 4 / 5 |
Actionability | Verification steps use concrete executable commands ('./gradlew verifyPlugin', './gradlew runIde'), but the core 'Implement Fix' step is abstract ('Resolve the specific issue') with no concrete technique for actually eliminating an internal/override-only API usage. | 3 / 5 |
Workflow Clarity | A clear six-step sequence with explicit validation checkpoints (baseline testClasses/test, re-run verifyPlugin, test for regressions) and a feedback loop (re-run verifyPlugin to confirm the warning is gone). | 5 / 5 |
Progressive Disclosure | Under 50 lines, single-purpose, and well-organized into clearly labeled sections with no external bundle files to navigate; meets the simple-skill exception for progressive disclosure. | 5 / 5 |
Total | 17 / 20 Passed |