CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.40x
Quality

Does it follow best practices?

Impact

100%

1.40x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and clearly organized for a simple command-runner skill, with executable examples throughout. Its main weakness is redundancy across the Tools, Examples, and When-to-Use sections.

Suggestions

Consolidate the Tools table into the Usage Examples section to remove duplicated 'just'/'just test' rows.

Trim the 'When to Use' bullet list so it states the decision criteria rather than re-listing commands already shown in examples.

Merge the standalone 'Best Practice' snippet into 'Discovery' since both cover listing recipes on entering a project.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept-explaining fluff, but the Tools table, Usage Examples, and 'When to Use' sections repeat the same 'just test'/'just build' commands, so it could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands ('just', 'just test', 'just --list', 'just --show test', 'just --summary') plus a complete example justfile with real recipes.

3 / 3

Workflow Clarity

For a simple single-purpose skill the action is unambiguous, and the 'When to Use'/'Discovery' sections sequence the flow (check justfile first, then run recipes) without needing validation checkpoints for non-destructive operations.

3 / 3

Progressive Disclosure

The body is a self-contained simple skill with no need for external references, and it is well-organized into clearly labeled sections (Purpose, Tools, Usage Examples, Discovery, When to Use, Best Practice).

3 / 3

Total

11

/

12

Passed

Description

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.

The description is specific, complete, and rich in natural trigger terms, with only minor overlap risk from generic project-task phrasing. It is written in third person and avoids fluff.

Suggestions

Tie trigger terms more tightly to just (e.g., 'justfile recipes', 'run just task') to reduce overlap with generic build/test runners.

Consider dropping or narrowing 'run script' and 'project commands', which are broad enough to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Check for justfile in project root, list available tasks, execute common operations like test, build, lint') rather than vague language.

3 / 3

Completeness

Explicitly states what the skill does ('Run project commands with just...') and when to use it via an explicit 'Triggers on' clause, satisfying both what and when.

3 / 3

Trigger Term Quality

'Triggers on: run tests, build project, list tasks, check available commands, run script, project commands' covers natural phrases a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The 'just'/'justfile' framing is a distinct niche, but generic trigger terms like 'run tests' and 'build project' could overlap with make/npm-script runner skills, so it is not a clear 3.

2 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.