query-parameters-api-custom-commands

How to author custom commands for the query-parameters-api CLI using the co-generated SDK.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./seed/cli/query-parameters-openapi-as-objects/.agents/skills/custom-commands/SKILL.md

Quality

Content

57%

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

The content is well-structured, code-forward, and appropriately self-contained, with a strong regeneration-safety explanation. Its main weaknesses are the empty "Available SDK Clients" section and the absence of validation checkpoints in the build/regeneration workflow.

Suggestions

Fill in or remove the "Available SDK Clients" section so it lists the actual sub-clients or links to where they are documented.

Add a validation checkpoint to the regeneration workflow, e.g. "After fern generate, run cargo build to confirm custom.rs still compiles before proceeding."

Make the example call verifiable by either documenting the real sub-client/method names or clearly marking client.resource.get(id) as illustrative.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and code-forward without explaining known concepts, but the empty "Available SDK Clients" section and the regeneration table restating the architecture diagram are minor wasted structure that could be tightened.	2 / 3
Actionability	A complete, copy-paste-style register() example and executable build commands are provided, but the "Available SDK Clients" section lists no actual sub-clients and client.resource.get(id) is illustrative rather than verifiable, leaving key details incomplete.	2 / 3
Workflow Clarity	Steps are numbered and sequenced and regeneration behavior is explained, but there are no validation or verification checkpoints (e.g. confirming the build compiles after fern generate), which caps workflow clarity at 2 for a regeneration workflow.	2 / 3
Progressive Disclosure	The self-contained body is well-organized into clear sections (Overview, Architecture, Adding a Custom Command, Regeneration Safety, Build & Test) with easy navigation and no nested references, which earns a 3 for a simple skill with no external bundle files.	3 / 3
	Total	9 / 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 concrete and clearly scoped to a specific CLI, but it lacks an explicit "Use when..." trigger and uses technical phrasing that users would not naturally say. Adding natural trigger terms and a when-to-use clause would raise the weaker dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to add or modify custom commands for the query-parameters-api CLI."

Replace or augment technical phrasing like "co-generated SDK" with natural user-facing terms such as "typed SDK client".

List a couple of concrete actions (e.g. "register, build, and run custom CLI commands") to strengthen specificity.

Dimension	Reasoning	Score
Specificity	"How to author custom commands for the query-parameters-api CLI using the co-generated SDK" names a concrete domain and a main action, but lists only one action rather than multiple specific concrete actions.	2 / 3
Completeness	It states what the skill does (author custom commands) but has no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Relevant keywords like "author custom commands" and "CLI" appear, but proprietary phrasing ("co-generated SDK") and missing common variations mean users would not naturally say these terms.	2 / 3
Distinctiveness Conflict Risk	Naming the specific "query-parameters-api CLI" gives it a clear narrow niche, making it unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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/query-parameters-openapi-as-objects/.agents/skills/custom-commands/SKILL.md
Commit: 37dc173

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.