create-table-hook

Create reusable Octane table infrastructure with createTableHook, useAppTable, createAppColumnHelper, registered components, stable App wrappers, and typed context hooks. Load for recurring conventions, scoped contexts, or prop drilling.

Quality

76%

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

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, actionable reference: executable setup, core patterns, wrong/correct pitfalls, and a verification pointer, with no concept fluff. Minor gaps are the non-standard code shorthand and absence of an explicit validation feedback loop.

Dimension	Reasoning	Score
Conciseness	Lean and dense throughout: it assumes Claude's competence, never explains what tables/React/context are, and every prose line (e.g. 'Create the factory at module scope...') earns its place alongside executable code.	5 / 5
Actionability	Provides concrete, mostly copy-paste-ready code with imports and typed usage plus wrong/correct pairs, but the non-standard `@{` body shorthand and `<output>` tags prevent the examples from being fully executable TSX as written.	4 / 5
Workflow Clarity	Sections are clearly sequenced (Setup, Core Patterns, Common Mistakes, API Discovery) and the API Discovery step acts as an inspection checkpoint, but there is no explicit multi-step workflow with validation feedback loops.	4 / 5
Progressive Disclosure	Well-organized into clear sections with one-level-deep, clearly signaled references (inline 'Source:' citations and the 'API Discovery' pointer to specific .d.ts files), though source citations are slightly scattered rather than consolidated.	4 / 5
	Total	17 / 20 Passed

Description

71%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 distinctive, naming concrete APIs and an explicit load-trigger clause. Its main weakness is trigger-term quality: it leans on API jargon over natural user phrasing.

Suggestions

Add natural user-facing trigger phrases (e.g., 'Use when repeating table setup across screens', 'Use when avoiding prop drilling into table cells') alongside the API names.

Include common synonyms/variations a user might say (e.g., 'shared table config', 'table context', 'reusable table hook') to broaden trigger coverage.

Sharpen the 'when' clause by tying each trigger to a concrete user cue rather than only an internal concept like 'scoped contexts'.

Dimension	Reasoning	Score
Specificity	Lists several concrete building blocks (createTableHook, useAppTable, createAppColumnHelper, registered components, stable App wrappers, typed context hooks), but the actions themselves reduce to 'Create' and 'Load' rather than many distinct verbs, leaving minor coverage gaps.	4 / 5
Completeness	Clearly states what ('Create reusable Octane table infrastructure with...') and gives explicit 'Load for...' trigger guidance with concrete scenarios, but the 'when' could be slightly more specific about user-facing cues.	4 / 5
Trigger Term Quality	Natural trigger phrases are limited to 'recurring conventions, scoped contexts, or prop drilling'; the bulk of the description is API names (technical jargon) rather than phrases a user would naturally say, and common synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	Tightly scoped to Octane table infrastructure with named APIs (createTableHook, useAppTable), giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/octane-table/skills/create-table-hook/SKILL.md
Commit: 21d713f

Reviewed: 5 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.