path-param-body-collision-custom-commands

How to author custom commands for the path-param-body-collision 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/openapi-path-param-body-collision/.agents/skills/custom-commands/SKILL.md

Quality

Content

72%

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

The content is concise and well-structured with executable code, but the hollow 'Available SDK Clients' section and absent validation checkpoints hold back actionability and workflow clarity. Filling the SDK client list and adding an explicit build/run verification step would raise the score.

Suggestions

Populate the 'Available SDK Clients' section with the actual sub-clients and representative method names (or link to generated SDK docs) so handlers are copy-paste ready.

Add an explicit validation checkpoint in the workflow, e.g. after editing run `cargo build` and only proceed to run the command once it compiles.

Clarify how to discover the real SDK method names after `fern generate` (e.g. a command to list generated sub-clients) so users are not left guessing the surface.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Rust/CLI competence, and avoids explaining basic concepts; code, the architecture block, and the regeneration table each earn their place without padding.	3 / 3
Actionability	The register() example and key-pattern snippets are executable, but the 'Available SDK Clients' section is an empty placeholder ('Sub-clients are derived from the API spec at generation time.') leaving the actual SDK surface unspecified, matching 'Some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	Steps (edit custom.rs, regeneration safety, build, run) are sequenced, but there is no explicit validation checkpoint or feedback loop and the SDK-clients step is a gap, fitting 'Steps listed but validation gaps; checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	With no bundle files present, the body is self-contained and well-organized into clear sections (Overview, Architecture, Adding a Custom Command, Regeneration Safety, Build & Test), which per the scoring notes earns a 3 for skills needing no external references.	3 / 3
	Total	10 / 12 Passed

Description

57%

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 narrow, low-conflict niche but lacks an explicit usage trigger and only names a single action. Adding a 'Use when...' clause and enumerating concrete capabilities would lift the weaker dimensions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when extending the path-param-body-collision CLI with custom commands or when the user mentions adding CLI commands.'

Enumerate concrete capabilities beyond a single action, such as 'register commands, call typed SDK methods, and preserve code across regeneration'.

Include a few natural user-spoken trigger terms (e.g. 'add a CLI command', 'extend the CLI', 'custom SDK commands') alongside the technical jargon.

Dimension	Reasoning	Score
Specificity	Names a concrete domain ('author custom commands') and the SDK mechanism, but lists only one action rather than multiple specific capabilities, matching the 'Names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It answers 'what' (authoring custom commands via the SDK) but provides no 'Use when...' trigger, so per the guideline a missing explicit-when clause caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'custom commands', 'CLI', and 'co-generated SDK' are relevant but lean toward technical jargon and lack common user-spoken variations, fitting 'Some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The highly specific 'path-param-body-collision CLI' niche makes it unlikely to trigger for any other skill, matching the 'Clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 3
	Total	9 / 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/openapi-path-param-body-collision/.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.