CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-data-testid

Add stable `data-testid` attributes when a new or refactored UI flow needs reliable unit or E2E selectors. Use for interactive React/TSX views, menus, or test-driven UI work; do not add selectors to static markup without a test or automation need.

Quality

83%

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

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.

Highly actionable content with executable examples, a concrete naming scheme, and a clear sequenced workflow capped by explicit done criteria. The main weakness is redundancy: the repeated-row scoping rules are restated across four sections, which inflates token cost without adding guidance.

Suggestions

Consolidate the repeated-row guidance (Workflow steps 5-7, the checklist bullet, Playbook item 2, and the Stability Rules bullets) into a single 'Repeated rows' section; the same shared-id-plus-within(row) rule is currently stated four times.

Promote verification into the Workflow itself (e.g., a final step to grep the diff for removed `data-testid` before declaring done) instead of leaving all validation in the trailing Done Criteria section.

Replace the hedged step 9 ('where feasible') with a concrete condition for when Vitest/RTL tests must be added versus when they may be skipped.

DimensionReasoningScore

Conciseness

The body avoids explaining basics Claude already knows, but the repeated-row scoping rule (shared row id plus `within(row)` scope, shared child ids) is stated four times across Workflow steps 5-7, the Minimum Coverage Checklist, Scenario Playbook item 2, and Stability Rules, so it could be meaningfully tightened. It is not score 2 because each repetition adds slight nuance and there is no concept padding.

3 / 5

Actionability

Fully executable guidance: a concrete naming format (`<scope>-<entity>-<action>`), a stable-suffix vocabulary, three copy-paste-ready TSX examples covering the common cases (component markup, repeated list rows with row-scoped Playwright queries, config-driven menu forwarding), explicit query priorities, and a per-scenario playbook.

5 / 5

Workflow Clarity

The 9-step Workflow is clearly sequenced (scope prefix, root, interactive nodes, config forwarding, rows, tests) and the Done Criteria plus Minimum Coverage Checklist provide end-state verification, matching 'clear sequence with most checkpoints present'. It is not 5 because validation appears only at the end rather than as inline checkpoints and step 9 is hedged ('where feasible').

4 / 5

Progressive Disclosure

The single-file skill is well-sectioned with clear headers and no nested or buried references, giving good structure and easy navigation. It is not 5 because at ~135 lines with four sections restating row-scoping guidance, some content (e.g., the Scenario Playbook or Patterns) could be consolidated or split out, leaving minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

82%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: third-person, concise, with an explicit 'Use for...' trigger clause and a negative boundary that reduces conflict risk. Its only weaknesses are single-action specificity and a few missing natural synonyms (e.g., Testing Library, Playwright).

DimensionReasoningScore

Specificity

The description names one concrete action — "Add stable `data-testid` attributes" — with detailed conditions, but does not list several distinct actions, matching the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

It explicitly answers both what ("Add stable `data-testid` attributes") and when ("Use for interactive React/TSX views, menus, or test-driven UI work") with concrete trigger phrases, and adds a negative boundary ("do not add selectors to static markup"), matching the top anchor; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("data-testid", "unit or E2E selectors", "React/TSX views", "menus", "refactored") that users would plausibly say, but common synonyms like "Testing Library", "Playwright", or "test id" are missing, so it falls just short of comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (test-id attributes for UI test selectors) with distinct triggers and an explicit exclusion clause for static markup; the broad phrase "test-driven UI work" creates only minor overlap with general test-writing skills, which the boundary clause offsets.

5 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dtyq/magic

Path

frontend/magic-web/.agents/skills/ui-data-testid/SKILL.md

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.