CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-x-fern-global-parameters-extension-custom-commands

How to author custom commands for the test-x-fern-global-parameters-extension CLI using the co-generated SDK.

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/x-fern-global-parameters/no-custom-config/.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.

This is a strong, self-contained skill: fully executable Rust code, exact file paths, concrete build/run/debug commands, and a clear edit-register-build-test sequence with regeneration safety explicitly documented. Its only weaknesses are mild — duplicated file listings across the Architecture and Regeneration Safety sections and a thin one-row SDK client table — none of which materially impede execution.

DimensionReasoningScore

Conciseness

The body is efficient: it avoids explaining Rust, clap, or SDK concepts Claude already knows and goes straight to file paths, code, and commands. Minor trimming is possible — the Architecture file listing and the Regeneration Safety table largely duplicate the same five file paths, and 'zero configuration required' reads as marketing padding. This fits 'Efficient; minor instances of over-explanation that could be trimmed'; it is below 5 due to that duplication and above 3 because padding is minimal.

4 / 5

Actionability

The skill provides a complete, copy-paste-ready Rust example with the exact file to edit (custom.rs), the registration signature, typed argument handling, SDK client construction, async bridging via block_on, JSON output, and the exact cargo build and CLI invocation commands with a debugging variant (RUST_LOG=debug). The 'Key Patterns' section generalizes the three operations needed for any command. This matches 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The sequence is clear and numbered: edit custom.rs, register the command, 'Then build and test' with the concrete build and run commands — a validation checkpoint of actually invoking the command with real arguments. It is below 5 because there is no explicit error-recovery guidance for build failures or a changed SDK surface beyond one sentence ('update your custom.rs to match'), and above 3 because the build-then-run checkpoint is explicitly present with runnable commands.

4 / 5

Progressive Disclosure

There are no bundle files (references/, scripts/, assets/ do not exist) and the ~110-line body is self-contained, so nothing needs offloading; sections (Overview, Architecture, Adding a Custom Command, Regeneration Safety, Build & Test) are well-organized and every file path referenced is one of the five real project paths listed. It sits below 5 only because the body exceeds the under-50-lines simple-skill threshold and contains some content (the duplicated file tables) that could be consolidated; it is above 3 because structure is clean with no buried or nested references.

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 highly distinctive and states a concrete 'what', but it entirely lacks a 'when to use' trigger clause and offers no synonyms or natural phrasing variations for discovery. Its narrow, tool-specific scope protects it from conflicts but also limits how easily a user would surface it by natural language.

Suggestions

Add an explicit trigger clause, e.g., 'Use when adding or modifying commands in the test-x-fern-global-parameters-extension CLI, or when the user asks to extend or customize the CLI with new subcommands.'

Briefly enumerate 1-2 concrete capabilities in the description (e.g., 'registers clap commands, wires the authenticated SDK client, and survives fern generate') to strengthen both specificity and trigger-term coverage.

Include natural synonyms such as 'add a command', 'extend the CLI', or 'custom subcommands' so users phrasing the request differently can still match the skill.

DimensionReasoningScore

Specificity

The description names a clear domain ("the test-x-fern-global-parameters-extension CLI") and one concrete action ("author custom commands"), plus the mechanism ("using the co-generated SDK"), but lists no additional capabilities such as what the commands inherit or how they are wired. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; it is above score 2 because the action is concrete rather than generic, and below score 4 because there is only a single action with minor coverage gaps.

3 / 5

Completeness

The 'what' is clearly stated ("author custom commands for the ... CLI using the co-generated SDK"), but there is no 'Use when...' clause or any trigger guidance for when to invoke the skill. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3 ('when' is missing or only weakly implied); it is above 2 because the 'what' is concrete, and below 4 because 'when' is entirely absent.

3 / 5

Trigger Term Quality

Relevant keywords are present — "custom commands", "CLI", "SDK" — which a user working on this CLI would plausibly say, but there are no synonyms or phrasing variations (e.g., "add a command", "extend the CLI", "register a subcommand"). This fits 'Some relevant keywords but missing common variations or synonyms'; not 4 because natural variations are absent, not 2 because the terms are domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

The description names one specific CLI (test-x-fern-global-parameters-extension) and a specific task (custom command authoring), creating a clear niche that no other skill would plausibly match. This matches the top anchor 'Clear niche with distinct triggers; minimal conflict risk'; the ultra-specific tool name makes overlap with similar skills nearly impossible.

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/x-fern-global-parameters/no-custom-config/.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.