CtrlK
BlogDocsLog inGet started
Tessl Logo

positron-data-grid-pattern

Use when building a list, table, grid, or virtualized scrolling UI in Positron, or touching `DataGridInstance` / `PositronDataGrid`. Avoids the common mistake of mediating props into the instance via useEffect.

63

Quality

74%

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 ./.claude/skills/positron-data-grid-pattern/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, lean design-pattern skill with executable code, a clear core pattern, an explicit anti-pattern section, and a checklist. Slight redundancy and the lack of a complete fetchData code example are the only gaps keeping it from top marks.

DimensionReasoningScore

Conciseness

Lean content that assumes Claude's competence (no explaining of React/useEffect) with executable code; minor redundancy between the 'pattern' and 'two data strategies' sections keeps it just below a 5.

4 / 5

Actionability

Provides copy-paste-ready TSX for the core 5-step pattern and names concrete subclasses; the fetchData strategy is described rather than shown as a complete executable example, leaving a minor gap.

4 / 5

Workflow Clarity

A clearly numbered 5-step pattern plus a quick checklist provide a sound sequence and checkpoint; no explicit validate-fix-retry loop, though the design-pattern nature does not demand one.

4 / 5

Progressive Disclosure

Well-organized with clear section headers, a single-level reference list of subclasses to skim, and easy navigation; no bundle files exist, so the monolithic-but-appropriately-split structure fits one level below a 5.

4 / 5

Total

16

/

20

Passed

Description

73%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 focused, well-triggered description with strong distinctiveness and a clear 'Use when' clause. Its main weakness is that the 'what' is expressed as an anti-pattern avoidance rather than a comprehensive list of concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and concrete entities (`DataGridInstance`, `PositronDataGrid`, list/table/grid UI) plus the specific prop-mediation anti-pattern, but frames capability as a single avoidance behavior rather than enumerating multiple discrete actions.

3 / 5

Completeness

Explicitly answers 'when' with concrete trigger phrases and answers 'what' via the anti-pattern avoidance, but the 'what' is framed indirectly (what to avoid) rather than a constructive capability statement.

4 / 5

Trigger Term Quality

Includes natural trigger terms a user would say ('building a list, table, grid, or virtualized scrolling UI') with synonyms and the explicit 'Use when' clause; a few broader synonyms are absent but coverage is strong.

4 / 5

Distinctiveness Conflict Risk

Highly specific to Positron's grid system with named classes and a niche trigger, making conflict with unrelated skills very unlikely.

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
posit-dev/positron
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.