nullable-allof-extends-test-custom-commands

How to author custom commands for the nullable-allof-extends-test 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/nullable-allof-extends/.agents/skills/custom-commands/SKILL.md

Quality

Content

78%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 a concise, well-structured, and actionable guide with executable code and a helpful regeneration-safety table; its main weaknesses are an empty 'Available SDK Clients' section and the absence of an explicit verification step in the workflow.

Suggestions

Fill in or remove the 'Available SDK Clients' stub — list the actual sub-clients or point to where they can be discovered at generation time.

Add an explicit verification step to the workflow, e.g. 'Run `nullable-allof-extends-test my-command --help` to confirm registration before invoking it.'

Replace the placeholder 'some_resource.some_method(args)' with a concrete representative SDK call so the example is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence without explaining what a CLI or SDK is, with tight code examples; the near-empty 'Available SDK Clients' stub is a minor inefficiency rather than verbosity, landing just below the lean-everything-earns-its-place anchor.	4 / 5
Actionability	Provides mostly executable Rust code (register pattern, client(ctx), block_on, typed imports) and concrete build/test commands, but the empty sub-client list and the placeholder 'some_resource.some_method(args)' leave minor gaps that keep it below fully copy-paste-ready.	4 / 5
Workflow Clarity	The numbered add-command workflow and the regeneration-safety table give a clear sequence, but there is no explicit verification checkpoint (e.g. confirming the command registered or testing output), which is a minor validation gap rather than a wholesale absence.	4 / 5
Progressive Disclosure	No bundle files are needed or present, and the content is well-organized into clearly labeled sections (Overview, Architecture, Adding a Custom Command, Regeneration Safety, Build & Test) with easy navigation, satisfying the simple-skill exception for well-organized single-file skills.	5 / 5
	Total	17 / 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 clearly states what the skill does and is well-scoped to a distinct named CLI, but it lacks an explicit 'Use when...' trigger clause and only lightly enumerates capabilities, which caps completeness and trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to add, modify, or debug custom commands for the nullable-allof-extends-test CLI.'

List a couple more concrete actions (e.g. 'register clap subcommands, call typed SDK methods, share the CLI auth/TLS context') to lift specificity toward a 4-5.

Include natural synonyms a user might say (e.g. 'CLI plugins', 'custom subcommands', 'extend the CLI') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (custom commands for the CLI) and 1-2 concrete actions (author custom commands, use the co-generated SDK), but does not enumerate multiple specific actions, matching the anchor for 'Names domain and 1-2 concrete actions, but not comprehensive'.	3 / 5
Completeness	Provides a clear 'what' (authoring custom commands using the co-generated SDK) but has no 'Use when...' trigger clause; per the judging guidelines, a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant keywords ('custom commands', 'CLI', 'SDK') but is a narrow technical domain missing common variations or synonyms a user might naturally say, matching the 'Some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named CLI ('nullable-allof-extends-test'), giving it a clear niche with distinct triggers and minimal conflict risk with 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/nullable-allof-extends/.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.