CtrlK
BlogDocsLog inGet started
Tessl Logo

query-docs-library-metadata

Retrieve machine-readable context with tanstack libraries, tanstack doc, tanstack search-docs, tanstack create --list-add-ons --json, and --addon-details for agent-safe discovery and preflight validation.

61

Quality

72%

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 ./packages/cli/skills/query-docs-library-metadata/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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, highly actionable, and well-structured with executable commands and a properly signaled one-level reference file; its only gap is the lack of an explicit validation feedback loop in the discovery workflow.

DimensionReasoningScore

Conciseness

The body is lean and code-forward with no padding about what TanStack or libraries are, but a few prose passages (the 'HIGH Tension' meta-section and Common Mistakes explanations) could be trimmed slightly, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Commands are fully executable and copy-paste ready ('npx @tanstack/cli libraries --json', 'npx @tanstack/cli doc router framework/react/guide/routing', 'search-docs "server functions" --library start --json') and the Wrong/Correct pairs cover the common cases comprehensively.

5 / 5

Workflow Clarity

The HIGH mistake provides a clear two-step sequence (resolve valid library id, then fetch) where the resolve step acts as the preflight validation checkpoint, but there is no explicit error-recovery feedback loop (e.g. 'if the id is invalid, re-run libraries'), keeping it just below 5.

4 / 5

Progressive Disclosure

The body is a well-organized overview (Setup, Core Patterns, Common Mistakes, References) with a clearly signaled one-level-deep reference to references/discovery-command-output-schemas.md (a real file), keeping bulky output schemas appropriately out of the main skill.

5 / 5

Total

18

/

20

Passed

Description

58%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 niche-focused, listing concrete CLI commands, but it omits an explicit 'Use when...' trigger clause and relies on technical jargon over natural user phrasings, capping completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when looking up TanStack library metadata, fetching or searching TanStack docs, or enumerating create add-ons before scaffolding.'

Swap jargon ('agent-safe discovery', 'preflight validation') for plain user-facing terms like 'library metadata', 'docs lookup', and 'add-on discovery' to improve trigger-term quality.

Clarify the action beyond a single 'Retrieve' verb by naming what each command returns (list libraries, fetch a doc page, search docs, list add-ons) to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description enumerates several concrete CLI commands ('tanstack libraries', 'tanstack doc', 'tanstack search-docs', 'tanstack create --list-add-ons --json', '--addon-details') for discovery and validation, but a single verb 'Retrieve' with a vague purpose ('agent-safe discovery and preflight validation') leaves minor coverage gaps.

4 / 5

Completeness

The 'what' is clear (retrieve context via listed commands), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric; the 'when' is only weakly implied by 'for agent-safe discovery and preflight validation'.

3 / 5

Trigger Term Quality

It surfaces relevant terms (tanstack, libraries, doc, search-docs) but they are command names rather than natural user phrasings, and it leans on jargon ('machine-readable context', 'agent-safe discovery', 'preflight validation') while missing common synonyms like 'documentation', 'docs lookup', or 'library metadata'.

3 / 5

Distinctiveness Conflict Risk

It targets a clear niche (TanStack CLI metadata/doc discovery) that is mostly distinct, though the body itself flags overlap tension with create-app-scaffold and choose-ecosystem-integrations, indicating minor conflict risk with closely related skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
TanStack/cli
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.