Content
80%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 lean, well-organized single-purpose skill with concrete file targets, but it lacks a verification checkpoint before pushing to main and does not specify how to look up the star count.
Suggestions
Add an explicit method to fetch the star count (e.g., a GitHub API endpoint or URL) so the first step is fully executable rather than left to inference.
Insert a validation checkpoint before committing/pushing to main, such as confirming the rounded count is lower than the current displayed value and that the three files still build, to satisfy the workflow-clarity feedback-loop requirement.
State the commit message convention (e.g., 'chore: update GitHub star count') to make the final push step concrete and consistent.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean body with no padding or restated common knowledge; every line (round-down rule, file list, push target) earns its place and assumes Claude's competence. | 5 / 5 |
Actionability | Concrete guidance via three specific file paths and an explicit round-down rule, but "Check on GitHub how many stars Remotion has" omits the exact lookup method (API endpoint/URL), leaving a minor gap that prevents a 5. | 4 / 5 |
Workflow Clarity | A clear sequence exists (check, round, update three files, commit and push to main), but pushing to main and batch-editing three files is a destructive/batch operation with no validation checkpoint, capping this dimension at 3 per the rubric. | 3 / 5 |
Progressive Disclosure | A simple single-purpose skill under 50 lines with no external references and well-organized sections (rule, file list, push instruction), meeting the simple-skill exception for a 5. | 5 / 5 |
Total | 17 / 20 Passed |