CtrlK
BlogDocsLog inGet started
Tessl Logo

api-custom-commands

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

64

Quality

75%

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/file-upload-openapi/.agents/skills/custom-commands/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The SKILL.md body is lean, executable, and well-structured: it gives copy-paste-ready Rust code, concrete build/test commands, a regeneration-safety table, and clear sectioned navigation without explaining concepts Claude already knows. It is a strong, token-efficient reference for authoring custom api CLI commands.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no preamble explaining what a CLI or SDK is; real code and dense tables carry the content, with only minor redundancy in repeated build commands.

3 / 3

Actionability

It provides fully executable Rust (register(), client(), block_on()), concrete cargo/api commands, and copy-paste key-pattern snippets, matching the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Adding a command is laid out as a clear numbered sequence (edit custom.rs, build, run, patterns, auth) with a debug feedback step (RUST_LOG=debug); the task is straightforward code-edit/build rather than a destructive operation requiring validate loops.

3 / 3

Progressive Disclosure

The skill is single-purpose and well-organized into clear sections with no bundle files and no nested references; the body points only at in-repo code paths, so the well-organized single-file structure earns the top score.

3 / 3

Total

12

/

12

Passed

Description

50%

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 concrete and narrowly scoped to authoring custom commands for the api CLI, but it lacks an explicit 'Use when...' trigger clause and leans on technical jargon ('co-generated SDK') that users would not naturally say. It is competent but sits at the midpoint of the rubric.

Suggestions

Add an explicit trigger clause such as 'Use when extending the api CLI with new commands or wiring custom handlers to the generated SDK.'

Replace or gloss the jargon 'co-generated SDK' with user-natural phrasing like 'generated SDK' or 'typed API client'.

Enumerate concrete actions (e.g., 'register, wire, and test custom commands') to raise specificity.

DimensionReasoningScore

Specificity

It names a concrete domain ('custom commands for the api CLI') and a specific action ('author') plus the mechanism ('co-generated SDK'), but lists only a single action rather than enumerating multiple concrete capabilities, matching the 'names domain and some actions' anchor.

2 / 3

Completeness

It clearly answers 'what' (author custom commands for the api CLI) but provides no explicit 'Use when...' trigger guidance, so 'when' is only implied — the rubric caps completeness at 2 in this case.

2 / 3

Trigger Term Quality

'custom commands' and 'api CLI' are terms a user might say, but 'co-generated SDK' is technical jargon users would not naturally voice and common variations are missing, fitting the 'some relevant keywords but missing variations' anchor.

2 / 3

Distinctiveness Conflict Risk

It is scoped to a named CLI's custom-command authoring, which is a distinct niche, but the absence of explicit trigger phrasing leaves it somewhat overlapping with general CLI/SDK skills rather than unambiguous.

2 / 3

Total

8

/

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