CtrlK
BlogDocsLog inGet started
Tessl Logo

plant-store-api-custom-commands

How to author custom commands for the plant-store-api CLI using the co-generated SDK.

56

Quality

63%

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

Quality

Content

68%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 delivers concrete, executable Rust examples and a clear architecture map with strong regeneration-safety guidance, but the "Available SDK Clients" section is an empty stub and the add-command workflow lacks an explicit verification step.

Suggestions

Fill in the "Available SDK Clients" section with the actual sub-clients or a pointer to where they are enumerated in the SDK crate.

Add an explicit verification step to the add-command workflow, e.g. "After registering, run `cargo build` then `plant-store-api my-command <id>` and confirm the expected output."

Trim the marketing prose in the Overview (e.g. "zero configuration required") to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's knowledge of Rust, clap, and serde, with only minor trimmable prose ("zero configuration required", the overview sentence), matching the anchor for efficient content with minor over-explanation.

4 / 5

Actionability

Provides concrete, executable Rust code for registering a command and specific patterns (client(ctx), block_on()), plus build/test commands; the main gap is the "Available SDK Clients" section that promises sub-clients but lists none, fitting the mostly-executable-with-minor-gaps anchor.

4 / 5

Workflow Clarity

The add-command workflow is numbered and sequenced, but it lacks explicit validation or verification checkpoints (no "run your command and confirm output" step before proceeding), matching the anchor with steps present but validation gaps.

3 / 5

Progressive Disclosure

Content is well-organized under clear section headers (Architecture, Adding a Custom Command, Regeneration Safety, Build & Test) with no nested references, matching the good-structure anchor; the stub "Available SDK Clients" section is a minor organization gap.

4 / 5

Total

15

/

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 is specific and clearly distinct, naming the exact CLI and SDK involved, but it omits any explicit "Use when..." trigger guidance, which caps its completeness. Trigger-term coverage is adequate but could include more natural variations.

Suggestions

Add a "Use when..." clause, e.g. "Use when adding or modifying commands for the plant-store-api CLI."

Expand the action list slightly, e.g. "register, wire, and run custom commands".

Include a natural synonym such as "extend the plant-store-api CLI" to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ("plant-store-api CLI", "co-generated SDK") and one concrete action ("author custom commands"), but does not enumerate several specific actions, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Clearly states what the skill does ("author custom commands for the plant-store-api CLI using the co-generated SDK") but provides no "Use when..." trigger guidance, so per the missing-trigger clause completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes relevant keywords ("custom commands", "CLI", "SDK") that a user might naturally say, but lacks common variations or synonyms (e.g. "add a command", "extend the CLI"), fitting the anchor with some relevant keywords but missing variations.

3 / 5

Distinctiveness Conflict Risk

The description targets a clearly distinct niche (custom commands for a specific named CLI, plant-store-api) with minimal overlap risk against other skills, matching the anchor for a clear niche with distinct triggers.

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.