CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

server-url-templating-api-custom-commands

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

Quality

73%

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/.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 an efficient, well-structured, single-purpose guide with copy-adaptable code, an accurate regeneration-safety table, and concrete build/test commands. Its main defect is the placeholder 'Available SDK Clients' section that promises a list it never delivers, plus mild redundancy around .fernignore.

Suggestions

Fill in or remove the '### 2. Available SDK Clients' section — either list the actual sub-clients (even a few common ones like client.resource, client.auth) or replace it with a one-line pointer on how to discover them in the generated SDK.

Consolidate the .fernignore explanation (currently stated in the Architecture block, step 1, and the Regeneration Safety table) into one location.

Add a quick verification step after editing custom.rs (e.g. 'cargo check' before the full build) to strengthen the workflow's feedback loop.

DimensionReasoningScore

Conciseness

Sections are lean and every one serves the task (architecture map, registration code, regen-safety table, build commands); only minor trimming needed, e.g. '.fernignore' protection is stated in three places and the Overview slightly repeats the Architecture block.

4 / 5

Actionability

The Rust registration snippet, key-pattern snippets, and exact build/run commands are concrete and adaptable. Minor gap: '### 2. Available SDK Clients' promises 'the following sub-clients:' then lists none — a dangling placeholder that delivers no guidance.

4 / 5

Workflow Clarity

The edit → register → cargo build → run sequence is clear, with a debugging checkpoint (RUST_LOG=debug) and explicit regeneration-safety guidance. Not a destructive/batch operation, so no validation cap applies; the hollow step 2 is the only sequence flaw.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed at this size: the body is self-contained, clearly sectioned, and easy to navigate. The empty sub-clients section is the only structural blemish keeping it from a clean 5.

4 / 5

Total

16

/

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 clear, honest, and highly distinctive thanks to the specific CLI name, but it reads as a title rather than a trigger: it answers 'what' well while completely missing 'when'. Adding an explicit use-when clause with natural trigger phrases would lift completeness and trigger-term quality substantially.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks to add, edit, or register custom commands in the server-url-templating-api CLI.'

Include natural trigger variations such as 'add a command', 'extend the CLI', or 'custom subcommand' alongside 'custom commands'.

Optionally enumerate 1-2 more concrete capabilities (e.g. 'register commands in custom.rs, wire them to the generated SDK client, and survive fern regeneration') to strengthen specificity.

DimensionReasoningScore

Specificity

Names the domain ('server-url-templating-api CLI', 'co-generated SDK') and 1-2 concrete actions ('author custom commands', 'using the co-generated SDK'), but coverage is not comprehensive — no mention of registration, regeneration safety, or build steps.

3 / 5

Completeness

It clearly answers 'what' (authoring custom commands using the co-generated SDK) but has no 'when' clause or equivalent trigger guidance, which the rubric caps at 3.

3 / 5

Trigger Term Quality

'custom commands', 'CLI', and 'SDK' are terms a user might naturally say, but common variations ('add a command', 'extend the CLI', 'new subcommand') and any use-when phrasing are missing.

3 / 5

Distinctiveness Conflict Risk

The hyper-specific project name ('server-url-templating-api CLI') carves out a clear niche with minimal conflict risk — virtually no other skill would trigger for this request.

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

Path

seed/cli/server-url-templating/.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.