CtrlK
BlogDocsLog inGet started
Tessl Logo

column-visibility

Hide columns with columnVisibilityFeature while rendering visibility-aware header, column, and cell collections. Load when hidden columns remain in the DOM, false-versus-absent state is confused, or enableHiding is misunderstood.

70

Quality

86%

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-structured reference skill with executable code and high-value Wrong/Correct patterns. Core Patterns snippets could be made fully self-contained to push actionability to the top anchor.

Suggestions

Make the Core Patterns code self-contained by showing how `table` is obtained, so the snippets are copy-paste executable rather than illustrative fragments.

Add a one-line note in API Discovery clarifying that visibility-aware vs all-column API names can be confirmed by listing the feature directory, turning the pointer into an explicit verification step.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no padding about what TanStack Table is, just executable setup, API patterns, and concise Wrong/Correct pairs where every line earns its place.

5 / 5

Actionability

Setup code is copy-paste ready and Common Mistakes give concrete Wrong/Correct snippets, but Core Patterns are illustrative fragments referencing an undefined `table` variable, leaving minor gaps versus fully executable guidance.

4 / 5

Workflow Clarity

The guidance is clearly organized (setup state, use visible APIs to render, all-column APIs for controls, avoid three named mistakes) with a clear sequence, but it is a patterns reference rather than a checkpointed multi-step workflow, so it sits just below the top anchor.

4 / 5

Progressive Disclosure

The body is under 50 lines with no external bundle files needed and is well-organized into clearly signaled sections (Setup, Core Patterns, Common Mistakes, API Discovery), meeting the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong description that clearly states both capability and load triggers in third person with concrete, distinct terms. Minor room to broaden trigger synonyms and action coverage for a perfect score.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Hide columns with columnVisibilityFeature', 'rendering visibility-aware header, column, and cell collections'), but coverage is not fully comprehensive across all column-visibility operations, so it sits just below the top anchor.

4 / 5

Completeness

It explicitly answers both 'what' (hide columns with columnVisibilityFeature, render visibility-aware collections) and 'when' (Load when hidden columns remain in the DOM, false-versus-absent is confused, or enableHiding is misunderstood) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural developer-facing triggers like 'hidden columns remain in the DOM', 'false-versus-absent state is confused', and 'enableHiding is misunderstood' are good and realistic, but a few common synonyms or phrasings are missing, keeping it just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly scoped to columnVisibilityFeature and visibility-aware APIs with distinct triggers (false-vs-absent, enableHiding), giving it minimal conflict risk with other skills.

5 / 5

Total

18

/

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.