CtrlK
BlogDocsLog inGet started
Tessl Logo

schemaless-request-body-examples-api-custom-commands

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

54

Quality

60%

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/schemaless-request-body-examples/.agents/skills/custom-commands/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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 content is lean, well-structured, and largely actionable with executable Rust and shell examples, but the "Available SDK Clients" section is underspecified and the command-authoring workflow lacks explicit validation/regeneration-check steps.

Suggestions

Fill in the "Available SDK Clients" section with the actual sub-clients (or remove the empty stub) so it is not a dead reference.

Add a validation step after `fern generate`, e.g. confirm `custom.rs` is unchanged and run `cargo build`/`cargo test` before considering the command done.

Consolidate the Architecture file listing and the Regeneration Safety table to remove redundancy and tighten token use.

DimensionReasoningScore

Conciseness

The body is well-organized with minimal preamble and lean code snippets, though lines like "(Sub-clients are derived from the API spec at generation time.)" and the architecture file list are slightly redundant given the table that follows.

4 / 5

Actionability

Concrete, executable Rust snippets (register(), client(ctx), block_on()) and real build/test commands are provided; the "Available SDK Clients" section is vague (only a parenthetical, no listed sub-clients), leaving a minor gap.

4 / 5

Workflow Clarity

There is a clear "Adding a Custom Command" sequence (edit custom.rs → use SDK patterns → regenerate), but it lacks validation checkpoints (e.g. verify `fern generate` preserves custom.rs, run tests after build) for what is effectively a compile/regeneration workflow.

3 / 5

Progressive Disclosure

No bundle files exist, so structure is judged on the body alone; sections (Overview, Architecture, Adding a Command, Regeneration Safety, Build & Test) are clearly headed and well-organized with content appropriately inline for a skill of this size, though the Regeneration Safety table partly duplicates the Architecture block.

4 / 5

Total

15

/

20

Passed

Description

55%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 (authoring custom commands for a specific CLI via its SDK) and is well-scoped to a distinct niche, but it omits any "Use when..." trigger guidance and relies on technical jargon rather than natural user phrasing.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding user-authored commands to the schemaless-request-body-examples-api CLI."

Include natural-language trigger terms a user might say, such as "add a CLI command" or "extend the CLI", alongside the technical SDK framing.

Optionally name one or two more concrete actions (e.g. "register commands, call the typed SDK, compile into the binary") to broaden coverage.

DimensionReasoningScore

Specificity

"author custom commands" and "using the co-generated SDK" name a concrete domain and specific action (authoring CLI custom commands), though only one primary action is stated rather than a comprehensive list.

4 / 5

Completeness

The "what" is clear (author custom commands for this CLI using the SDK), but there is no "when" clause — the trigger guidance is entirely missing, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

"custom commands", "CLI", and "co-generated SDK" are relevant terms, but the description lacks the natural phrases a user would say (e.g. "add a CLI command") and includes no trigger/"Use when" phrasing or synonyms.

3 / 5

Distinctiveness Conflict Risk

The highly specific skill name "schemaless-request-body-examples-api" and "co-generated SDK" pin it to a narrow niche with minimal overlap risk, though the description itself is moderately generic in wording.

4 / 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.