CtrlK
BlogDocsLog inGet started
Tessl Logo

server-sent-events-openapi-custom-commands

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

58

Quality

66%

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/server-sent-events-openapi/.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 content is lean, actionable, and well-structured, with executable Rust examples and a clear regeneration-safety table. The main weaknesses are a placeholder 'Available SDK Clients' section that lists no actual clients and the absence of an explicit build-failure feedback loop.

Suggestions

Fill in section 2 'Available SDK Clients' with the actual sub-client names (e.g. resource, events, auth) or link to the generated SDK crate, rather than leaving a placeholder.

Add an explicit validation/feedback step in Build & Test, e.g. 'If cargo build fails, check that custom.rs matches the regenerated SDK surface in sdk.rs'.

Tighten the overlap between the Architecture code block and the Regeneration Safety table by cross-referencing instead of restating the file list.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, with lean code, a compact architecture diagram, and a regeneration table; minor trimmable padding (the parenthetical in section 2 and slight overlap between Architecture and the Regeneration Safety table) keep it just below a 5.

4 / 5

Actionability

It provides copy-paste-ready Rust for registering a command, calling the SDK client, block_on, typed models, and concrete build/debug commands; the gap is section 2 promising sub-clients without listing them, which is a minor missing detail.

4 / 5

Workflow Clarity

The 'Adding a Custom Command' section is a clear numbered sequence (1-3) followed by a Build & Test verification step (cargo build, run the command, RUST_LOG=debug); it lacks an explicit validate-then-fix feedback loop, so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

The body is well-organized into clear sections (Overview, Architecture, Adding a Custom Command, Regeneration Safety, Build & Test) with no nested references and no external bundles needed; the placeholder section 2 ('Available SDK Clients' with no list) is a minor organization gap that prevents a 5.

4 / 5

Total

16

/

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 distinct, naming a clear niche and concrete action, but it omits any explicit 'when to use' trigger guidance, which caps completeness. Adding a 'Use when...' clause would raise the completeness and trigger_term_quality scores.

Suggestions

Add an explicit trigger clause, e.g. 'Use when adding or modifying custom commands for the server-sent-events-openapi CLI'.

Include natural user-facing synonyms such as 'SSE CLI', 'add a command', or 'extend the CLI' alongside the technical proper-noun terms.

Optionally list a second concrete action (e.g. 'register, wire up, and call SDK methods') to broaden specificity beyond a single action.

DimensionReasoningScore

Specificity

The description names the domain ('custom commands for the server-sent-events-openapi CLI') and a concrete action ('author custom commands ... using the co-generated SDK'), but lists only one main action rather than several, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

It gives a clear 'what' (author custom commands using the co-generated SDK) but has no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

It includes relevant keywords like 'custom commands', 'CLI', and 'SDK', but these are technical/proper-noun terms and it lacks the natural phrasings or synonyms a user would say, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Tied to a specific named CLI and a narrow task (custom commands via the co-generated SDK), giving it a clear niche with distinct triggers and minimal conflict risk with other skills.

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.