CtrlK
BlogDocsLog inGet started
Tessl Logo

create-table-hook

Create an Angular injectAppTable/createAppColumnHelper abstraction with shared features/defaults, registered components, injectTableContext/injectTableCellContext/injectTableHeaderContext, and correct FlexRender component-versus-function handling.

60

Quality

70%

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/angular-table/skills/create-table-hook/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

90%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, highly actionable pattern reference with strong Wrong/Correct examples and no fluff. It would benefit only from an explicit verify step after the API-discovery inspection.

DimensionReasoningScore

Conciseness

The body is lean: terse code-first sections with one-line rationales and no padding or re-explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Executable TypeScript setup and column-definition snippets plus paired Wrong/Correct blocks for each common mistake give copy-paste-ready guidance across the common cases.

5 / 5

Workflow Clarity

A clear Setup → Core Patterns → Common Mistakes → API Discovery sequence is present, but there are no explicit validation checkpoints; this is acceptable because the skill is non-destructive, so it sits just below 5.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and a real in-repo inspection pointer (node_modules types); no nested references, though no separate reference files are used to offload detail.

4 / 5

Total

18

/

20

Passed

Description

51%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 occupies a clear niche, but it reads as an API inventory rather than a user-facing trigger and omits any 'Use when...' guidance. Adding natural trigger phrases would lift both completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause with natural triggers, e.g. 'Use when building repeated/shared Angular table conventions; keep one-off tables on injectTable.'

Replace some API identifiers with user-facing terms like 'composable Angular table' or 'shared table defaults' so the description matches how users actually ask.

Keep the named exports but lead with the intent (shared table abstraction) before listing the injectors.

DimensionReasoningScore

Specificity

Names several concrete capabilities (injectAppTable/createAppColumnHelper abstraction, shared features/defaults, registered components, three typed injectors, FlexRender component-vs-function handling), with only minor abstraction in the framing verb 'Create an abstraction'.

4 / 5

Completeness

It clearly states 'what' the skill does but has no 'Use when...' or equivalent explicit trigger guidance, which the rubric caps at 3.

3 / 5

Trigger Term Quality

Dominated by API identifiers (injectAppTable, createAppColumnHelper, FlexRender, injectTableContext) rather than the natural phrases a user would actually say ('composable Angular table', 'shared table defaults'); common variations and synonyms are absent.

2 / 5

Distinctiveness Conflict Risk

The Angular composable-table niche with named app-hook APIs is mostly distinct, with only minor overlap risk against a more basic injectTable skill it builds upon.

4 / 5

Total

13

/

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.