CtrlK
BlogDocsLog inGet started
Tessl Logo

nullable-request-body-custom-commands

How to author custom commands for the nullable-request-body CLI using the co-generated SDK.

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./seed/cli/nullable-request-body/.agents/skills/custom-commands/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

90%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 tight, actionable reference with executable code and strong structure, assuming Claude's competence throughout. The only gap is the absence of an explicit validation checkpoint in the build/test workflow.

DimensionReasoningScore

Conciseness

The body is lean and efficient — tables for clients and regeneration safety, tight code blocks, and no padding or explanation of basic concepts Claude already knows.

5 / 5

Actionability

Copy-paste-ready Rust registration code, concrete build/test commands, and a typed client table give fully executable, specific guidance covering the common case.

5 / 5

Workflow Clarity

A clear sequence (edit custom.rs → register → cargo build → run command) is present, and cargo build acts as implicit validation, but there is no explicit validation checkpoint or error-recovery loop.

4 / 5

Progressive Disclosure

Content is organized into clear, well-signaled sections (Overview, Architecture, Adding a Custom Command, Regeneration Safety, Build & Test) with no nesting; a single overview table of available clients could be split out, but it is appropriately inline.

4 / 5

Total

18

/

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 conveys what the skill does and is highly distinct, but it lacks any 'when to use' trigger guidance and offers only one concrete action with limited keyword variety.

Suggestions

Add an explicit 'Use when...' clause describing the situations that call for this skill (e.g. 'Use when extending the nullable-request-body CLI with user-authored commands').

Broaden trigger keywords to include natural phrasings users might say, such as 'add a command', 'extend the CLI', or 'wire up an SDK call'.

Consider listing one or two additional concrete actions (e.g. registering subcommands, wiring auth/retries) to raise specificity above a single action.

DimensionReasoningScore

Specificity

Names the domain ('author custom commands for the nullable-request-body CLI') and the concrete mechanism ('using the co-generated SDK'), but only covers a single action rather than a comprehensive list.

3 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' or equivalent trigger clause, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Relevant keywords like 'custom commands', 'CLI', and 'SDK' are present, but natural synonyms a user might say (e.g. 'add command', 'extend CLI') are missing.

3 / 5

Distinctiveness Conflict Risk

The description targets an extremely specific niche (a single named CLI and its co-generated SDK), making it highly distinct with minimal conflict risk.

5 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fern-api/fern
Reviewed

Table of Contents

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.