Name: devtools
Rating: 64.8 (1 reviews)
Author: TanStack

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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/solid-table-devtools/skills/devtools/SKILL.md

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 lean, executable, and well-structured, with copy-paste setup code and concrete common-mistake guidance; only workflow clarity leaves slight room for explicit checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is lean: a complete minimal setup example plus tight Wrong/Correct mistake entries with sources, no padding, no explaining concepts Claude already knows; every token earns its place.	5 / 5
Actionability	The setup block is copy-paste ready executable code covering the common case, mistakes give concrete wrong/correct pairs, and API Discovery names exact .d.ts paths to inspect.	5 / 5
Workflow Clarity	The setup code embeds a clear sequence (create table, call hook, render plugin) and the owner/enabled/cleanup nuances are surfaced via mistakes, but there are no explicit prose checkpoints; minor validation gaps keep it just below 5.	4 / 5
Progressive Disclosure	A short, well-organized body with clearly labeled sections (Setup, Hooks and Components, Common Mistakes, API Discovery) and one-level-deep external references to .d.ts files; no bundle files exist and none are needed.	5 / 5
	Total	19 / 20 Passed

Description

62%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 and well-scoped to a distinct niche, but it omits an explicit 'Use when...' trigger clause and leans on technical jargon over natural user phrases, capping completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming user-facing scenarios (e.g., 'Use when debugging a Solid Table v9 app or wiring up TanStack devtools').

Soften jargon by pairing API names with natural phrases users actually say (e.g., 'Solid Table devtools', 'debug my table').

Lead with the primary action and reserve the conditions list (key, enabled, cleanup, production) as supporting detail.

Dimension	Reasoning	Score
Specificity	Names concrete APIs (tableDevtoolsPlugin, useTanStackTableDevtools) and specific concerns (reactive owner, options.key, enabled state, cleanup, dev vs production), giving several concrete actions with only minor gaps versus a clean comprehensive action list.	4 / 5
Completeness	The 'what' is clear (connect Solid Table v9 to Devtools), but there is no explicit 'Use when...' trigger clause; the 'Load for missing targets, required options.key...' fragment lists load conditions rather than user scenarios, so per the missing-trigger-clause rule completeness caps at 3.	3 / 5
Trigger Term Quality	'Devtools' and 'Solid Table' are natural terms a developer would say, but the description leans heavily on API-level jargon and lacks common variations or user-facing synonyms; missing a plain 'Use when debugging Solid Table' phrasing.	3 / 5
Distinctiveness Conflict Risk	The niche is sharply scoped to TanStack Solid Table v9 devtools integration, with distinctive API names making conflict with other skills minimal.	5 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 9e523bc

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.