CtrlK
BlogDocsLog inGet started
Tessl Logo

cli-output-review

Review fallow's human-readable CLI output for scanability, information hierarchy, empty states, and terminal compatibility. Use when changes affect human output, command UX, or text formatting in the CLI.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

A tight, well-structured reviewer skill that loads context from two clearly signaled references and ends with a concrete deliverable. It is token-efficient and well-organized, with only minor gaps in explicit verification steps.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept explanations, just file paths, a review target, focus areas, and a required verdict — so every token earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

It gives concrete pointers (exact file paths to read, the `crates/cli/` path to review, explicit focus dimensions, and a required APPROVE/CONCERN/BLOCK output) but stops short of fully executable review steps, fitting 'mostly executable guidance; minor gaps'.

4 / 5

Workflow Clarity

A clear sequence is present — Read the listed files, review the concrete output path, apply the focus areas, end with a verdict — with most checkpoints in place; it is not a destructive/batch operation so the validation cap does not apply, but a couple of verification steps are implicit rather than explicit.

4 / 5

Progressive Disclosure

A short, well-organized overview points to two clearly signaled one-level-deep references under 'Read:' with no nested indirection; for a sub-50-line skill this matches the top anchor, and the referenced files are real repo paths rather than missing bundle entries.

5 / 5

Total

18

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, well-constructed description that clearly states both capability and trigger conditions in third person. It is specific, distinct, and uses natural trigger language with only minor keyword-coverage gaps.

DimensionReasoningScore

Specificity

Names the domain (CLI output review) and several concrete review dimensions — 'scanability, information hierarchy, empty states, and terminal compatibility' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the comprehensive 5.

4 / 5

Completeness

It explicitly answers both what ('Review ... CLI output for scanability, information hierarchy, empty states, and terminal compatibility') and when ('Use when changes affect human output, command UX, or text formatting in the CLI') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

The 'Use when changes affect human output, command UX, or text formatting in the CLI' clause supplies good natural keywords a user would say, though a few common variations are missing, placing it just below the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'fallow's human-readable CLI output' review with distinct triggers around command UX and text formatting, giving it a clear niche with minimal overlap with other skills.

5 / 5

Total

18

/

20

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
fallow-rs/fallow
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.