CtrlK
BlogDocsLog inGet started
Tessl Logo

with-tanstack-virtual

Virtualize Angular Table final row or column models inside the correct injection and reactive lifecycle with signal counts, scroll elements, keys, measurement, transforms, sticky regions, grid/flex sizing, and infinite data.

64

Quality

78%

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/with-tanstack-virtual/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 body is a tight, highly actionable reference that pairs executable Setup code with high-value Wrong/Correct mistake patterns, weakened only by two conceptual Core Patterns that lack full code and the absence of an explicit numbered workflow.

Suggestions

Add a short executable snippet for the 'Gate infinite fetches' pattern showing the fetch-if-more-and-not-active guard, since that pattern is currently prose-only.

Provide a concrete layout-contract template (scroll element + total-size spacer + translated item) as code rather than only describing it in 'Own the layout contract'.

Consider moving the dist/types and examples pointers in API Discovery into a short bulleted list with exact path patterns to make discovery more navigable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what Angular, signals, or virtualization are, and every Setup/Core Patterns/Common Mistakes section earns its tokens with concrete code or directly useful guidance.

5 / 5

Actionability

Setup and the Wrong/Correct mistake pairs are copy-paste executable, but the 'Gate infinite fetches' and 'Own the layout contract' patterns stay conceptual ('fetch only if more server rows exist...', 'translate or measure each virtual item') without complete code, leaving minor gaps.

4 / 5

Workflow Clarity

Content is logically organized as Setup → Core Patterns → Common Mistakes with a sensible implicit flow (derive models → own layout → gate fetches); virtualization is non-destructive so the missing-validation cap does not apply, though there is no explicit numbered workflow with checkpoints.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers and the API Discovery pointers are one level deep to installed package types, but the skill is slightly over the 50-line simple-skill threshold and the API Discovery section is a mild catch-all rather than a clean split into bundle references.

4 / 5

Total

17

/

20

Passed

Description

75%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 a comprehensive set of virtualization capabilities, but it omits any 'Use when...' trigger guidance, which caps completeness and slightly limits natural trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when virtualizing Angular Table rows or columns, implementing virtual/infinite scroll, or handling sticky headers with @tanstack/angular-table.'

Include user-natural synonyms such as 'virtual scroll', 'windowing', and 'infinite scroll' alongside the existing 'infinite data' phrasing to broaden trigger coverage.

Lead with the primary action ('Virtualize Angular Table rows and columns') before the long list of sub-concerns so the core capability reads first.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'Virtualize Angular Table final row or column models', 'signal counts, scroll elements, keys, measurement, transforms, sticky regions, grid/flex sizing, and infinite data' — giving comprehensive coverage rather than minor gaps.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good natural keywords ('Virtualize', 'Angular Table', 'infinite data', 'sticky regions') but the language leans technical and omits common synonyms a user might say such as 'virtual scroll', 'windowing', or 'infinite scroll'.

4 / 5

Distinctiveness Conflict Risk

'Virtualize Angular Table' carves a clear niche distinct from the sibling core/getting-started/table-state skills, with minimal risk of triggering for the wrong skill.

5 / 5

Total

17

/

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.