row-pinning

Pin stable row IDs into top, center, and bottom collections with rowPinningFeature and keepPinnedRows. Load for filtering/pagination visibility, explicit region rendering, or renderer-owned sticky CSS.

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/table-core/skills/row-pinning/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 tight, executable, and well-structured, providing concrete setup code, region-rendering patterns, and high-value wrong/correct mistake guidance without explaining concepts Claude already knows. Its only gaps are mild redundancy in the opening line and reference-pattern organization rather than a strict sequenced workflow.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence (no padding about what tables are), with only minor trimmable lines such as the opening 'This skill builds on core and table-features' that repeats the frontmatter requires field.	4 / 5
Actionability	Copy-paste-ready setup and region-rendering code plus concrete wrong/correct pairs for two HIGH mistakes and explicit keepPinnedRows values fully cover the common cases.	5 / 5
Workflow Clarity	Organization is clear (Setup -> Core Patterns -> Common Mistakes -> visibility policy) and the single-purpose action is unambiguous, but it reads as a reference of patterns rather than a sequenced workflow with explicit checkpoints.	4 / 5
Progressive Disclosure	Well-organized section headers with clearly signaled inline 'Source:' references and a directed API Discovery path; no bundle files exist, so structure is self-contained with only minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

70%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, technical, and covers both what the skill does and when to load it, with mostly natural trigger terms. Its main weakness is that it frames a single pinning action rather than a comprehensive action list, and the 'when' is implicit-as-trigger rather than an explicit 'Use when' phrase.

Suggestions

Add an explicit 'Use when ...' clause (e.g. 'Use when pinning rows for sticky headers/footers or keeping rows visible across filtering and pagination') to raise completeness.

Broaden the action list beyond a single pinning action to include region rendering and the visibility-policy toggle for fuller coverage.

Add common synonyms users say ('freeze rows', 'lock rows', 'sticky rows') to improve trigger-term recall.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete API surface ('Pin stable row IDs into top, center, and bottom collections with rowPinningFeature and keepPinnedRows') but describes essentially one action rather than a comprehensive set, matching the 1-2-concrete-actions anchor.	3 / 5
Completeness	Provides a clear 'what' (pin row IDs into regions) and an equivalent trigger clause ('Load for filtering/pagination visibility, explicit region rendering, or renderer-owned sticky CSS'), though the 'when' is phrased as 'Load for' rather than an explicit 'Use when'.	4 / 5
Trigger Term Quality	Good natural keyword coverage ('row pinning', 'pinned rows', 'sticky CSS', 'filtering/pagination visibility') that users would plausibly say, with a few common synonyms (e.g. 'freeze rows', 'lock rows') missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche (TanStack row pinning with named APIs) with minimal conflict risk, but 'sticky CSS' and the broader table-features family create minor overlap with closely related skills.	4 / 5
	Total	15 / 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/table-core/skills/row-pinning/SKILL.md
Commit: d01c01b

Reviewed: 1 day 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.