create-table-hook

Share Alpine tableFeatures, defaults, createAppTable, and createAppColumnHelper with createTableHook. Load when multiple Alpine tables repeat infrastructure; unlike JSX adapters, Alpine has no registered table/cell/header component or context registry.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%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, actionable reference: executable setup code, terse core patterns, concrete Wrong/Correct mistake entries with sources, and a precise API-discovery pointer. It is a patterns skill rather than a sequenced workflow, so workflow clarity lacks checkpoints but is otherwise clear.

Dimension	Reasoning	Score
Conciseness	Lean throughout: tight Setup code, terse one-paragraph pattern bullets, and Wrong/Correct mistake pairs with sources, assuming Claude already knows Alpine and JSX adapters with no padding.	5 / 5
Actionability	Provides fully copy-paste-ready Setup code (imports, types, columns, Alpine.data registration), concrete Wrong/Correct examples for each mistake, and a precise node_modules .d.ts path for API discovery.	5 / 5
Workflow Clarity	Organized into a clear Setup -> Core Patterns -> Common Mistakes -> API Discovery sequence with unambiguous guidance, but it is a patterns skill rather than a multi-step process, so it lacks explicit validation checkpoints; no destructive/batch cap applies.	4 / 5
Progressive Disclosure	No bundle files exist, the body is compact and well-structured with clear section headers, and its only external pointers (node_modules .d.ts, TanStack sources) are one level deep and clearly signaled.	5 / 5
	Total	19 / 20 Passed

Description

78%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, third-person, and clearly distinguishes the Alpine hook from JSX adapters while stating both what it does and when to load it. It is slightly held back by jargon-heavy triggers and a single shared-infrastructure action rather than a broader action list.

Suggestions

Add a couple of natural trigger phrases users would say (e.g. 'Use when wiring several Alpine tables to the same features and defaults') to lift trigger_term_quality and completeness.

Broaden the action wording beyond a single 'share' verb to name the concrete outcomes (e.g. 'Register shared table features, defaults, and column helpers; spin up per-component tables with local reactive data').

Dimension	Reasoning	Score
Specificity	Names concrete API symbols (tableFeatures, defaults, createAppTable, createAppColumnHelper, createTableHook) and a specific share action, but coverage is essentially a single shared-infrastructure action rather than a comprehensive multi-action list, so it sits below 5.	4 / 5
Completeness	Explicitly answers both 'what' (share tableFeatures/defaults/createAppTable/createAppColumnHelper with createTableHook) and 'when' (load when multiple Alpine tables repeat infrastructure); the 'when' is concrete but not elaborated with multiple trigger phrases, so it is below 5.	4 / 5
Trigger Term Quality	Includes natural-ish triggers like 'Load when multiple Alpine tables repeat infrastructure' and 'unlike JSX adapters', but the rest is API jargon (createTableHook, context registry) missing common synonyms or variations users would say.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear, narrow niche (the Alpine adapter) and explicitly contrasts it with JSX adapters, noting Alpine has no registered component/context registry, giving minimal conflict risk.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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/alpine-table/skills/create-table-hook/SKILL.md
Commit: 9e523bc

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.