Content
71%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.
A well-organized, actionable review skill body that avoids concept padding and offers concrete anti-patterns and thorough checklists. Its main weaknesses are missing referenced rule files (broken progressive disclosure) and an inline time-sensitive date that should be quarantined.
Suggestions
Ship the referenced rules/1-safety.md through rules/5-legal.md files (or remove the table links) so the progressive-disclosure navigation resolves.
Move the "Guidelines current through: June 8, 2026" statement into a dated/changelog or deprecated-guidance section so stale time-sensitive data does not clutter the overview.
Add a short numbered review workflow (e.g., identify platform → load relevant rule file → run matching checklist → report findings by risk level) to make the end-to-end process explicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Largely lean and actionable — tables, anti-pattern code snippets, and checklists with minimal concept re-explanation — but the inline time-sensitive claim "Guidelines current through: Apple's June 8, 2026 App Review Guidelines update" is not isolated in a deprecated/old-patterns section, a minor efficiency penalty. | 4 / 5 |
Actionability | Provides concrete, recognizable code anti-patterns (e.g. "NSSelectorFromString(\"_privateMethod\")", "eval(downloadedCode)", "StoreReview.requestReview()") plus sectioned checklists; mostly executable guidance with minor gaps since examples illustrate what to avoid rather than full copy-paste solutions. | 4 / 5 |
Workflow Clarity | Organization by category with explicit per-section checklists (Privacy, Payments, Safety, Performance, Design, Legal) supplies clear validation checkpoints; the end-to-end review sequence is implicit rather than numbered, a minor gap that keeps it below 5. | 4 / 5 |
Progressive Disclosure | The guideline-sections table signals one-level-deep references cleanly, but the referenced rule files (rules/1-safety.md ... rules/5-legal.md) are absent from the bundle, so the disclosure navigation is partially broken and the body must stand alone. | 3 / 5 |
Total | 15 / 20 Passed |