CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

devtools

Register TanStack Table targets and inspect options, state, features, columns, rows, and row models with @tanstack/table-devtools. Load for missing connections, required unique table options.key, target replacement/cleanup, or an explicit request for production Devtools entrypoints.

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, high-signal skill body: complete registration code, terse pattern rules, and Wrong/Correct/source-attributed pitfalls with zero generic explanation. The only notable gap is the absence of a framework-adapter registration example despite adapters being the recommended integration path. Organization is clean and nothing that belongs in a separate file is inlined.

Suggestions

Add a short framework-adapter registration example (e.g., the React hook or Angular injector usage) since "Let adapter lifecycles own registration" identifies adapters as the normal path but shows no code for it.

Clarify in the Setup snippet that cleanup() is called on unmount/teardown rather than immediately after registration, to avoid copy-paste misuse.

DimensionReasoningScore

Conciseness

Every section carries library-specific, non-obvious information ("The non-empty options.key is both registry identity and panel label", "Default production exports intentionally use no-op implementations") with no generic concept explanations or padding; per-mistake Source lines are compact attribution rather than filler.

5 / 5

Actionability

The Setup section provides a complete, executable TypeScript snippet (constructTable with features, upsertTableDevtoolsTarget, cleanup) and each mistake pairs a literal Wrong with a literal Correct value (key: 'billing-invoices'). The minor gap is that the recommended primary path — framework-adapter lifecycle registration — has no code example, only a pointer to the framework packages.

4 / 5

Workflow Clarity

This is a single-purpose skill with no multi-step process, and the single action (register a uniquely keyed target and clean it up) is unambiguous: the Setup snippet shows the full lifecycle including cleanup(), and the mistake entries explain the registry's failure behavior (logs missing-key error, returns without adding).

5 / 5

Progressive Disclosure

No bundle files exist, and none are needed at this size: the body is well-organized into Setup, Core Patterns, Common Mistakes, and API Discovery, with the bulk reference material correctly delegated to the package's own .d.ts files rather than inlined.

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 with an explicit two-part structure: concrete capabilities tied to a specific package, followed by an explicit load-trigger clause. It is written in third-person imperative voice with no fluff. The only room for improvement is broader natural-keyword coverage and slightly fuller enumeration of the actions it supports.

Suggestions

Add one or two more concrete actions beyond register/inspect (e.g., remove/clean up targets, enable production inspection) to reach comprehensive action coverage.

Include additional natural trigger phrasings users might say, such as "devtools panel not showing", "debug table state", or "duplicate table key".

DimensionReasoningScore

Specificity

"Register TanStack Table targets and inspect options, state, features, columns, rows, and row models" names the domain plus two concrete verbs with a detailed enumeration of inspection targets, but the action list is limited to register/inspect rather than the multiple distinct actions of the 5 anchor.

4 / 5

Completeness

The description explicitly answers what ("Register TanStack Table targets and inspect options, state, features, columns, rows, and row models") and when ("Load for missing connections, required unique table options.key, target replacement/cleanup, or an explicit request for production Devtools entrypoints") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms like "@tanstack/table-devtools", "Devtools", "table options.key", "missing connections", and "production Devtools entrypoints" match what affected users would say, but common variations such as "devtools not showing", "debug table state", or "panel" phrasing are absent.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to a single named package (@tanstack/table-devtools) with package-specific triggers (unique options.key, /production entrypoint), giving it a clear niche with minimal overlap against other 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/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.