create-table-hook

Create a reusable Lit useAppTable/createAppColumnHelper layer with host-backed controllers, shared features/defaults, typed cell/header renderers, App wrappers, and useTableContext for custom-element controls. Load when multiple Lit tables share infrastructure or prop drilling obscures table context.

Quality

80%

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/lit-table/skills/create-table-hook/SKILL.md

Quality

Content

76%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.

A concise, actionable framework skill with concrete code and useful Wrong/Correct patterns. Its main weakness is workflow clarity: it reads as a pattern catalog rather than a sequenced, checkpointed workflow, and the full usage shape relies on an external example.

Suggestions

Add a short, copy-paste-ready per-table usage snippet (initialize useAppTable as a host field and call table() during render) so the actionability gap left by the deferred example is closed inline.

Either bundle or inline a minimal version of the host/getter shape referenced from the composable-tables example, so progressive disclosure does not depend on an external, non-bundled source.

Reframe the Setup → usage → context flow as a short ordered checklist with a verification checkpoint (e.g., confirm the table instance is stable across renders) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a tight setup block, three short core patterns, and Wrong/Correct mistake entries with no padding or explanation of basic concepts.	5 / 5
Actionability	Executable setup code and concrete Wrong/Correct guidance are present, but the per-table host/getter usage shape is deferred to an unbundled example ("the maintained composable-tables example shows the complete host/getter shape"), leaving a minor gap.	4 / 5
Workflow Clarity	A loose Setup → Core Patterns → Common Mistakes structure exists, but there is no explicit sequenced workflow with validation checkpoints; this is a pattern/reference skill rather than a checkpointed process.	3 / 5
Progressive Disclosure	Sections are well organized with no nested references, but the ~75-line body is entirely inline and no bundled reference files exist to offload detail, leaving minor organization room.	4 / 5
	Total	16 / 20 Passed

Description

83%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.

A specific, well-structured description that clearly states both capability and an explicit load condition with natural trigger phrases. It is held back only slightly by a couple of abstract framings and minor overlap with related table skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete components/actions ("host-backed controllers, shared features/defaults, typed cell/header renderers, App wrappers, and useTableContext for custom-element controls"), though a few are framed as abstractions rather than fully concrete actions, keeping it just below comprehensive.	4 / 5
Completeness	Explicitly answers both what ("Create a reusable Lit useAppTable/createAppColumnHelper layer ...") and when ("Load when multiple Lit tables share infrastructure or prop drilling obscures table context") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural developer phrases appear ("multiple Lit tables share infrastructure", "prop drilling obscures table context"), giving good keyword coverage, though a few common synonyms/variations are absent.	4 / 5
Distinctiveness Conflict Risk	The composable-table-hook layer is a clear niche with distinct triggers, but it sits among sibling Lit table skills (getting-started, table-state), creating minor overlap risk.	4 / 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/lit-table/skills/create-table-hook/SKILL.md
Commit: 21d713f

Reviewed: 6 hours 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.