CtrlK
BlogDocsLog inGet started
Tessl Logo

acme-versioned-custom-commands

How to author custom commands for the acme-versioned CLI using the co-generated SDK.

59

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./seed/cli/cli-multi-spec-namespaced/no-custom-config/.agents/skills/custom-commands/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The body is a lean, highly actionable guide with executable code and clear sequencing. It is well structured for a single-file skill; its main gap is the absence of an explicit validation checkpoint in the workflow.

DimensionReasoningScore

Conciseness

Largely lean and efficient with tight code examples and no basic-concept over-explanation; minor instances of restated padding (e.g. 'No manual auth wiring is needed' after 'automatically inherit the CLI's authentication').

4 / 5

Actionability

Fully executable copy-paste-ready Rust register() example, a concrete sub-client table, and specific build/test commands including RUST_LOG debugging cover the common cases.

5 / 5

Workflow Clarity

Clear numbered sequence (edit custom.rs, use SDK clients, key patterns, auth) plus a build/test verification block; minor validation gaps but no explicit validate-then-proceed checkpoint.

4 / 5

Progressive Disclosure

Well-organized single-file guide with clear section headers and easy navigation; no bundle files are needed, though the SDK client/pattern reference could arguably be split into a separate file.

4 / 5

Total

17

/

20

Passed

Description

53%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.

The description clearly states what the skill covers but omits any 'when to use' trigger guidance, which caps its completeness. It is distinct and reasonably specific but would benefit from natural trigger phrases and broader keyword coverage.

Suggestions

Add a 'Use when ...' clause naming concrete trigger situations, e.g. 'Use when extending the acme-versioned CLI or adding user-authored commands'.

Broaden trigger-term coverage with natural synonyms users might say ('add a command to acme-versioned', 'extend the CLI', 'register a custom subcommand').

List one or two more concrete actions (e.g. 'register, wire, and compile custom commands') to lift specificity toward a 4-5.

DimensionReasoningScore

Specificity

Names the domain ('custom commands for the acme-versioned CLI') and one concrete action ('author ... using the co-generated SDK'), but lists only 1-2 actions rather than comprehensive coverage.

3 / 5

Completeness

Provides a clear 'what' (author custom commands using the SDK) but has no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Relevant keywords ('custom commands', 'CLI', 'SDK') are present but missing common variations or synonyms a user might naturally say; no file extensions or alternate phrasings.

3 / 5

Distinctiveness Conflict Risk

Targets a uniquely named CLI (acme-versioned), giving it a clear niche with minimal conflict risk; the brief description keeps it just shy of full distinctiveness.

4 / 5

Total

13

/

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
fern-api/fern
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.