CtrlK
BlogDocsLog inGet started
Tessl Logo

query-param-name-conflict-api-custom-commands

How to author custom commands for the query-param-name-conflict-api 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/query-param-name-conflict/.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 content is concise, well-structured, and provides executable Rust examples with a clear edit-build-run workflow; its main weakness is the empty "Available SDK Clients" section that withholds a concrete sub-client list.

Suggestions

Fill in "Available SDK Clients" with the actual sub-client names (or an explicit pointer to where they are generated), so users can write SDK calls without guessing the surface.

Add a one-line note that custom.rs changes require a rebuild before the new command appears, tying the edit and build steps together explicitly.

DimensionReasoningScore

Conciseness

The body is lean: it skips explaining what a CLI/SDK is and goes straight to file layout, executable Rust snippets, a regeneration-safety table, and build commands — every section earns its tokens.

3 / 3

Actionability

The register() example, client()/block_on() patterns, and cargo build commands are executable and copy-paste ready, but the "Available SDK Clients" section promises sub-clients and delivers none — a missing key detail needed to actually call the SDK.

2 / 3

Workflow Clarity

The flow is clearly sequenced (edit custom.rs → use SDK patterns → rebuild/test), with `cargo build` and running the command serving as the validation checkpoint for this non-destructive code task.

3 / 3

Progressive Disclosure

This single-purpose, well-sectioned SKILL.md (Overview, Architecture, Adding a Command, Regeneration Safety, Build & Test) needs no external bundle files and is organized for easy navigation.

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 and states its purpose clearly, but it lacks an explicit "Use when..." trigger clause and multiple concrete action verbs, leaving both completeness and specificity at the mid-level.

Suggestions

Add an explicit trigger clause, e.g. "Use when extending the query-param-name-conflict-api CLI with custom commands or wiring into the co-generated SDK."

List a couple more concrete actions (e.g. "register commands, wire the authenticated SDK client, run async calls from sync handlers") to lift specificity to a 3.

DimensionReasoningScore

Specificity

"How to author custom commands for the query-param-name-conflict-api CLI using the co-generated SDK" names the domain and a concrete action (authoring custom commands via the SDK), but lists only one action rather than multiple specific concrete operations.

2 / 3

Completeness

It states what the skill does (authoring custom commands), but provides no "Use when..." trigger guidance, so the "when" is only implied — capping completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

It surfaces relevant terms ("custom commands", "CLI", "SDK", "co-generated") but leans on project-specific jargon ("query-param-name-conflict-api") and omits common natural variations a user might say.

2 / 3

Distinctiveness Conflict Risk

The highly specific project name "query-param-name-conflict-api" carves out a clear niche, making accidental triggering of the wrong skill unlikely.

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.