CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

82%

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

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

An efficient, actionable, well-structured single-file skill with executable code and concrete mistake guidance. Workflow clarity is the weakest area because it presents reference material rather than a sequenced, validated process.

Suggestions

Add a brief validation step after Setup (e.g. confirm the TanStackDevtools panel renders and the table key appears in the target list) to turn the setup into a checkpointed workflow.

Consider a short ordered checklist for the most common mistake fixes so the sequence of diagnosis → fix → verify is explicit.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or elementary explanations; every line (setup code, mistake entries, API discovery pointer) earns its place and assumes Claude's competence with Preact/TanStack.

5 / 5

Actionability

Provides a fully executable, copy-paste-ready setup block plus concrete Wrong/Correct pairs and a precise API discovery path ('Inspect node_modules/@tanstack/preact-table-devtools/dist/index.d.ts'), covering the common integration cases.

5 / 5

Workflow Clarity

Content is organized by topic rather than sequenced steps, and the setup→hooks→mistakes flow has no explicit validation checkpoint confirming the devtools panel actually registers; this is more a reference layout than a validated workflow.

3 / 5

Progressive Disclosure

Well-organized single-file skill under 90 lines with no bundle files and no nested references; sections (Setup, Hooks and Components, Common Mistakes, API Discovery) are clearly signaled and appropriately scoped, so the simple-skill exception applies.

5 / 5

Total

18

/

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.

A highly specific, complete, and distinctive description that names exact APIs and concrete failure triggers. Trigger term quality is the weakest dimension because it leans on technical symbols rather than the natural phrases a user might utter.

Suggestions

Pair the API names with at least one user-natural phrase (e.g. 'Use when debugging Preact table state or wiring up TanStack Table devtools') so trigger_term_quality reaches natural-language coverage.

Consider adding a synonym such as 'Preact table inspector/debugger' alongside 'Devtools' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names multiple concrete actions and primitives — 'tableDevtoolsPlugin', 'useTanStackTableDevtools', 'Connect native Preact Table v9 instances to Devtools' — plus specific failure modes (React-package mixups, missing targets, required options.key, cleanup, development gating).

5 / 5

Completeness

Explicitly states what ('Connect native Preact Table v9 instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools') and when ('Load for React-package mixups, missing targets, required options.key, enabled state, cleanup, or development gating'), satisfying both halves with concrete trigger phrases.

5 / 5

Trigger Term Quality

The natural trigger terms are largely technical jargon ('tableDevtoolsPlugin', 'useTanStackTableDevtools', 'options.key') rather than phrases a user would naturally say; 'React-package mixups' is the closest to a colloquial trigger but most keywords are API names, not user-facing synonyms.

3 / 5

Distinctiveness Conflict Risk

A clear narrow niche (Preact + TanStack Table v9 devtools) with distinct package and API names; minimal overlap risk with other skills since the trigger set is highly specific to this library.

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.

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.