CtrlK
BlogDocsLog inGet started
Tessl Logo

reviewing-cli-command

Provides checklist for reviewing Typer CLI command implementations. Covers structure, Annotated syntax, error handling, exit codes, display module usage, destructive action patterns, and help text conventions. Use when user asks to review/check/verify a CLI command, wants feedback on implementation, or asks if a command follows best practices.

75

Quality

92%

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

85%Weight 40%Scale 1-3

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

A concise, highly actionable checklist skill with executable GOOD/BAD examples, a clear review process, and well-organized sections. The main weakness is redundancy between the 'Common Mistakes' table and the preceding checklists.

Suggestions

Remove or condense the 'Common Mistakes' table, since each row duplicates a checklist item already stated above (print/exit codes/--force/default=False/Annotated/app/registration), to recover the token budget.

If the table is retained as a quick-reference, replace the duplicated checklist items with only the non-obvious gotchas not already covered above.

Briefly define the [!] severity marker in the 'Review Output Format' block so the OK/X/! distinction is unambiguous to the reviewer.

DimensionReasoningScore

Conciseness

The body is lean with no concept padding, but the 'Common Mistakes' table largely mirrors the checklists above (print->display, exit codes, --force, default=False, Annotated syntax, app=typer.Typer(), add_typer registration), so not every token earns its place.

2 / 3

Actionability

GOOD/BAD code blocks are executable and copy-paste ready (Annotated arguments, display.error() with raise typer.Exit(), typer.confirm(default=False)), with concrete exit codes 0/1/2 and specific flags.

3 / 3

Workflow Clarity

The 'Review Process' gives a clear three-step sequence (read -> check sections -> report) with checklist items as validation checkpoints and a defined output format; a review skill does not require an edit-fix-retry loop.

3 / 3

Progressive Disclosure

No bundle files exist and the single cohesive checklist is well-organized into clearly headed sections with no nested references, so the simple-skill well-organization criterion is met.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 strong, specific description with an explicit 'Use when...' trigger clause and concrete covered areas, written in third person. It clearly communicates both capability and activation conditions.

DimensionReasoningScore

Specificity

The description lists multiple concrete areas — 'structure, Annotated syntax, error handling, exit codes, display module usage, destructive action patterns, and help text conventions' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It explicitly answers both what ('Provides checklist for reviewing Typer CLI command implementations. Covers...') and when via an explicit 'Use when...' clause, satisfying the top anchor.

3 / 3

Trigger Term Quality

The trigger clause uses natural user phrasings — 'review/check/verify a CLI command', 'wants feedback on implementation', 'asks if a command follows best practices' — giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The niche is narrowly scoped to Typer CLI command review with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
https-deeplearning-ai/sc-agent-skills-files
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.