api-wide-base-path-with-default-custom-commands

How to author custom commands for the api-wide-base-path-with-default 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

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./seed/cli/api-wide-base-path-with-default/.agents/skills/custom-commands/SKILL.md

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, actionable reference: complete executable Rust, concrete build/test commands, and well-organized sections with no fluff or nested references. The only gap is the absence of an explicit build/validate feedback loop in the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean with purposeful code, tables, and a file-layout diagram, and assumes Claude's competence without explaining what a CLI or Rust is; the 'Key Patterns' restatement serves as quick-reference rather than padding.	3 / 3
Actionability	It provides a complete executable register() function, concrete cargo build / CLI invocations, and a typed SDK client table — copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	The edit → build → run sequence is present, but the numbered 'steps' mix reference material with workflow and there is no explicit validation or error-recovery checkpoint, matching the middle anchor.	2 / 3
Progressive Disclosure	With no bundle files, the single SKILL.md is well-organized into clearly navigable sections (Overview, Architecture, Adding a Custom Command, Regeneration Safety, Build & Test) with no nested-reference problem.	3 / 3
	Total	11 / 12 Passed

Description

50%

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 states what the skill covers and targets a distinct, uniquely-named CLI, but it is missing explicit 'when to use' trigger guidance and leans on technical jargon ('co-generated SDK') over natural user phrasing. All dimensions land at the middle anchor as a result.

Suggestions

Add an explicit trigger clause such as 'Use when extending or adding commands to the api-wide-base-path-with-default CLI' to lift completeness and distinctiveness.

Replace jargon like 'co-generated SDK' with natural phrasing (e.g. 'typed SDK') and add common verbs users would say ('add', 'register', 'extend').

List a couple of concrete capabilities (e.g. 'register commands, call typed SDK methods, preserve custom code across regeneration') to move specificity toward multiple concrete actions.

Dimension	Reasoning	Score
Specificity	Quotes 'author custom commands for the api-wide-base-path-with-default CLI using the co-generated SDK' name a concrete domain and mechanism in third person, but describe a single action rather than the multiple concrete actions the top anchor requires.	2 / 3
Completeness	The 'what' is explicit but there is no 'Use when...' or equivalent trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	'custom commands' and 'CLI' are relevant keywords a user might say, but 'co-generated SDK' is jargon and common natural variations (e.g. 'add', 'extend') are missing, matching the middle anchor.	2 / 3
Distinctiveness Conflict Risk	The uniquely-named CLI pins a fairly distinct niche, but without explicit trigger guidance it only reaches the 'somewhat specific' anchor rather than the top anchor whose examples include explicit 'Use when...' triggers.	2 / 3
	Total	8 / 12 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/api-wide-base-path-with-default/.agents/skills/custom-commands/SKILL.md
Commit: 134b13f

Reviewed: 2 days 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.