CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

devtools

Connect Vue Table v9 refs or instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools. Load for missing targets, reactive table replacement, required options.key, enabled state, cleanup, or development gating.

Quality

88%

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

86%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 tight, well-structured body: executable setup code, concrete Wrong/Correct mistake entries with source citations, and a precise API-discovery pointer, all with essentially no token waste. The main improvement opportunity is making the tableDevtoolsPlugin registration concrete in code rather than prose.

Suggestions

Add a short code snippet showing where and how tableDevtoolsPlugin({}) is registered (e.g., in app/main setup via app.use) so the full wiring sequence is copy-paste ready.

State the expected setup order explicitly (mount the Devtools host once at app setup, then call useTanStackTableDevtools per table component) to remove the implicit sequencing in the Setup section.

DimensionReasoningScore

Conciseness

The body is lean and assumes Vue competence: a complete setup snippet, terse Wrong/Correct mistake pairs, and one-line source citations, with no concept padding. The only near-redundant token is the opening 'This skill builds on...' line that duplicates frontmatter requires, which is not enough to drop below anchor 5.

5 / 5

Actionability

The Setup block is complete, executable code (useTable with key/features, useTanStackTableDevtools(table)) and API Discovery names exact .d.ts files to inspect, but the pivotal plugin registration ('Mount the Vue TanStackDevtools host once with tableDevtoolsPlugin({})') is prose only — never shown in code, leaving a minor gap between anchor 4 and the copy-paste-ready coverage of 5.

4 / 5

Workflow Clarity

A clear sequence is discernible (create table → attach hook → mount host once), and the Common Mistakes section doubles as error-recovery guidance (ref unwrapping, duplicate keys, dev-only gating). It is not a 5 because the placement of the plugin mount (app setup vs component) and the hook/plugin ordering are implicit rather than explicitly sequenced; the task is non-destructive so no validation loop is required.

4 / 5

Progressive Disclosure

A compact single-purpose skill (~45 non-blank body lines) with no bundle files and no need for external references: content is appropriately inline, sections are well-organized (Setup, Hooks and Components, Common Mistakes, API Discovery), and there is no reference nesting. Fits the simple-skill case with clean structure.

5 / 5

Total

18

/

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: concrete named APIs for the 'what' and an explicit, condition-specific 'Load for...' trigger list for the 'when', scoped tightly to Vue Table v9 devtools. The only weaknesses are a few missing natural synonyms for the trigger scenarios.

DimensionReasoningScore

Specificity

Names concrete APIs ('tableDevtoolsPlugin', 'useTanStackTableDevtools') and specific operations ('Connect Vue Table v9 refs or instances to Devtools'), listing several specific actions with only minor gaps (setup and mounting detail is left to the body). It is well above the '1-2 concrete actions' of a 3 but not the comprehensive action coverage of a 5.

4 / 5

Completeness

Explicitly answers both: the 'what' ('Connect Vue Table v9 refs or instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools') and the 'when' via an explicit trigger clause ('Load for missing targets, reactive table replacement, required options.key, enabled state, cleanup, or development gating') with concrete trigger phrases.

5 / 5

Trigger Term Quality

'missing targets', 'reactive table replacement', 'required options.key', 'enabled state', 'cleanup', 'development gating', and 'Devtools' are natural phrases a user would report when hitting these problems. A few common variations (e.g., 'panel not showing', 'devtools blank in production') are missing, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Pins an exact niche (library 'vue-table-devtools', framework Vue, version v9, two named APIs), so it is clearly distinguishable from other table or devtools skills with minimal conflict risk. The voice is third-person imperative with no first/second-person penalty.

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