CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

server-url-templating-api-single-base-url-custom-commands

How to author custom commands for the server-url-templating-api-single-base-url CLI using the co-generated SDK.

Quality

68%

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/server-url-templating-single-url/.agents/skills/custom-commands/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 delivers a tight, mostly executable recipe for adding custom commands, with good structure and an excellent regeneration-safety table. Its main defect is an empty 'Available SDK Clients' section and placeholder SDK calls that leave the reader without the actual API surface or where to find it. Workflow and organization are solid, with only minor validation and duplication issues.

Suggestions

Fill in the 'Available SDK Clients' section with the actual sub-clients from the generated API spec, or replace it with a concrete pointer (e.g., 'browse server-url-templating-api-single-base-url-sdk/src/api/ for the full surface').

Replace the placeholder 'client.resource.get(id)' with a real call from this API's SDK so the example is genuinely copy-paste ready.

Add an explicit verification step after building, such as checking the command appears in 'server-url-templating-api-single-base-url --help' before running it, and drop the duplicated client/block_on snippets in 'Key Patterns'.

DimensionReasoningScore

Conciseness

The body is lean — a file-layout diagram, one code example, a regeneration-safety table, and build commands — with only minor trimming opportunities, chiefly the 'Key Patterns' section repeating the 'super::sdk::client(ctx)' and 'super::sdk::block_on' lines already shown in the section 1 example. It is not a 5 because of that duplication, and not a 3 because there is no padded explanation of concepts Claude already knows.

4 / 5

Actionability

The registration scaffold, file paths, and build commands are concrete, but the 'Available SDK Clients' section says 'with the following sub-clients:' and then lists nothing, and the example's 'client.resource.get(id)' is a placeholder with no pointer to where real SDK methods can be found. This is 'concrete guidance but incomplete; missing key details' rather than a 4, since an entire promised section is empty and the core SDK call is unverifiable from the skill.

3 / 5

Workflow Clarity

The flow is clearly sequenced — edit custom.rs, build with 'cargo build', run the command, debug with 'RUST_LOG=debug' — and running the command acts as a test checkpoint. It falls short of 5 because there is no explicit verification step (e.g., confirming the command appears in '--help') or error-recovery guidance, and stays at 4 rather than 3 because the sequence is complete and the run/debug steps function as implicit checkpoints.

4 / 5

Progressive Disclosure

With no bundle files present, the ~100-line body is organized into clear, well-scoped sections (Architecture, Adding a Custom Command, Regeneration Safety, Build & Test) that are easy to navigate. It is not a 5 because the empty 'Available SDK Clients' section is an organization gap, and the unlisted SDK surface arguably belongs in a referenced file or a pointer to the generated crate.

4 / 5

Total

15

/

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 states a clear, narrowly-scoped capability but is incomplete as a skill trigger: it answers 'what' well yet never says when the skill should be used. Trigger-term coverage is adequate but thin on natural user phrasing. Distinctiveness is strong mainly by virtue of the unique CLI name.

Suggestions

Add an explicit trigger clause, e.g. 'Use when adding or modifying commands in the server-url-templating-api-single-base-url CLI, or when the user asks to extend the CLI with custom commands.'

Include natural trigger variations users would actually say ('add a command', 'extend the CLI', 'custom subcommand') alongside the technical terms.

Briefly enumerate the concrete actions the skill covers (registering commands, wiring the SDK client, preserving code across regeneration) to lift specificity beyond a single action.

DimensionReasoningScore

Specificity

The description names the domain ('custom commands for the server-url-templating-api-single-base-url CLI') and one concrete action ('author... using the co-generated SDK'), but offers no further actions or scope, matching the '1-2 concrete actions, not comprehensive' anchor. It is above a 2 because the action is concrete rather than generic, and below a 4 because only a single action is listed.

3 / 5

Completeness

The 'what' is clear (authoring custom commands for this CLI via the SDK), but there is no 'Use when...' clause or any equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

'custom commands', 'CLI', and 'SDK' are relevant keywords a user might say, but natural variations ('add a command', 'extend the CLI') are absent and 'co-generated SDK' leans technical. This lands on the 'some relevant keywords but missing common variations or synonyms' anchor rather than 4's 'good coverage'.

3 / 5

Distinctiveness Conflict Risk

The highly specific project name carves out a clear niche with low conflict risk, but the description has no distinct trigger phrasing, and sibling skills for other generated CLIs would read identically apart from the name — minor overlap risk with closely related skills. Not a 5 because distinctiveness rests solely on the project name, not on distinct triggers.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fern-api/fern

Path

seed/cli/server-url-templating-single-url/.agents/skills/custom-commands/SKILL.md

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.