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.

70

Quality

87%

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

82%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 concise, action-oriented, and well-structured for a focused diagnostic skill, with executable snippets and an explicit discovery order. The main gaps are minor: a few partial code examples and the absence of explicit validation checkpoints in the discovery workflow.

Suggestions

Add the import statement for createSortedRowModel() (and any other introduced factory) so the Correct example is fully runnable.

Insert an explicit validation checkpoint in the API Discovery workflow—e.g. "confirm the export exists in the .d.ts before using it"—to close the feedback loop.

Tighten the Wrong/Correct blocks by noting where each snippet lives (file path) so Claude can jump straight to source.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence ("Treat the installed package—not remembered docs—as exact API truth"), with tight executable snippets; the few prose sentences convey non-obvious v8→v9 facts rather than padding.

5 / 5

Actionability

It provides concrete, mostly copy-paste-ready code (package.json/entrypoint reads, rg searches, tableFeatures/getValue/getPrototypeOf) with explicit Wrong/Correct pairs, but some snippets are partial (e.g. createSortedRowModel() shown without its import).

4 / 5

Workflow Clarity

The "API Discovery" section gives an explicit ordered sequence (package.json version → adapter dist → core dist → feature directory), but there are no explicit validation/feedback checkpoints; for this read-only diagnostic task that is only a minor gap.

4 / 5

Progressive Disclosure

The body is well-organized into clear sections (Setup, Core Patterns, Common Mistakes, API Discovery) with content appropriately inline and no nested references; at ~80 lines it slightly exceeds the simple-skill threshold, keeping it just short of a clean 5.

4 / 5

Total

17

/

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.

The description is strong: it states concrete capabilities, gives explicit load-when trigger phrases, uses third-person voice, and is tightly scoped to a distinct v9-diagnosis niche. Its only weakness is trigger-term breadth, which is technical-leaning and could include a few more common phrasings.

Suggestions

Add one or two lay phrasings to the trigger list (e.g. "is not a function", "cannot find export") to broaden natural-term coverage.

Consider naming the package or file extension cues users might mention (e.g. "@tanstack/react-table", ".d.ts") to round out trigger synonyms.

DimensionReasoningScore

Specificity

The description lists several concrete diagnostic targets—"missing TanStack Table v9 exports, options, state slices, and instance methods"—giving comprehensive coverage of the capability rather than vague abstraction.

5 / 5

Completeness

It explicitly answers both what ("Diagnose missing ... 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

It surfaces multiple natural developer trigger phrases ("type error, undefined feature method, absent object key, adapter mismatch, or v8-shaped example"), but the terms lean technical and omit a few common lay variations, stopping short of fully comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche scoped to TanStack Table v9 API-not-found diagnosis with version-specific triggers, making overlap with unrelated skills minimal.

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.