CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

server-sent-events-openapi-custom-commands

How to author custom commands for the server-sent-events-openapi CLI using the co-generated SDK.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./seed/cli/server-sent-events-openapi/.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 content is a tight, actionable guide with a complete code example, a useful regeneration-safety table, and concrete build commands. Its main weaknesses are an empty 'Available SDK Clients' section that promises a list it never delivers, and validation checkpoints that remain implicit in the build-and-run workflow.

Suggestions

Fill in or remove the 'Available SDK Clients' section — either enumerate the sub-clients or point to where to find them (e.g. 'inspect server-sent-events-openapi-sdk/src/ for the generated API surface') instead of promising 'the following sub-clients:' with nothing following.

Add an explicit validation checkpoint after building, e.g. 'Verify the command registered: server-sent-events-openapi --help', and a note on diagnosing failures (compile errors from a changed SDK surface, auth errors at runtime).

Trim the 'Key Patterns' section, which repeats the client/block_on code already shown in the full registration example.

DimensionReasoningScore

Conciseness

The body is efficient — an architecture map, one complete example, a regeneration-safety table, and build commands with no padding — but the 'Key Patterns' section re-shows code already demonstrated in the full example ('let client = super::sdk::client(ctx);', the block_on snippet), fitting 'Efficient; minor instances of over-explanation that could be trimmed' rather than the lean anchor 5.

4 / 5

Actionability

The registration example is concrete and structured (clap command definition, handler, client wiring, build/run commands), matching 'Mostly executable guidance; concrete code or commands with minor gaps' — but '### 2. Available SDK Clients' promises 'the following sub-clients:' and lists none, and 'client.resource.get(id)' is illustrative rather than a real API surface, which rules out 5.

4 / 5

Workflow Clarity

The sequence (edit custom.rs → register command → cargo build → run) is present and the regeneration note covers SDK-surface drift, but validation checkpoints are only implicit — there is no explicit verify step (e.g. checking the command appears in --help) and no fix/retry loop, matching 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit' rather than anchor 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

No bundle files exist and the ~100-line body is appropriately self-contained with well-organized sections and no nested references, matching 'Good structure; most content is appropriately placed; references mostly clear; minor organization gaps' — the empty 'Available SDK Clients' stub section is the gap that keeps it from 5.

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 highly distinctive thanks to the specific tool name and states its purpose clearly, but it is thin: a single action phrase with no trigger guidance and few natural keywords. Adding a 'Use when...' clause and a couple of natural trigger phrases would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when adding or extending commands in the server-sent-events-openapi CLI, or when the user mentions custom commands or extending the CLI.'

Expand trigger-term coverage with natural synonyms users would say: 'add commands', 'extend the CLI', 'register a command', 'fern generate'.

Briefly enumerate what authoring involves (registering commands in custom.rs, using the SDK client, surviving regeneration) to lift specificity from one action to several.

DimensionReasoningScore

Specificity

"How to author custom commands for the server-sent-events-openapi CLI using the co-generated SDK" names the domain plus one concrete action (authoring custom commands) and its mechanism, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' — it does not list several specific actions (rules out 4) and is more concrete than a generic action-only phrase (rules out 2).

3 / 5

Completeness

The description has a clear 'what' (authoring custom commands for this CLI) but no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

The only natural keywords are "custom commands", "CLI", and "SDK" — relevant but sparse, with common variations ("add commands", "extend the CLI", "register commands") absent, fitting 'Some relevant keywords but missing common variations or synonyms' rather than the good coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

Naming the hyper-specific tool "server-sent-events-openapi CLI" gives a clear niche with distinct triggers and minimal conflict risk — no other skill would plausibly match this description.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fern-api/fern

Path

seed/cli/server-sent-events-openapi/.agents/skills/custom-commands/SKILL.md

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.