CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/vue-table-devtools/skills/devtools/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 lean, well-structured integration guide with executable setup code and concrete pitfall guidance. Its main gaps are abstract (non-code) corrective instructions in Common Mistakes and an informal workflow sequence.

Suggestions

Add a short executable snippet for each Common Mistake 'Correct' path (e.g., show the ref being passed to useTanStackTableDevtools) to lift actionability to 5.

Number the core setup sequence (1. create table, 2. call hook, 3. mount plugin once) to make the workflow explicit.

Expand the terse 'Hooks and Components' section or fold its guidance into Setup so the body is uniformly actionable.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids explaining basic concepts; sections like Common Mistakes give only Wrong/Correct/Source with no padding, so every token earns its place.

5 / 5

Actionability

The Setup block is copy-paste ready executable Vue code and API Discovery points to concrete .d.ts files, but the Common Mistakes 'Correct' guidance is abstract ('pass the ref/maybe-ref shape accepted by the hook') rather than executable code, leaving minor gaps.

4 / 5

Workflow Clarity

The sequence (create table -> useTanStackTableDevtools -> mount tableDevtoolsPlugin once) is clear and the operation is non-destructive so no validation checkpoints are required, though the steps are not formally numbered.

4 / 5

Progressive Disclosure

Content is well organized into clear sections (Setup, Hooks and Components, Common Mistakes, API Discovery) with no nested references, but at ~63 lines it slightly exceeds the under-50-line simple-skill threshold and the Hooks and Components section is thin.

4 / 5

Total

17

/

20

Passed

Description

71%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-distinguished, clearly communicating a niche Vue/TanStack devtools integration with explicit trigger conditions. Its main weakness is jargon-heavy trigger phrasing that lacks natural user vocabulary and a slightly condition-list framing of when-to-use.

Suggestions

Add an explicit 'Use when...' clause with natural user phrasing (e.g., 'Use when wiring TanStack Vue Table into Devtools for debugging') to improve trigger term quality and completeness.

Surface a few plain-language synonyms ('debug table', 'devtools panel') alongside the API names so users' natural requests match.

Reframe the load-conditions list as concrete actions ('register', 'gate by environment', 'clean up on replacement') to lift specificity from 4 to 5.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete triggers ('missing targets, reactive table replacement, required options.key, enabled state, cleanup, or development gating'), but these read as use-case conditions more than a comprehensive set of distinct actions, so it falls short of a 5.

4 / 5

Completeness

It states what the skill does ('Connect Vue Table v9 refs or instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools') and gives explicit when guidance via the load-conditions list, though a more conventional 'Use when...' phrasing would make the trigger clearer.

4 / 5

Trigger Term Quality

Relevant technical keywords (Vue Table, Devtools, key, cleanup) are present but the phrasing is jargon-heavy and omits natural user phrases like 'debug my TanStack table' or 'devtools panel', leaving common variations missing.

3 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to Vue Table v9 devtools integration with distinct API names, making it unlikely to trigger for unrelated skills.

5 / 5

Total

16

/

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.