CtrlK
BlogDocsLog inGet started
Tessl Logo

reserved-keyword-cli-custom-commands

How to author custom commands for the reserved-keyword-cli CLI using the co-generated SDK.

62

Quality

72%

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/cli-reserved-keywords/with-wire-tests/.agents/skills/custom-commands/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The body is lean, executable, and well-organized, with copy-paste Rust examples and a useful regeneration-safety table. Its main gap is the build-and-test workflow, which lacks an explicit validation checkpoint and error-recovery feedback loop.

Suggestions

Add an explicit validation checkpoint after building, e.g. verify the command appears in `reserved-keyword-cli --help` before running it.

Include an error-recovery feedback loop: if registration fails or the SDK surface changed, show how to update `custom.rs` to match and rebuild.

Add a verification gate such as `cargo test` or a smoke-test invocation as the final step before considering the command ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what a CLI, cargo, clap, or TLS is, and sections like Architecture and Regeneration Safety each earn their place without padding, matching the lean/efficient anchor.

3 / 3

Actionability

It provides a complete, executable `register()` Rust example, specific `cargo build` and `reserved-keyword-cli get <model_id>` commands, and a typed SDK-client table, which is copy-paste ready per the fully-executable anchor.

3 / 3

Workflow Clarity

Steps are sequenced (### 1–3 followed by build and test), but there is no explicit validation checkpoint or error-recovery feedback loop (e.g. what to do if the build fails or the SDK surface changed), fitting the anchor for steps listed with validation gaps.

2 / 3

Progressive Disclosure

The skill is self-contained with no bundle files, and content is split into well-organized, clearly signaled sections (Overview, Architecture, Adding a Custom Command, Regeneration Safety, Build & Test) with no nested references, matching the well-organized anchor for a focused skill that needs no 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 names a specific domain and concrete action and is highly distinctive due to the unique CLI name, but it lacks an explicit "Use when" trigger clause and only describes a single action, capping completeness and specificity. Adding trigger guidance and a broader action list would raise it.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when extending reserved-keyword-cli with user-authored commands or wiring custom subcommands into the generated SDK."

List multiple concrete actions to lift specificity, e.g. "register, build, and test custom commands" rather than only "author".

Include more natural trigger variations such as "custom CLI commands" or "extending reserved-keyword-cli".

DimensionReasoningScore

Specificity

Names a concrete action and domain ("author custom commands for the reserved-keyword-cli CLI using the co-generated SDK") but lists only a single action rather than multiple specific concrete actions, matching the anchor that names a domain and some actions but is not comprehensive.

2 / 3

Completeness

It states what the skill does (author custom commands) but provides no "Use when..." clause or equivalent explicit trigger for when to use it; per the guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

"reserved-keyword-cli" and "custom commands" are natural terms a user of this tool would say, but coverage of common variations is limited, fitting the anchor for some relevant keywords missing common variations.

2 / 3

Distinctiveness Conflict Risk

The highly specific "reserved-keyword-cli" tool name carves out a clear niche with a distinct trigger, making it unlikely to fire 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.