server-url-templating-api-custom-commands

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

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./seed/cli/server-url-templating/.agents/skills/custom-commands/SKILL.md

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 content is efficient, actionable, and well-structured for a single-purpose code-authoring skill, with executable examples and a regeneration-safety table. The main weakness is the empty 'Available SDK Clients' section that promises detail it does not deliver.

Suggestions

Fill or remove the 'Available SDK Clients' section — either list the actual sub-clients or point to where they can be discovered at generation time.

Promote the Build & Test steps into an explicit inline validation checkpoint (e.g. 'After editing, run `cargo build` to confirm it compiles before running `fern generate`').

Trim the 'Key Patterns' block since client(ctx) and block_on() are already shown in the register() example, to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Rust/clap competence with no padding about basic concepts, though the 'Key Patterns' section re-shows client(ctx)/block_on() already demonstrated in the register example.	4 / 5
Actionability	Provides copy-paste-ready Rust wiring and concrete build/test commands, but the 'Available SDK Clients' section promises sub-clients without listing any and some identifiers are placeholders.	4 / 5
Workflow Clarity	A clear numbered sequence (steps 1-3) is backed by a Build & Test verification section, though checkpoints live in a separate section rather than inline as explicit validate-then-proceed gates.	4 / 5
Progressive Disclosure	Single-purpose skill with no bundle files and well-organized sections that are easy to navigate, but it exceeds 50 lines and the empty 'Available SDK Clients' stub is a minor organization gap.	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 identifies a narrow niche and the core action, but it omits any 'when to use' trigger guidance and offers only modest keyword coverage. Adding a 'Use when...' clause with natural trigger terms would lift the completeness and trigger_term_quality dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when extending the server-url-templating-api CLI with custom commands or when the user asks to add new CLI subcommands.'

Broaden trigger terms with natural synonyms a user might say (e.g. 'add a CLI command', 'extend the CLI', 'custom subcommand') rather than only 'custom commands' and 'SDK'.

List one or two more concrete actions (e.g. 'register commands, call the typed SDK, print JSON output') to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('server-url-templating-api CLI') and a concrete action ('author custom commands') plus the means ('co-generated SDK'), but lists only one or two actions rather than comprehensive coverage.	3 / 5
Completeness	The 'what' is clear (author custom commands for the CLI using the SDK) but there is no 'Use when...' or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant keywords ('custom commands', 'CLI', 'SDK') but misses natural variations and synonyms a user would actually say, so coverage is partial rather than good.	3 / 5
Distinctiveness Conflict Risk	Naming a specific CLI tool gives it a clear niche with minimal conflict risk, but the absence of explicit trigger phrasing leaves minor overlap risk compared to the anchor 5 example.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 8267efd

Reviewed: about 21 hours ago

Table of Contents

Discovery Implementation Validation

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.