task-runner
Run project commands with just. Check for justfile in project root, list available tasks, execute common operations like test, build, lint. Triggers on: run tests, build project, list tasks, check available commands, run script, project commands.
92
88%
Does it follow best practices?
Impact
100%
1.40xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description that clearly identifies the tool (just/justfile), lists concrete capabilities, and includes explicit trigger terms. Its main weakness is that several trigger terms ('run tests', 'build project', 'run script') are generic enough to conflict with other task runner or build system skills, which could cause selection ambiguity in a multi-skill environment.
Suggestions
Differentiate more clearly from other task runners (Make, npm scripts, etc.) by emphasizing 'justfile' more prominently in trigger terms, e.g., 'Triggers on: justfile, just commands, just run, ...'
Add a negative boundary like 'Not for Makefiles, npm scripts, or other build systems' to reduce conflict risk with similar skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: check for justfile, list available tasks, execute operations like test/build/lint. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (run project commands with just, check for justfile, list tasks, execute operations) and 'when' (explicit 'Triggers on:' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'run tests', 'build project', 'list tasks', 'check available commands', 'run script', 'project commands'. These cover common variations of how users would phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | While 'just' and 'justfile' are distinctive, trigger terms like 'run tests', 'build project', and 'run script' are generic enough to overlap with Makefile, npm scripts, or other task runner skills. The description could conflict with similar build/task runner tools. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A solid, actionable skill with clear executable examples and good organization. Its main weakness is some unnecessary content: the example justfile showing recipe implementations and the explanation of what just is add tokens without teaching Claude anything new. The discovery commands section is a genuine value-add.
Suggestions
Remove the 'Common justfile Recipes' example block—Claude doesn't need to see what justfile contents look like to execute just commands.
Trim the Purpose line to remove the explanation of what just is ('simpler than make, cross-platform') since Claude already knows this.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary content. The 'Purpose' line explaining what just is ('simpler than make and works cross-platform') is information Claude already knows. The example justfile showing recipe implementations (pytest, npm run build, etc.) is padding—Claude doesn't need to see what a justfile looks like to use just. The 'When to Use' section largely repeats the usage examples. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready commands throughout. The bash examples for listing, running, and discovering recipes are concrete and specific. The discovery commands (--summary, --show, --list) are particularly useful actionable guidance. | 3 / 3 |
Workflow Clarity | For this simple, single-purpose skill, the workflow is clear and unambiguous: check for justfile first, then list available recipes, then run them. The 'When to Use' section provides a clear sequence starting with discovery. No destructive or batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (basic usage, common recipes, discovery, when to use, best practice). No external file references are needed and the structure is clean. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
9f4534c
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.