Conciseness

The body is two lines — a generation provenance comment and "Load and follow the shared skill at `~/.agents/skills/justfile/SKILL.md`." — with zero padding and no explanation of concepts Claude already knows; every token earns its place.

Actionability

The only guidance is a single high-level pointer to an external file; no task-specific steps, commands, or examples exist in the body itself. Not 1 because the pointer is a specific, executable instruction rather than vague description; not 3 because there is no partial concrete guidance — 100% of task guidance is delegated.

Workflow Clarity

The single delegation step ("Load and follow the shared skill") is unambiguous, but the skill's described scope (creating, editing, reviewing, adding recipes) shows no visible sequence or validation checkpoints — the entire workflow is implicit in an external file. Not 4-5 because the actual task workflow is absent rather than having only minor gaps; not 2 because the one instruction given is precise, not poorly defined.

Progressive Disclosure

There is exactly one clearly signaled, one-level-deep reference and nothing inlined that belongs elsewhere (no bundle files exist in references/, scripts/, or assets/). Not 5 because navigation depends entirely on an external path outside the bundle with no in-file overview of what it covers — a dead end if the shared skill is not installed; not 3 because the reference that exists is clean, unburied, and appropriately shallow.

Specificity

"creating, editing, reviewing, or adding recipes to a justfile, Justfile, or *.just file" lists several concrete actions in a clearly named domain. It falls short of 5 because common justfile activities like running/executing recipes or working with `just` syntax are not covered, and exceeds 3 because more than 1-2 specific actions are explicitly stated.

Completeness

An explicit "Use when invoked as $justfile or when creating, editing, reviewing..." clause answers 'when' concretely, and the 'what' is directly readable from the listed actions. Not 5 because there is no standalone capability statement (the actions are grammatically embedded in the trigger clause); not 3 because the 'when' is explicit and detailed, not missing or weakly implied.

Trigger Term Quality

Natural triggers include "justfile", "Justfile", "*.just", and "recipes", covering synonyms and the file extension. Not 5 because users commonly refer to the `just` command itself (e.g. "run this with just") or to running recipes, and no such trigger term is present; not 3 because synonym and extension coverage is solid rather than partial.

Distinctiveness Conflict Risk

"justfile, Justfile, or *.just file" plus "$justfile" define a clear niche with distinct, file-type-specific triggers. Overlap risk with adjacent build-tool skills is minimal, matching the top anchor rather than the 'minor overlap' anchor at 4.