CtrlK
BlogDocsLog inGet started
Tessl Logo

plant-store-custom-commands

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

56

Quality

64%

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/oauth-client-credentials-openapi/with-wire-tests/.agents/skills/custom-commands/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 is well-structured, concise, and actionable with concrete Rust examples and a clear edit-build-test workflow. The main gaps are minor redundancy between the two file tables and a placeholder in the patterns section.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explanation of cargo, clap, or what a CLI is), but the Architecture code block and Regeneration Safety table describe overlapping file information, a minor redundancy that keeps it just below a 5.

4 / 5

Actionability

Concrete, copy-paste-ready Rust code for register(), explicit build/test commands, and an SDK client table provide mostly executable guidance; the placeholder `some_resource.some_method(args)` in Key Patterns is the minor gap preventing a 5.

4 / 5

Workflow Clarity

"Adding a Custom Command" gives a clear numbered sequence (edit custom.rs, build, test) where `cargo build` acts as a compile-time checkpoint, but there is no explicit guidance on handling build or runtime failures, leaving a minor validation gap.

4 / 5

Progressive Disclosure

The skill has no bundle files but is well-organized into clear sections (Overview, Architecture, Adding a Custom Command, Regeneration Safety, Build & Test); it exceeds 50 lines so the simple-skill exception does not fully apply, leaving minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

53%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 tied to a distinct niche, but it omits any explicit "Use when" trigger guidance, which caps completeness and limits trigger term quality. Adding a usage-trigger clause would meaningfully raise the score.

Suggestions

Append a "Use when..." clause naming the natural trigger phrases (e.g., "Use when adding or modifying plant-store CLI commands, or when wiring custom command handlers to the generated SDK").

Include common synonym phrasings users might say (e.g., "plant-store CLI plugins", "custom SDK commands") to broaden trigger term coverage.

Optionally list a second concrete action beyond "author" (e.g., "register, build, and test") to improve specificity.

DimensionReasoningScore

Specificity

"author custom commands for the plant-store CLI" names the domain and one concrete action (authoring) with SDK context, but offers no broader action coverage, matching the anchor for naming domain and 1-2 concrete actions without being comprehensive.

3 / 5

Completeness

The description gives a clear "what" (authoring custom commands for the plant-store CLI) but has no "Use when..." clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Terms like "custom commands", "plant-store CLI", and "co-generated SDK" are relevant to this niche but lack common variations or synonyms a user might naturally say, fitting the anchor for some relevant keywords missing variations.

3 / 5

Distinctiveness Conflict Risk

Tying the skill to the specific "plant-store CLI" gives it a clear, distinct niche with minimal conflict risk, though the brief trigger phrasing leaves minor overlap risk with closely related CLI-authoring skills.

4 / 5

Total

13

/

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.