CtrlK
BlogDocsLog inGet started
Tessl Logo

api-wide-base-path-with-default-custom-commands

How to author custom commands for the api-wide-base-path-with-default CLI using the co-generated SDK.

60

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./seed/cli/api-wide-base-path-with-default/.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 strong, executable guide: a complete register() example, SDK client table, regeneration-safety matrix, and working build/test commands. Its weaknesses are minor — some duplicated code/command blocks across sections and no explicit error-recovery loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no basic-concept explanations — but build/run commands are duplicated between the 'Adding a Custom Command' section and 'Build & Test', and 'Key Patterns' restates code already shown in the full example, so minor trimming is possible.

4 / 5

Actionability

The register() example is complete, copy-paste-ready Rust with real clap wiring, backed by cargo build commands, an actual invocation line, an SDK sub-client table, and a RUST_LOG=debug debugging tip — fully executable with nothing pseudocode or missing.

5 / 5

Workflow Clarity

A clear sequence is present (edit custom.rs -> cargo build -> run the command) and the regeneration section explicitly covers what to do when the SDK surface changes, but there is no explicit validate/fix/retry loop (e.g. what to do on build failure), which anchor 5 requires.

4 / 5

Progressive Disclosure

This single-file skill has no bundle directories, and its sections (Overview, Architecture, step-by-step authoring, regeneration-safety table, build/test) are well organized with all content directly load-bearing; the only gap is the duplication between 'Key Patterns', 'Build & Test', and the main example.

4 / 5

Total

17

/

20

Passed

Description

57%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 is concise and unambiguous about its niche, anchored by a very specific CLI name, but it omits any 'when to use this' trigger guidance and lists only one or two concrete actions. It reads more like a title than a triggerable description.

Suggestions

Add an explicit 'when' clause, e.g. 'Use when adding or modifying commands in the api-wide-base-path-with-default CLI, or when the user asks to extend the CLI with new subcommands.'

Enumerate the concrete actions covered, such as registering commands in custom.rs, wiring clap args to SDK calls via client(ctx) and block_on(), and preserving custom code across fern generate.

Include natural trigger terms users would actually say, such as 'custom command', 'add a CLI command', 'extend the CLI', and the file name 'custom.rs'.

DimensionReasoningScore

Specificity

The description names a concrete domain ("custom commands for the api-wide-base-path-with-default CLI") and 1-2 concrete actions ("author custom commands", "using the co-generated SDK"), but does not enumerate several specific actions like the anchor-4 example does.

3 / 5

Completeness

It has a clear 'what' (authoring custom commands via the co-generated SDK) but no 'Use when...' clause or equivalent trigger guidance; per the judging guidelines a missing 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present ("custom commands", "CLI", "SDK") but common natural variations users would say ("add a command", "extend the CLI", "custom.rs") are missing, matching the anchor for some-relevant-keywords-with-missing-synonyms.

3 / 5

Distinctiveness Conflict Risk

The uniquely named CLI ("api-wide-base-path-with-default") gives the skill a clear niche with essentially no overlap risk against other skills, matching the anchor for clear-niche-minimal-conflict.

5 / 5

Total

14

/

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.

Validation — 16 / 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.