discriminated-union-with-nested-oneof-custom-commands

How to author custom commands for the discriminated-union-with-nested-oneof 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/discriminated-union-with-nested-oneof/.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 body is well-organized, lean, and supplies executable Rust examples plus a useful regeneration-safety table, but it is held back by a placeholder 'Available SDK Clients' section and the absence of explicit validation checkpoints in the workflow.

Suggestions

Fill in or remove the empty 'Available SDK Clients' section so it either lists the sub-clients or links to where they can be discovered at generation time.

Add an explicit verification checkpoint after registration/build (e.g., run the command and confirm it appears in `--help`) to strengthen workflow_clarity.

Consolidate the repeated `super::sdk::client(ctx)`/`block_on` snippets into one canonical example to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's knowledge of Rust/clap without explaining basics, but the placeholder 'Available SDK Clients' section and slight repetition of the client/block_on patterns leave minor trim opportunities, fitting score 4 over 5.	4 / 5
Actionability	It provides concrete, executable Rust code for register(), key patterns, and build/test commands that are copy-paste ready, but the empty 'Available SDK Clients' section leaves a gap in coverage of common cases, keeping it at 4 rather than 5.	4 / 5
Workflow Clarity	The 'Adding a Custom Command' subsections and Build & Test block give a clear sequence with `cargo build` as an implicit compile checkpoint, but there is no explicit verify-the-command-registered step, matching the score-4 anchor with minor validation gaps.	4 / 5
Progressive Disclosure	The content is well-sectioned (Overview, Architecture, Adding a Command, Regeneration Safety, Build & Test) in a single self-contained file with no nested references, but the empty 'Available SDK Clients' section is a minor organization gap preventing a 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 highly distinctive and names its niche precisely, but it states only one concrete action and lacks any explicit 'when to use' trigger guidance, capping both completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should reach for this skill (e.g., 'Use when adding user-authored commands to the ... CLI').

List 1-2 more concrete actions (e.g., 'register commands, wire the authenticated SDK client, run async calls') to raise specificity above 3.

Include natural trigger synonyms a user might actually say beyond 'custom commands', such as 'CLI plugins' or 'user commands'.

Dimension	Reasoning	Score
Specificity	It names the domain ('author custom commands for the discriminated-union-with-nested-oneof CLI') and one concrete action ('using the co-generated SDK'), but lists only a single action rather than several, matching the score-3 anchor rather than 4.	3 / 5
Completeness	It clearly states the 'what' (authoring custom commands with the co-generated SDK) but provides no 'Use when...' or equivalent trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'custom commands', 'CLI', and 'SDK' are relevant keywords a user might say, but the description omits common variations/synonyms and leans on technical jargon, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	The highly specific CLI name ('discriminated-union-with-nested-oneof') carves out a clear niche with distinct triggers and minimal conflict risk, matching the score-5 anchor.	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/discriminated-union-with-nested-oneof/.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.