x-fern-default-test-custom-commands

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

Quality

66%

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/x-fern-default/.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 a tight, actionable guide with executable code and a clear regeneration-safety table. It could be improved with explicit build/run validation checkpoints and slightly tighter prose.

Suggestions

Add an explicit validation/feedback step after `cargo build` (e.g. 'If the build fails on a renamed SDK method, update the call in custom.rs and rebuild') to strengthen workflow_clarity.

Trim the one-line parenthetical about sub-clients or replace it with the actual sub-client list, since the section currently promises sub-clients it does not enumerate.

Consider pulling the regeneration-safety table into a short reference file once the skill grows, to keep SKILL.md as a focused overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no boilerplate about Rust or CLIs); only minor stretches like the parenthetical 'Sub-clients are derived from the API spec at generation time' could be trimmed, fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	Provides copy-paste-ready Rust code plus concrete `cargo build` / `RUST_LOG=debug` commands covering the common cases, with only minor illustrative gaps (e.g. `client.resource.get(id)`), matching 'mostly executable; concrete code with minor gaps'.	4 / 5
Workflow Clarity	Steps are clearly sequenced (edit custom.rs → register → build → run) with a regeneration-safety table; not a destructive/batch operation so the 3-cap does not apply, but build/run validation and error-recovery checkpoints are only implicit, keeping it at 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inline in a single, well-organized SKILL.md with clear sections and a summary table; good structure with only minor organization gaps, fitting the 4 anchor rather than 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 specific to a niche and clearly distinguishable, but it states only the 'what' and omits any 'when to use' trigger guidance. Adding a 'Use when...' clause would raise completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause naming the natural triggers (e.g. 'Use when adding or editing custom commands for the x-fern-default-test CLI').

Add user-natural synonyms beyond technical jargon — e.g. 'add a CLI command', 'extend the CLI' — so it matches how users phrase the request.

Optionally list the concrete actions covered (register a command, call the SDK client, handle async) to move specificity toward 4-5.

Dimension	Reasoning	Score
Specificity	Names the domain ('author custom commands for the x-fern-default-test CLI') and a concrete mechanism ('co-generated SDK'), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor rather than the more action-rich 4.	3 / 5
Completeness	Gives a clear 'what' (authoring custom commands via the co-generated SDK) but has no 'Use when...' or equivalent trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant terms ('custom commands', 'CLI', 'SDK') but leans technical; it lacks the natural phrases a user would say and common synonyms, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The product-specific 'x-fern-default-test' niche plus 'co-generated SDK' give it a clear, distinct trigger with minimal overlap risk against other skills.	5 / 5
	Total	14 / 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/x-fern-default/.agents/skills/custom-commands/SKILL.md
Commit: 8267efd

Reviewed: about 22 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.