CtrlK
BlogDocsLog inGet started
Tessl Logo

slots

Use when: building, modifying, or wrapping compound components that use child-component "slots" in Primer React. Covers when to add a `__SLOT__` marker, the `useSlots` hook, the `isSlot` helper, the `asSlot` wrapper helper, naming conventions for slot symbols, and common pitfalls.

72

Quality

89%

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 well-structured, executable skill body: concrete code for every primitive, a useful conventions table, explicit pitfalls, and a closing checklist. The only slack is minor verbosity in a couple of explanatory paragraphs.

Suggestions

Tighten the 'Don't call useSlots inside useMemo/useCallback/...' paragraph — the lint-rule rationale could be one sentence instead of several.

The matcher-styles prose could be trimmed; the code block plus the single-match note already convey the behavior.

Consider collapsing the two example blocks in the asSlot section (old vs new) into a single 'old → new' contrast to save tokens.

DimensionReasoningScore

Conciseness

Largely lean and assumes Claude's React/TS knowledge — e.g. 'The Symbol description shows up in React DevTools and crash logs' earns its place — but a few passages (notably the useSlots-inside-hooks paragraph and some prose around matcher styles) could be tightened; not a 5 due to these minor over-explanations, and not a 3 because the bulk is efficient.

4 / 5

Actionability

Provides fully executable, copy-paste-ready code blocks for all four primitives (useSlots, __SLOT__ marker, asSlot, isSlot), shows both matcher styles, and a conventions table with concrete examples covering the common cases.

5 / 5

Workflow Clarity

Clear sequencing across consumer → sub-component → wrapping flows, supported by a 'when to use / not use' framing and an end-of-doc checklist; this is not a destructive or batch operation so the validation cap does not apply. Not a 5 because there is no explicit validate→fix→retry checkpoint, though the skill's nature does not strictly demand one.

4 / 5

Progressive Disclosure

No bundle files exist; content is self-contained in a single well-organized SKILL.md (~200 lines) with clear section headers (TL;DR, Architecture, per-primitive sections, Limitations, Checklist). Per the simple-skill guidance, a well-organized single-file skill scores 5 here.

5 / 5

Total

18

/

20

Passed

Description

92%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, concrete description with an explicit 'Use when' trigger and comprehensive coverage of the slot API surface. Its only weakness is a slight over-reliance on internal API names over the natural phrasings a user would say.

DimensionReasoningScore

Specificity

Names the domain (Primer React slots) and lists multiple concrete capabilities — building/modifying/wrapping compound components, the __SLOT__ marker, useSlots, isSlot, asSlot, naming conventions, and pitfalls — giving comprehensive coverage of the API surface.

5 / 5

Completeness

Explicitly answers both 'what' (covers the slot primitives and conventions) and 'when' via a concrete 'Use when:' clause with specific trigger conditions; not below 5 because both halves are clearly present, and not a 4 because the when-guidance is concrete rather than weakly implied.

5 / 5

Trigger Term Quality

Includes natural phrases a user might say ('compound components', 'slots', 'wrapping', 'Primer React') but leans heavily on technical jargon (__SLOT__ marker, useSlots, isSlot, asSlot) and omits common synonyms; a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Primer React's slot system) with distinct triggers; the 'Primer React' + 'compound component slots' framing makes it very unlikely to fire for an unrelated skill.

5 / 5

Total

19

/

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
primer/react
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.