CtrlK
BlogDocsLog inGet started
Tessl Logo

column-sizing

Use columnSizingFeature numeric size, minSize, maxSize, getSize, getStart, getAfter, and total-size APIs in table, grid, or flex CSS. Load for auto or percentage misconceptions and sizing/pinning layout mismatch.

66

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a tight, well-structured reference with executable code and concrete wrong/correct patterns that assume Claude's competence. The main gap is that the offset APIs (getStart/getAfter) are named but not demonstrated, and API Discovery is a pointer rather than executable guidance.

DimensionReasoningScore

Conciseness

The body is lean throughout: a single orienting sentence ("Sizing is numeric state; translating it to layout is a renderer decision"), tight code blocks, and one-line Wrong/Correct pairs with no padding or over-explanation of concepts Claude already knows.

5 / 5

Actionability

Setup and Core Patterns give copy-paste-ready executable code, and the Common Mistakes pairs are concrete; minor gaps remain since getStart/getAfter only appear as names and API Discovery is a pointer rather than code.

4 / 5

Workflow Clarity

Setup -> apply getSize to cell width -> getTotalSize to table width -> apply consistently forms a clear single-purpose sequence with an implicit consistency checkpoint, though there is no explicit validation step (none is needed for this non-destructive sizing task).

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files and no need for external references, the body is well-organized into clearly signaled sections (Setup, Core Patterns, Common Mistakes, API Discovery), meeting the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

76%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 distinct, naming concrete APIs and a clear niche, and includes explicit trigger guidance. Its weakness is trigger-term naturalness: the when clause relies on jargon ("misconceptions", "sizing/pinning layout mismatch") rather than phrases users actually say.

Suggestions

Rewrite the trigger clause in user-natural language, e.g. "Use when debugging column width, percentage/auto sizing, or pinned-column offset mismatches in TanStack Table."

Add common synonyms and the library name in the trigger, e.g. mention "column width", "table grid", and "@tanstack/table-core" so users searching those terms match.

DimensionReasoningScore

Specificity

Lists many concrete API names ("numeric size, minSize, maxSize, getSize, getStart, getAfter, and total-size APIs") plus concrete CSS contexts ("table, grid, or flex CSS"), giving comprehensive coverage of specific capabilities.

5 / 5

Completeness

Answers both what ("Use columnSizingFeature ... APIs in table, grid, or flex CSS") and when ("Load for auto or percentage misconceptions and sizing/pinning layout mismatch"), with explicit trigger guidance, though the when clause is phrased unnaturally.

4 / 5

Trigger Term Quality

Relevant terms like "columnSizingFeature" and "table" are present, but the trigger phrasing is jargon-heavy ("auto or percentage misconceptions", "sizing/pinning layout mismatch") and missing natural synonyms a user would say.

3 / 5

Distinctiveness Conflict Risk

Targets a very narrow niche (TanStack table columnSizingFeature numeric sizing APIs) with distinct, specific triggers, minimizing conflict risk with other skills.

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.