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

81%

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

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 an efficient, well-structured guide with executable setup code and concrete, source-cited common mistakes. The main gaps are the prose-only plugin-mounting step and implicit rather than explicit step sequencing.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a single copy-paste setup example, terse Wrong/Correct/Source mistake entries, and no padding or explanations of concepts Claude already knows. The Hooks paragraph and the ref-unwrap mistake are complementary (behavior vs. anti-pattern), not redundant, so every token earns its place.

5 / 5

Actionability

The Setup SFC is complete and executable, and each Common Mistake gives concrete Correct guidance plus provenance. It misses 5 because the required tableDevtoolsPlugin({}) host mounting is described only in prose ("Mount the Vue TanStackDevtools host once with tableDevtoolsPlugin({})") with no code showing where or how it is registered.

4 / 5

Workflow Clarity

The flow (setup code, mount host, hook behavior, mistakes to avoid, API discovery) is coherent and unambiguous for this non-destructive, single-purpose task. It is not 5 because sequencing is implicit via sections and the mount instruction appears after the registration code that depends on it.

4 / 5

Progressive Disclosure

Sections are well-organized and compact, with API Discovery correctly pointing to .d.ts files for detail. It is not 5 because the body is ~64 lines (over the under-50-line simple-skill exception) and references docs/devtools.md, which is an upstream repo path rather than a bundle file (no references/, scripts/, or assets/ exist).

4 / 5

Total

17

/

20

Passed

Description

73%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 highly distinctive with a clear what and an explicit trigger clause, though the trigger list leans on terse internal jargon rather than natural user phrases and describes only one or two concrete actions. It is a solid, specific description with room to make triggers more user-facing.

Suggestions

Rewrite the trigger clause in natural user phrasing, e.g. "Load when Vue TanStack Table devtools targets are missing, a table ref is replaced, options.key errors appear, or the panel only works in development".

Add one more concrete action verb beyond "Connect" (e.g. mentioning mounting the Devtools host with tableDevtoolsPlugin as a distinct step) to lift capability coverage.

DimensionReasoningScore

Specificity

"Connect Vue Table v9 refs or instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools" names the domain and 1-2 concrete actions via specific APIs, but the second sentence lists trigger scenarios rather than additional actions, so coverage is not comprehensive as anchor 4 requires.

3 / 5

Completeness

Both parts are present: a clear "what" ("Connect Vue Table v9 refs or instances to Devtools with tableDevtoolsPlugin and useTanStackTableDevtools") and an explicit "Load for..." trigger clause, so the missing-trigger cap at 3 does not apply. It falls short of 5 because the triggers are terse jargon noun phrases ("enabled state", "development gating") rather than concrete natural trigger phrases.

4 / 5

Trigger Term Quality

Natural terms like "Devtools", "Vue Table", "refs", "cleanup", and "key" give good keyword coverage, but common variations users might say ("TanStack", "debug table", "devtools panel") are missing, falling short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (Vue Table v9 + @tanstack/vue-table-devtools) with API-specific triggers, making it highly distinguishable from other skills with minimal conflict risk.

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.

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.