CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webhook-audience-test-custom-commands

How to author custom commands for the webhook-audience-test CLI using the co-generated SDK.

Quality

73%

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/webhook-audience/.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 a lean, well-organized single-file skill with executable Rust and shell examples, a clear edit→build→run sequence, and valuable regeneration-safety guidance that anticipates a real failure mode. Its main weaknesses are a content-free "Available SDK Clients" section and a "Key Patterns" section that duplicates the main example. Filling in or removing the stub section would push it toward top marks.

DimensionReasoningScore

Conciseness

The body is tight — no explanations of known concepts (clap, cargo, async), a compact ASCII architecture tree, and a focused regeneration table. Minor trimmable content exists: the "Key Patterns" section re-repeats three snippets already shown verbatim in the registration example, and the "Available SDK Clients" section promises a list but delivers only "(Sub-clients are derived from the API spec at generation time.)". This is 'Efficient; minor instances... that could be trimmed', not 3, since the redundancy is structural rather than padded prose.

4 / 5

Actionability

Concrete, near copy-paste Rust registration code ("pub fn register(app: CliApp) -> CliApp { ... }") and executable build/run commands ("cargo build", "RUST_LOG=debug webhook-audience-test <your-command>") are provided. It falls short of 5 because the example uses a placeholder sub-client ("client.resource.get(id)") and the actual SDK surface is never documented, leaving the reader to discover real method names.

4 / 5

Workflow Clarity

The sequence is clear and ordered: edit custom.rs → register the command → cargo build → run the command, and the "Regeneration Safety" section anticipates a failure mode with remediation ("If the SDK surface changes... update your custom.rs to match"). Minor validation gaps (no step to verify the command appears in --help or a test invocation) keep it at 'most checkpoints present' rather than 5's explicit validation steps.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the single-file body is well-sectioned with clear headers and a one-level, non-nested structure that is easy to navigate. The empty "Available SDK Clients" section — a promised list that never materializes — is a minor organization gap that prevents the 'clear overview, content appropriately split' bar of 5, fitting 'Good structure... minor organization gaps'.

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 precise and unambiguous about what the skill covers, and its product-specific naming eliminates conflict risk. However, it entirely lacks a 'when to use' trigger clause and natural trigger variations, leaving it dependent on the user already naming the exact CLI. Adding an explicit 'Use when...' sentence with common phrasings would lift completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g., "Use when adding, modifying, or debugging commands in the webhook-audience-test CLI, or when the user asks to extend the CLI with a custom subcommand."

Include natural synonyms users would say, such as "add a CLI command", "custom subcommand", or file references like "custom.rs" / ".fernignore", to improve trigger term coverage.

Optionally name one more concrete capability (e.g., "registers clap commands with a pre-wired authenticated SDK client") to move specificity beyond a single action.

DimensionReasoningScore

Specificity

The description names a concrete domain and action — "author custom commands for the webhook-audience-test CLI" — plus the mechanism "using the co-generated SDK", but stops at a single action with no elaboration. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than 4, which requires several listed actions.

3 / 5

Completeness

The 'what' is clear ("How to author custom commands for the webhook-audience-test CLI using the co-generated SDK"), but there is no 'when' — no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3. It cannot score 4 because 'when' is not present even implicitly.

3 / 5

Trigger Term Quality

"custom commands" and "CLI" are relevant keywords a user might say, but there are no natural variations or synonyms (e.g., "add a command", "extend the CLI", "custom subcommand", "custom.rs"). This is exactly 'Some relevant keywords but missing common variations or synonyms', not 4's 'a few natural terms missing' since synonyms are entirely absent.

3 / 5

Distinctiveness Conflict Risk

The description is anchored to a uniquely named tool ("webhook-audience-test CLI"), giving it a clear niche with minimal overlap risk against generic skills. It fits 'Clear niche with distinct triggers; minimal conflict risk'; 4 would require identifiable overlap with closely related skills, which the specific product name precludes.

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/webhook-audience/.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.