CtrlK
BlogDocsLog inGet started
Tessl Logo

devtools

Connect React Table v9 instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools. Load for missing Table panels, registration lifecycle, required options.key, enabled state, or development versus explicit production exports.

70

Quality

86%

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

93%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 exceptionally lean and actionable, with a complete runnable example and tight Wrong/Correct guardrails. The only minor gap is the absence of explicit validation checkpoints, which is not strictly required for this non-destructive setup skill.

DimensionReasoningScore

Conciseness

The body is lean with no padding: it assumes Claude knows React/hooks basics and adds only library-specific facts (e.g. 'Core target registration skips keyless tables'), with every line earning its place.

5 / 5

Actionability

Provides a complete, copy-paste-ready TSX setup example, concrete Wrong/Correct pairs for each mistake, and a specific node_modules path to inspect for API discovery.

5 / 5

Workflow Clarity

The setup sequence is clear with ordering cues ('immediately after creating the table', 'near the application root') and the Common Mistakes act as guardrails, but there are no explicit validation checkpoints; acceptable since no destructive or batch operations are involved.

4 / 5

Progressive Disclosure

No bundle files exist; the body is well-organized into clearly signaled sections (Setup, Hooks and Components, Common Mistakes, API Discovery) with no nested references, fitting the simple-skill exception for a concise single-purpose skill.

5 / 5

Total

19

/

20

Passed

Description

80%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, explicit about both what and when, and highly distinct. Its main weakness is trigger-term naturalness: the load conditions read as technical jargon rather than phrases a user would naturally say.

Suggestions

Add a few natural-language trigger synonyms users would actually say (e.g. 'use when devtools panels are missing for a React Table', 'when the table is not showing in Devtools').

Consider leading the trigger clause with an explicit 'Use when...' phrasing to mirror the anchor examples and improve recall.

DimensionReasoningScore

Specificity

Names concrete APIs (tableDevtoolsPlugin, useTanStackTableDevtools) and the connect action plus a list of specific scenarios, but the capability is essentially a single action with several trigger conditions rather than multiple distinct actions.

4 / 5

Completeness

Clearly states what it does ('Connect React Table v9 instances to Devtools with...') and provides equivalent explicit trigger guidance via 'Load for missing Table panels, registration lifecycle...' with concrete trigger phrases.

5 / 5

Trigger Term Quality

Trigger phrases like 'missing Table panels', 'registration lifecycle', 'required options.key', 'enabled state' are relevant to the niche but phrased as technical jargon, missing the more natural synonyms a user would actually say.

3 / 5

Distinctiveness Conflict Risk

Tightly scoped to React Table v9 devtools with named APIs and a pinned library version, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

17

/

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.