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.

67

Quality

82%

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.

A tight, well-organized reference skill that delivers executable code and concrete wrong/correct pairs without padding. The only soft spot is the vague 'API Discovery' pointer, which undercuts full actionability.

Suggestions

Replace the vague 'API Discovery' pointer with one or two concrete snippets (e.g. the region-aware offset signature and the default values) so the skill is fully self-contained.

Optionally add a one-line validation/check step (e.g. assert getTotalSize() equals the summed rendered widths) to help catch sizing/pinning mismatches explicitly.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanations of concepts Claude already knows; every line is concrete code or a concrete mistake, assuming Claude's competence.

5 / 5

Actionability

Setup and Core Patterns give copy-paste-ready code and each Common Mistake pairs a concrete Wrong with a concrete Correct example, but the closing 'API Discovery' line ('Inspect node_modules/... for defaults and region-aware offset signatures') is a pointer rather than executable guidance.

4 / 5

Workflow Clarity

As a single-purpose reference skill the core action (apply numeric sizes to DOM CSS) is shown unambiguously via Core Patterns, but it is a pattern catalogue rather than a sequenced workflow, so there are no explicit checkpoints; the simple-skill exception keeps this from being penalized further.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and no bundle files present; the content is well-organized into clearly labeled sections (Setup, Core Patterns, Common Mistakes, API Discovery), meeting the simple-skill bar for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

78%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.

A specific, well-scoped description that names concrete APIs and trigger conditions tied to a single feature. It answers both what and when, with only minor room for more explicit 'Use when...' phrasing and additional synonyms.

Suggestions

Rephrase the trigger as an explicit 'Use when...' clause (e.g. 'Use when handling column auto/percentage sizing or pinned-column layout mismatches') to make the when unambiguous.

Add a few natural synonyms users might say, such as 'column width' or 'resized columns', alongside the existing API-centric terms.

DimensionReasoningScore

Specificity

Enumerates concrete APIs (size, minSize, maxSize, getSize, getStart, getAfter, total-size) and concrete contexts (table, grid, flex CSS) rather than vague language, but the two top-level actions ("Use ... APIs", "Load for ...") could enumerate a couple more use cases for full coverage.

4 / 5

Completeness

"Use ... APIs in table, grid, or flex CSS" states the what, and "Load for auto or percentage misconceptions and sizing/pinning layout mismatch" is equivalent explicit trigger guidance for the when; both are present but the when could be phrased more explicitly as a 'Use when...' clause.

4 / 5

Trigger Term Quality

Includes natural developer phrases ("auto or percentage misconceptions", "sizing/pinning layout mismatch", "columnSizingFeature") that a user would plausibly say, though a few common synonyms (e.g. "column width", "resized columns") are absent.

4 / 5

Distinctiveness Conflict Risk

Scoped to a single named feature (columnSizingFeature) with distinct triggers (column sizing/pinning layout mismatch), giving it a clear niche with minimal conflict risk against 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.