CtrlK
BlogDocsLog inGet started
Tessl Logo

multi-content-type-examples-custom-commands

How to author custom commands for the multi-content-type-examples CLI using the co-generated SDK.

57

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/multi-content-type-examples/.agents/skills/custom-commands/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable code and clear organization, and it appropriately avoids external reference nesting; its main weaknesses are mild internal redundancy and implicit rather than explicit validation checkpoints in the workflow.

Suggestions

Collapse the architecture file list and the Regeneration Safety table into a single source of truth to remove the duplicated file listing.

Add an explicit validation/feedback step after `cargo build` (e.g. 'If the build fails, read the error, fix custom.rs, and rebuild before running the command').

Trim the 'Key Patterns' section so `super::sdk::client(ctx)` and `block_on(...)` are not re-shown immediately after the worked example.

DimensionReasoningScore

Conciseness

The body is code-forward and mostly lean, but the architecture code block and the Regeneration Safety table re-list the same files, and 'Key Patterns' repeats the `super::sdk::client(ctx)` call already shown in the example, so it could be tightened rather than earning the every-token-counts anchor at 3.

2 / 3

Actionability

It provides fully executable Rust registration code and concrete bash commands (`cargo build`, `multi-content-type-examples clients-create`), plus a typed sub-client table, matching the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

The 'Adding a Custom Command' section is numbered (edit → build → run), but validation checkpoints are only implicit: there is no error-recovery feedback loop (e.g. 'if the build fails, fix and rebuild'), matching the 'sequence present but checkpoints missing or implicit' anchor.

2 / 3

Progressive Disclosure

The skill is a single self-contained file with no external references and is organized into clear, well-signaled sections (Overview, Architecture, Adding a Custom Command, Regeneration Safety, Build & Test); per the simple-skill note, well-organized sections with no need for external references earn the top score.

3 / 3

Total

10

/

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 and clearly scoped to a niche tool, but it omits any 'Use when...' trigger guidance and relies on tool-internal jargon, leaving the 'when to use' question unanswered and capping completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when adding or modifying custom commands for the multi-content-type-examples CLI.'

Add user-facing synonyms (e.g. 'custom CLI commands', 'add a new CLI subcommand') alongside the tool-specific terms to improve trigger coverage.

List one or two concrete actions beyond 'author' (e.g. 'register, build, and test custom commands') to lift specificity.

DimensionReasoningScore

Specificity

Names the domain and the single action 'author custom commands for the multi-content-type-examples CLI', but does not list multiple distinct concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multiple-actions anchor at 3.

2 / 3

Completeness

It clearly states what the skill does ('How to author custom commands... using the co-generated SDK') but provides no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

'custom commands' is a term a user might say, but it is wrapped in tool-specific jargon ('co-generated SDK', the named CLI) and lacks common variations, so it sits above the no-natural-keywords anchor (1) but below good coverage (3).

2 / 3

Distinctiveness Conflict Risk

It is scoped to a single named CLI ('multi-content-type-examples CLI'), a clear niche with distinct triggers unlikely to conflict with other skills, matching the 'clear niche with distinct triggers' anchor.

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.