create-table-hook

Create reusable Solid table infrastructure with createTableHook, createAppTable, createAppColumnHelper, shared features/defaults, component registries, App wrappers, and typed context hooks. Load for recurring app conventions, reactive per-table getters, or prop drilling.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/solid-table/skills/create-table-hook/SKILL.md

Quality

Content

88%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 lean, executable, and well-structured with concrete Wrong/Correct examples and a single external pointer for exact API details; it loses only a little on workflow clarity for lacking explicit verification checkpoints and on progressive disclosure because no separate reference files are used.

Suggestions

Add an explicit verification step in API Discovery (e.g., 'Confirm the returned names match the .d.ts before relying on them') to strengthen the feedback loop.

Consider extracting the API surface into a referenced file (e.g. references/api.md) so SKILL.md stays a pure overview, which would lift progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	Lean throughout: no padding, no explaining of basics, just setup, core patterns, and mistakes with minimal prose; the API Discovery section points to the .d.ts rather than restating types.	5 / 5
Actionability	Copy-paste-ready executable code for setup, column inference, reactive data via getters, and concrete Wrong/Correct pairs for each common mistake, covering the common cases.	5 / 5
Workflow Clarity	Sequenced sections (Setup -> Core Patterns -> Common Mistakes -> API Discovery) with corrective examples, but there are no explicit validation/verification checkpoints; this is not a destructive/batch workflow so the cap does not apply, yet a checkpoint for verifying returned names against the .d.ts is only implied.	4 / 5
Progressive Disclosure	Well-organized single-file overview with clear section headers and a one-level pointer to the .d.ts for exact API names; no bundle files exist, and content is appropriately self-contained, with only minor room to externalize the API reference.	4 / 5
	Total	18 / 20 Passed

Description

62%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 technical, naming concrete APIs and including an explicit 'Load for...' trigger, but trigger terms are more internal/API-flavored than the natural language a user would say.

Suggestions

Reword the 'Load for...' clause to use natural user phrasing (e.g., 'Use when sharing table configuration across many tables, avoiding prop drilling, or needing per-table reactive data').

Add common synonyms users would say, such as 'reusable tables', 'shared table setup', or 'Solid table factory', to improve trigger matching.

Ensure the description uses consistent third-person voice and trims the API-name list slightly to favor capability descriptions.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (createTableHook, createAppTable, createAppColumnHelper, shared features/defaults, component registries, typed context hooks), though some are API names rather than user-facing capabilities, leaving minor coverage gaps.	4 / 5
Completeness	Clear 'what' (build reusable table infrastructure) and an explicit 'Load for...' trigger clause covering recurring conventions, reactive getters, and prop drilling; the 'when' is present but could be more specific about typical user phrasings.	4 / 5
Trigger Term Quality	Includes relevant terms like 'prop drilling' and 'recurring app conventions' but lacks the natural synonyms or variations a user would say (no 'reusable tables', 'shared table config', or file extensions), and the phrasing leans technical.	3 / 5
Distinctiveness Conflict Risk	The Solid/TanStack table factory niche is fairly distinct and tied to specific API names, with only minor overlap risk against a generic table-state or getting-started skill.	4 / 5
	Total	15 / 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/solid-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.