CtrlK
BlogDocsLog inGet started
Tessl Logo

table-state

Use Angular-signal-backed table.atoms, direct template reads, computed selectors, controlled signals, value-or-updater callbacks, and external Angular Store atoms while accounting for injectTable initializer reruns.

60

Quality

71%

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/table-state/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is strong: executable, well-structured guidance with concrete wrong/correct code pairs and clear ownership rules tailored to this Angular TanStack table niche. It is concise and actionable, with only minor structural tightening possible.

DimensionReasoningScore

Conciseness

The body is largely lean and code-driven with minimal generic padding; only minor repetition (e.g. 'Angular-backed table atom reads are signal reads' restating the mental model) keeps it just below fully efficient.

4 / 5

Actionability

It provides copy-paste-ready TypeScript across Setup, Core Patterns, Initialize/Update/Reset, and Common Mistakes, with concrete wrong/correct pairs covering the common cases of external atoms, controlled signals, and updater handling.

5 / 5

Workflow Clarity

The content follows a logical progression (mental model → setup → patterns → ownership → init/reset → mistakes → API discovery); this is guidance rather than a destructive/batch workflow, so the missing validation-feedback loop is not a cap, though no explicit checkpoints are present.

4 / 5

Progressive Disclosure

The body is well-organized under clear section headers with one-level 'Source:' pointers to TanStack docs and node_modules type paths; no bundle files exist, and structure is good, though it runs longer than the under-50-line simple-skill case that would merit a 5.

4 / 5

Total

17

/

20

Passed

Description

60%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 highly specific and distinctive, but it is written as a technical capability list rather than a user-facing trigger: it lacks natural keywords and any explicit 'Use when...' guidance. Adding trigger phrasing would lift the weaker completeness and trigger-term dimensions.

Suggestions

Append an explicit 'Use when...' clause naming natural user phrases, e.g. 'Use when managing TanStack Table state in Angular with signals, controlling pagination/sorting state, or wiring table atoms to Angular Store or Query.'

Soften pure jargon with synonyms users actually say — 'Angular table state', 'controlled pagination signal', 'table atoms' — alongside the precise API terms.

Keep the existing capability list but lead with the 'when' so the trigger context is front-loaded for skill selection.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'Angular-signal-backed table.atoms', 'computed selectors', 'value-or-updater callbacks', 'external Angular Store atoms', 'injectTable initializer reruns' — giving comprehensive, mechanism-specific coverage of this skill's surface.

5 / 5

Completeness

The 'what' is clear (use these specific mechanisms), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3 with 'when' only weakly implied by 'while accounting for injectTable initializer reruns'.

3 / 5

Trigger Term Quality

The terms are almost exclusively technical jargon (e.g. 'value-or-updater callbacks', 'injectTable initializer reruns') rather than natural phrases a user would say; it lacks common variations or synonyms a developer would naturally utter when asking for help.

2 / 5

Distinctiveness Conflict Risk

It targets a narrow, well-defined niche — TanStack Angular table state via signals/atoms — with distinct triggers and minimal risk of firing for an unrelated skill.

5 / 5

Total

15

/

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.