CtrlK
BlogDocsLog inGet started
Tessl Logo

create-table-hook

Create a reusable Vue useAppTable/createAppColumnHelper with shared features/defaults, reactive per-table options, optional component registries, dynamic App wrappers, typed context hooks, and explicit types that break circular inference.

58

Quality

68%

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/skills/create-table-hook/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 tight, highly actionable pattern reference: executable code throughout, a Wrong/Correct structure for the key gotchas, and a concrete API-discovery pointer. Its only weak spot is the absence of a true multi-step workflow, which leaves workflow_clarity just below the top anchor.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no preamble explaining Vue or TanStack — with brief one-line rationales after each Wrong/Correct pair; only minor phrasing could be trimmed further.

4 / 5

Actionability

Provides fully executable, copy-paste-ready TypeScript/Vue blocks for setup, core patterns, and each common mistake, plus a concrete 'inspect this .d.ts path' instruction for API discovery.

5 / 5

Workflow Clarity

A clear logical structure (Setup → Core Patterns → Common Mistakes → API Discovery) with no destructive or batch operations requiring validation; it falls just short of 5 because it is a pattern reference rather than an explicitly sequenced workflow with checkpoints.

4 / 5

Progressive Disclosure

Content is well-organized under clearly headed sections in a single self-contained file with no need for external bundle references, but at ~127 lines it exceeds the under-50-line simple-skill exception and has no one-level-deep references to signal.

4 / 5

Total

17

/

20

Passed

Description

55%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 highly distinct but is written for an expert audience: it enumerates concrete capabilities without any natural-language trigger guidance. Adding a 'Use when...' clause with user-facing terms would materially raise completeness and trigger_term_quality.

Suggestions

Add an explicit 'Use when...' trigger clause naming natural user phrases (e.g. 'Use when setting up reusable Vue table conventions with @tanstack/vue-table').

Soften the jargon density by including common synonyms a user might say ('Vue table composable', 'app table defaults') alongside the API names.

Lead with the user-facing purpose before the feature list so the 'what' is anchored to a recognizable goal.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ('shared features/defaults, reactive per-table options, optional component registries, dynamic App wrappers, typed context hooks, and explicit types that break circular inference') but reads as a feature enumeration with minor coverage gaps rather than a fully comprehensive action list.

4 / 5

Completeness

It clearly states what the skill does ('Create a reusable Vue useAppTable/createAppColumnHelper...') but contains no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

The text is dominated by technical jargon ('circular inference', 'typed context hooks', 'dynamic App wrappers') and API names ('useAppTable/createAppColumnHelper'); it lacks the natural phrases a user would actually say when they need this skill.

2 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (Vue + TanStack table composable with this specific hook pattern) that is unlikely to trigger for unrelated skills.

5 / 5

Total

14

/

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.