CtrlK
BlogDocsLog inGet started
Tessl Logo

inline-enum-type-name-override-custom-commands

How to author custom commands for the inline-enum-type-name-override 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/inline-enum-type-name-override/.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 body is a focused, actionable guide with executable Rust examples, a clear add-command workflow, and clean section organization. Its main weakness is mild redundancy between the Architecture listing and the Regeneration Safety table, plus re-shown code snippets in Key Patterns.

Suggestions

Merge the Architecture file listing and the Regeneration Safety table — both enumerate the same five files with overlapping descriptions; consolidate into one place to remove the redundancy.

In 'Key Patterns', avoid re-displaying the `client(ctx)` and `block_on(...)` calls already shown in the worked example; reference that example or trim to only the novel patterns.

DimensionReasoningScore

Conciseness

The body is largely lean and free of filler, but the Architecture code block and the Regeneration Safety table describe the same five files with overlapping one-line descriptions, and the Key Patterns section re-shows the `client(ctx)`/`block_on(...)` snippets already present in the worked example — it could be tightened.

2 / 3

Actionability

It provides a complete, copy-paste-ready `register()` Rust example using a real SDK method (`client.reporting.load()`), concrete build/run commands, a typed sub-client table, and executable pattern snippets — fully actionable guidance.

3 / 3

Workflow Clarity

The add-command flow is sequenced (edit custom.rs → register → `cargo build` → run the command), and the Build & Test section provides a verification loop including `RUST_LOG=debug` for error recovery; for this simple, non-destructive task the workflow is unambiguous.

3 / 3

Progressive Disclosure

The content is self-contained with no bundle files and no nested references, organized into clearly headed sections (Overview, Architecture, Adding a Custom Command, Regeneration Safety, Build & Test) that make navigation easy; no external split is warranted.

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 specific to a distinct niche but reads as a terse technical caption rather than a discoverable trigger: it states what the skill does without listing multiple concrete actions or any "Use when" guidance. Adding explicit trigger language and natural user phrasing would lift it across the board.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when extending the inline-enum-type-name-override CLI with new subcommands') to raise completeness above its current cap of 2.

Replace jargon like 'co-generated SDK' with natural terms a user would say ('add a custom command', 'write a new CLI subcommand', 'extend the CLI') to improve trigger term quality.

List concrete actions beyond the single verb 'author' (e.g., 'register commands, call the typed SDK, run async calls from sync handlers') to move specificity from domain-naming to multiple concrete actions.

DimensionReasoningScore

Specificity

It names a concrete domain ("custom commands for the inline-enum-type-name-override CLI") and one action ("author... using the co-generated SDK"), but only a single verb is given rather than a list of concrete actions, matching the anchor that names a domain and some actions but is not comprehensive.

2 / 3

Completeness

It clearly states what the skill does (author custom commands for the CLI via the SDK) but provides no "Use when..." clause or equivalent explicit trigger for when to use it, so the "when" is only implied and completeness is capped at 2 per the guidelines.

2 / 3

Trigger Term Quality

Terms like "custom commands", "CLI", and "SDK" are relevant, but the phrasing is jargon-heavy ("co-generated SDK", "inline-enum-type-name-override") and a user would be unlikely to naturally say this verbatim when reaching for the skill; common variations are missing.

2 / 3

Distinctiveness Conflict Risk

The highly specific tool name "inline-enum-type-name-override" carves out a clear niche, making it very unlikely to trigger for the wrong skill.

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.