CtrlK
BlogDocsLog inGet started
Tessl Logo

api-not-found

Diagnose missing TanStack Table v9 exports, options, state slices, and instance methods. Load before inventing an API when code sees a type error, undefined feature method, absent object key, adapter mismatch, or v8-shaped example.

68

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

A dense, actionable diagnostic skill with concrete code and a clear discovery order. It loses points for missing explicit validation checkpoints and for inlining content that a focused reference file could offload.

Suggestions

Add an explicit verification step in the API Discovery flow (e.g., assert the discovered export resolves the original type error before adopting it).

Introduce the shared variables used in snippets (rowSortingFeature, row, columnVisibilityFeature) or note they are illustrative, so examples run as-is.

Consider moving the Common Mistakes catalog into a bundled reference file and keeping SKILL.md as an overview with one-level-deep links.

DimensionReasoningScore

Conciseness

Lean throughout: no preamble explaining what TanStack Table is or how libraries work; every section is code or a concrete directive. Version detail lives in frontmatter, not the body.

5 / 5

Actionability

Setup block, rg commands, and Wrong/Correct pairs are executable and copy-pasteable, but several snippets reference undefined variables (rowSortingFeature, row, columnVisibilityFeature) without showing their origin.

4 / 5

Workflow Clarity

An ordered API Discovery sequence and a feature-gating checkpoint exist, but there is no explicit validate/verify step or feedback loop for the diagnostic flow; checkpoints are implicit.

3 / 5

Progressive Disclosure

Well-organized sections (Setup, Core Patterns, Common Mistakes, API Discovery) with no nested references and no bundle files; inlined at ~100 lines when a small reference split could aid navigation, so not a 5.

4 / 5

Total

16

/

20

Passed

Description

92%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.

A tight, third-person description that clearly defines a narrow diagnostic niche and supplies concrete trigger conditions. Both 'what' and 'when' are explicit and version-scoped.

DimensionReasoningScore

Specificity

Names the domain (TanStack Table v9) and lists multiple concrete diagnostic targets — 'exports, options, state slices, and instance methods' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly states both what ('Diagnose missing TanStack Table v9 exports, options, state slices, and instance methods') and when ('Load before inventing an API when code sees a type error...'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural developer-facing triggers like 'type error, undefined feature method, absent object key, adapter mismatch, or v8-shaped example' are strong and relevant, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The 'TanStack Table v9' niche with version-specific v8-migration triggers is highly distinct and unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

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