CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

devtools

Connect native Preact Table v9 instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools. Load for React-package mixups, missing targets, required options.key, enabled state, cleanup, or development gating.

Quality

90%

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

92%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 lean, highly actionable body: one complete executable Setup example, three concrete Wrong/Correct mistake entries with sources, and a specific API discovery path, with zero filler. The only notable gap is lifecycle coverage — the `enabled` option gets a single unshown mention and cleanup is absent despite being an advertised trigger term.

Suggestions

Add a short cleanup/unmount note or example (e.g., what happens to registered targets when a table unmounts), since the description advertises 'cleanup' as a trigger but the body never addresses it.

Show the `{ enabled }` option in a one-line snippet so the 'pass { enabled } rather than conditionally calling the registration hook' guidance is copy-paste ready.

DimensionReasoningScore

Conciseness

The body contains no concept explanations and no padding: the Setup code block, terse Wrong/Correct pairs ("Wrong: omit `key` or reuse `users-table`"), and the one-line API Discovery pointer each earn their place. The only arguably trimmable line is the opener duplicating the frontmatter `requires`, which still serves standalone readability.

5 / 5

Actionability

The Setup block is complete, copy-paste-ready code with imports, typing, and rendering, and the Common Mistakes entries give concrete Wrong/Correct pairs. It falls short of the top anchor because "Pass `{ enabled }" is never shown in code and "cleanup" — a trigger the description explicitly advertises — receives no guidance or example at all.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill (~45 non-blank content lines) whose one action — configure the table, call useTanStackTableDevtools, render TanStackDevtools — is unambiguous in the Setup example, so the simple-skill exception applies. There are no destructive or batch operations that would require validation checkpoints.

5 / 5

Progressive Disclosure

A well-organized single-file skill (Setup / Hooks and Components / Common Mistakes / API Discovery) with no need for external references at this size: nothing is buried, no reference chains exist, and no content clearly belongs in a separate file. The simple-skill guidance for short, reference-free skills is satisfied.

5 / 5

Total

19

/

20

Passed

Description

87%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 strong description: it explicitly answers both what and when, names the exact APIs and version, and defines a sharply distinct niche that self-disambiguates from the React adapter. Trigger terms are relevant and specific but lean slightly technical ("development gating") and miss a few natural user phrasings.

DimensionReasoningScore

Specificity

"Connect native Preact Table v9 instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools" names the exact domain, version, and APIs, but the 'what' is essentially a single connect action rather than the multiple distinct concrete actions of the top anchor. It sits above anchor 3 because the precise API names and detailed scenario list exceed '1-2 concrete actions'.

4 / 5

Completeness

The what is explicit ("Connect native Preact Table v9 instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools") and the when is explicit ("Load for React-package mixups, missing targets, required options.key, enabled state, cleanup, or development gating") with six concrete trigger phrases, matching the top anchor. The 'Use when...' cap does not apply since an equivalent trigger clause is present.

5 / 5

Trigger Term Quality

"React-package mixups, missing targets, required options.key, enabled state, cleanup, or development gating" covers several relevant failure-mode keywords, but omits natural user phrasings (e.g., "devtools not showing", "debug my table") and "development gating" is library-internal jargon users would not naturally say.

4 / 5

Distinctiveness Conflict Risk

"native Preact Table v9" plus the named exports carve out a clear niche, and the "React-package mixups" trigger explicitly disambiguates from the React adapter, so the risk of triggering the wrong skill is minimal.

5 / 5

Total

18

/

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.

Validation — 14 / 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

Path

packages/preact-table-devtools/skills/devtools/SKILL.md

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.