CtrlK
BlogDocsLog inGet started
Tessl Logo

api-custom-commands

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

56

Quality

64%

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

Quality

Content

75%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 lean, actionable, and well-structured with complete executable code and a clear build/test workflow, falling just short of top marks due to thin SDK-client coverage and only implicit validation checkpoints.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Rust/clap/serde competence, with only minor redundancy between the Architecture listing and the Regeneration Safety table, fitting the efficient-with-minor-trim anchor above the midpoint.

4 / 5

Actionability

Concrete, executable guidance dominates — a complete copy-paste `register()` handler, `client()`/`block_on()` patterns, and `cargo build`/`api get-movie` commands — but the SDK clients table shows only a single row, leaving a minor coverage gap.

4 / 5

Workflow Clarity

The edit → build → test sequence is clear and the test invocation acts as a verification step, but explicit validation/error-recovery checkpoints are only implicit, matching the clear-sequence-with-minor-validation-gaps anchor.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed self-contained sections with no nested references and no bundle files needed, fitting the good-structure anchor; it is a single focused file rather than an overview pointing to deeper materials.

4 / 5

Total

16

/

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 names a specific niche and one concrete action, but it lacks any explicit "when to use" trigger guidance and relies on somewhat technical terms, capping completeness and trigger quality at the midpoint.

Suggestions

Add an explicit "Use when..." clause naming natural triggers, e.g. "Use when adding or modifying user-authored commands for the api CLI."

Broaden trigger terms with natural synonyms users would say ("add a command", "extend the api CLI", "CLI plugin") instead of relying on "co-generated SDK".

List one or two more concrete actions (e.g. "register, wire up, and test custom commands") to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

"How to author custom commands for the api CLI" names the domain and one concrete action (authoring custom commands) but lists no further specific actions, matching the anchor for domain plus 1-2 actions without comprehensive coverage.

3 / 5

Completeness

The description gives a clear "what" (authoring custom commands for the api CLI) but includes no "Use when..." clause or equivalent trigger guidance, so per the missing-trigger cap it cannot exceed 3.

3 / 5

Trigger Term Quality

"custom commands" and "api CLI" are relevant natural keywords, but "co-generated SDK" is jargon and common variations/synonyms (e.g., "add command", "CLI plugin", "extend api") are missing, so it sits at the some-keywords anchor rather than comprehensive coverage.

3 / 5

Distinctiveness Conflict Risk

The "api CLI" + "custom commands" + "co-generated SDK" niche is mostly distinct with only minor overlap risk against other CLI-command-authoring skills, fitting the mostly-distinct anchor above the midpoint.

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.