Content
100%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.
An exceptionally lean, directive workflow skill: every step is concrete and executable, validation and feedback loops are explicit, and risky actions (commit, push, CI changes) are guarded. Structure and navigation are clean with appropriately shallow references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is pure directive content — commands like `git log next..HEAD --oneline`, `pnpm --filter @novu/api-service build`, and the commit format `type(scope): concise why fixes NV-XXX` are given without any concept explanation or padding. It assumes Claude's competence throughout; nothing can be trimmed without losing information. | 5 / 5 |
Actionability | Guidance is fully executable: concrete git/pnpm/gh commands, a change-type-to-check mapping table, exact commit and PR title formats, and named skills to load for each situation. Copy-paste-ready commands cover the common cases (build checks, e2e runs, PR creation). | 5 / 5 |
Workflow Clarity | Nine explicitly sequenced steps with a tracked checklist, a dedicated local-validation step (4), a CI triage step with feedback-loop decision branches (deterministic vs flake), and a merge-ready checklist with stop conditions. Risky operations are guarded ('Commit only when the user asks', 'Never modify CI config/workflows'), so no validation cap applies. | 5 / 5 |
Progressive Disclosure | No bundle files exist and none are needed; the single file is well-sectioned with numbered headers and a Related skills section. References to sibling skills (run-api-e2e-tests, verify-in-box, enterprise-submodule) are one level deep and clearly signaled, with no content inlined that belongs in a separate file. | 5 / 5 |
Total | 20 / 20 Passed |