CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

devtools

Connect Solid Table v9 instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools in the proper reactive owner. Load for missing targets, required options.key, enabled state, cleanup, or development versus explicit production exports.

Quality

93%

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

100%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 body is a model of lean skill writing: one complete executable example, terse per-mistake Wrong/Correct entries with library-specific mechanism notes and source citations, and a one-line pointer to type declarations instead of inlined API detail. No dimension shows anchor-level defects; the only nitpick is slight overlap between the Hooks section and the first Common Mistake entry, which does not rise to a deduction.

DimensionReasoningScore

Conciseness

The body is ~41 non-blank lines of mostly code and concrete guidance with zero concept padding — it never explains what Solid or Devtools are, and every sentence ("The target registry skips missing keys and replaces duplicate identities") adds library-specific behavior Claude would not know. It matches anchor 5's "lean and efficient; every token earns its place" with nothing to trim toward anchor 4.

5 / 5

Actionability

The Setup block is complete, executable, copy-paste ready (imports, createTable with key, hook call, rendered TanStackDevtools), and the common cases each get concrete guidance: "Pass `{ enabled }` to the hook for conditional registration" and "use `/production` only on explicit request". This matches anchor 5's fully-executable examples covering the common cases, exceeding anchor 4's "minor gaps".

5 / 5

Workflow Clarity

This is a simple single-purpose skill (wire up devtools) and the single action is unambiguous: the Setup code shows the exact sequence (create table with key → call hook in owner → render component), and Common Mistakes adds wrong/correct guardrails for each failure mode. Per the rubric's simple-skill exception the single action can score 5; no destructive or batch operations exist that would cap it at 3.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed at this size; the body is under 50 non-blank lines with clean, well-labeled sections (Setup, Hooks and Components, Common Mistakes, API Discovery). The API Discovery section also defers detail one level deep to concrete paths ("node_modules/@tanstack/solid-table-devtools/dist/index.d.ts ... production.d.ts") instead of inlining them, matching the simple-skill exception for a 5.

5 / 5

Total

20

/

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, highly targeted description: it names the exact library, version, APIs, and the reactive-owner requirement for the "what", and provides an explicit multi-condition load clause for the "when". The only weaknesses are a slightly thin action list and a few missing natural synonyms such as "TanStack" or "debug".

DimensionReasoningScore

Specificity

"Connect Solid Table v9 instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools in the proper reactive owner" names the domain, version, both APIs, and the owner requirement, but the actual action list is essentially one connect action plus trigger topics ("missing targets, required options.key, enabled state, cleanup"), leaving minor gaps such as what Devtools lets you do once connected. This sits above anchor 3 (only 1-2 concrete actions, not comprehensive) but below anchor 5's fully comprehensive multi-action coverage.

4 / 5

Completeness

The "what" is explicit ("Connect Solid Table v9 instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools in the proper reactive owner") and the "when" is an equivalent explicit trigger clause enumerating concrete conditions ("Load for missing targets, required options.key, enabled state, cleanup, or development versus explicit production exports"). This clearly answers both what and when with concrete trigger phrases, matching anchor 5 rather than anchor 4 where the "when" could be more specific.

5 / 5

Trigger Term Quality

Phrases like "Devtools", "Solid Table v9", "options.key", "enabled state", "cleanup", and "production exports" are natural terms for this niche, and the named exports are strong triggers. A few natural synonyms users would say are missing (e.g., "TanStack", "debug", "inspect table state"), which matches anchor 4 rather than anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The combination of "Solid Table v9", "tableDevtoolsPlugin", "useTanStackTableDevtools", and "options.key" carves out a clear niche with distinct triggers and minimal conflict risk with other devtools skills. It matches anchor 5; it is far more distinct than anchor 4's "minor overlap risk with closely related skills".

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/solid-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.