CtrlK
BlogDocsLog inGet started
Tessl Logo

nullable-allof-extends-test-custom-commands

How to author custom commands for the nullable-allof-extends-test CLI using the co-generated SDK.

61

Quality

71%

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-allof-extends/.agents/skills/custom-commands/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content is actionable and well-structured with executable Rust examples and a useful regeneration-safety table. Its main weakness is the empty 'Available SDK Clients' placeholder section that adds tokens without information.

Suggestions

Fill or remove the 'Available SDK Clients' section — either list the actual sub-clients or drop the placeholder header.

Optionally note where to discover available sub-clients at generation time (e.g., inspect nullable_allof_extends_test_sdk::api) so the section is actionable.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Rust/clap competence, but the 'Available SDK Clients' subsection is a placeholder that promises sub-clients and delivers none, wasting tokens.

2 / 3

Actionability

It provides a complete, copy-paste-ready register() example, concrete key-pattern snippets, and exact build/test commands — fully executable guidance.

3 / 3

Workflow Clarity

For a simple authoring skill the single task is unambiguous and well-organized; no destructive or batch operation is present, so missing validation checkpoints is not penalized.

3 / 3

Progressive Disclosure

The skill is a single well-organized file with clear sections (Architecture, Adding a Command, Regeneration Safety, Build & Test) and no nested external references.

3 / 3

Total

11

/

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 clear about its narrow purpose but lacks an explicit use-trigger clause and lists only a single high-level action. It is distinct thanks to the specific CLI name, yet trigger-term coverage is limited.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when extending the nullable-allof-extends-test CLI with user-authored commands').

Enumerate concrete capabilities (e.g., register commands, call typed SDK methods, run async calls from sync handlers) instead of the single verb 'author'.

Include common user phrasings like 'custom CLI commands' or 'add a command to the CLI' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain ('author custom commands for the nullable-allof-extends-test CLI') and a mechanism ('using the co-generated SDK'), but lists only one broad action rather than multiple concrete capabilities.

2 / 3

Completeness

It states what the skill does (authoring custom commands via the co-generated SDK) but has no 'Use when...' trigger clause, so the 'when' guidance is only implied.

2 / 3

Trigger Term Quality

'custom commands', 'CLI', and 'SDK' are relevant terms a user might say, but coverage is thin and the unusual generated CLI name offers no natural-language variations.

2 / 3

Distinctiveness Conflict Risk

The skill is scoped to one specific named CLI ('nullable-allof-extends-test'), giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

12

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.