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

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/discriminated-union-with-nested-oneof/.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 body is concise, code-driven, and well-structured for a focused CLI-extension skill, but it has a hollow 'Available SDK Clients' placeholder and lacks an explicit validation checkpoint in the build/test workflow.

Suggestions

Fill the 'Available SDK Clients' section with the actual generated sub-clients (or point to where they are enumerated in the SDK crate) instead of leaving a parenthetical placeholder.

Replace illustrative names like 'some_resource.some_method' with a real, runnable SDK call drawn from the generated API surface.

Add an explicit verification step after registration, e.g. 'cargo build && discriminated-union-with-nested-oneof my-command --id <id>' with guidance on what to do if it fails to compile or panics.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward with no explanation of concepts Claude already knows (Rust, clap, serde, async, TLS), and its prose (architecture map, regeneration table, build commands) earns its place, matching the level-3 'lean and efficient' anchor.	3 / 3
Actionability	It provides executable, copy-pasteable Rust (register(), client(ctx), block_on()) and real build commands, but the 'Available SDK Clients' section is a placeholder that promises sub-clients and lists none, and key examples use illustrative names like 'some_resource.some_method', so guidance is incomplete per the level-2 anchor.	2 / 3
Workflow Clarity	Steps are sequenced (edit custom.rs, register, build, run) and a regeneration-safety table addresses the regenerate failure mode, but there is no explicit validation/verification checkpoint (only an implicit 'cargo build') and no feedback loop for build/registration failures, matching level-2 'steps listed but validation gaps'.	2 / 3
Progressive Disclosure	No bundle files exist and none are needed; the skill is single-purpose and well-organized into clear sections (Overview, Architecture, numbered Adding a Custom Command, Regeneration Safety, Build & Test), so per the simple-skill note well-organized inline content earns a 3.	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 well-scoped niche and avoids generic fluff, but it omits an explicit 'Use when...' trigger clause and lists only a single action, which leaves it solid rather than exemplary.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when extending the discriminated-union-with-nested-oneof CLI with user-authored commands or wiring SDK calls into custom handlers.'

Enumerate a couple more concrete actions (e.g. 'register clap subcommands, call typed SDK methods, share auth/retries/TLS from the CLI') to lift specificity to multiple concrete actions.

Include a few natural keyword variations users might actually say (e.g. 'custom command', 'CLI plugin', 'SDK handler') alongside the existing terms.

Dimension	Reasoning	Score
Specificity	It names the domain ('custom commands for the discriminated-union-with-nested-oneof CLI') and a concrete action ('author ... using the co-generated SDK'), but lists only one action rather than multiple specific capabilities, so it stops short of the level-3 'multiple concrete actions' anchor.	2 / 3
Completeness	It answers 'what' (author custom commands via co-generated SDK) but provides no 'Use when...' or equivalent trigger clause for 'when', which per the guidelines caps completeness at 2; not level 3 because the when is entirely missing rather than explicit.	2 / 3
Trigger Term Quality	It surfaces relevant terms a user might say ('custom commands', 'CLI', 'SDK'), but offers only these few technical terms with no common variations, matching the level-2 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The narrow reference to the specific 'discriminated-union-with-nested-oneof CLI' and its co-generated SDK carves a clear niche unlikely to trigger for unrelated skills, matching the level-3 'clear niche with distinct triggers' 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/discriminated-union-with-nested-oneof/.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.