CtrlK
BlogDocsLog inGet started
Tessl Logo

modular-ds-presentational-components

Use when: building or evaluating flexible, composable Primer React parts that consumers assemble directly, or deciding whether a pattern is ready to become a config component. Covers structure-first composition, pairing presentational components with behavior hooks, data-component attributes, sub-component export conventions, and when to promote a pattern up the spectrum.

65

Quality

78%

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 ./.github/skills/modular-ds-presentational-components/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body delivers specific, actionable Primer conventions with a logical topical flow and clearly signaled cross-references, assuming Claude's competence throughout. Its main weakness is verbosity — several explanatory passages could be trimmed without losing clarity.

Suggestions

Tighten the data-component section: condense the ComponentName.PartName vs flat-export divergence rationale into one sentence and move the ADR-023 edge-case detail to a reference, since the rule itself is already stated.

Trim qualifying hedges like "this is a default, not a prohibition" and "never on a new component, where it buys nothing and adds an RSC trap" into shorter imperative forms that preserve the rule.

Consider splitting the composition-rules list and the data-component conventions into a reference file so SKILL.md reads as a leaner overview, improving both conciseness and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence (references RSC, slots, ADRs without basics), but several passages — notably the data-component value/export divergence explanation and repeated qualifying clauses — are verbose and could be tightened, matching the mostly-efficient anchor.

3 / 5

Actionability

Provides concrete conventions (CSS Modules + tokens + clsx, data-component naming rules, flat export code block) and a real copy-relevant export example; the primary sample is explicitly flagged illustrative-only, leaving minor gaps.

4 / 5

Workflow Clarity

A clear topical progression runs from when-to-use through hooks, composition, data-component, exports, accessibility, to promotion; no destructive or batch operations are involved, so absent validation checkpoints are not penalized.

4 / 5

Progressive Disclosure

No bundle files exist, so the skill is a single well-sectioned file with clearly signaled one-level cross-skill references (modular-ds-utilities, the ADR-023 doc); good structure with minor organization gaps rather than a fully split overview.

4 / 5

Total

15

/

20

Passed

Description

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

The description is strong: it states a concrete capability set, gives an explicit "Use when:" trigger, and carves out a clear presentational-components niche. Minor overlap with sibling modular-ds skills and slightly jargon-bound trigger terms keep it just off the top of trigger and distinctiveness.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "structure-first composition, pairing presentational components with behavior hooks, data-component attributes, sub-component export conventions, and when to promote a pattern up the spectrum" — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both: an explicit "Use when:" trigger clause and a "Covers..." what clause with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural triggers for the Primer contributor audience ("building... composable Primer React parts", "deciding whether a pattern is ready to become a config component") are good but jargon-heavy with a few synonyms missing, fitting just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear presentational-tier niche but the "deciding whether a pattern is ready to become a config component" trigger overlaps with the sibling config-components skill, giving minor overlap risk rather than minimal.

4 / 5

Total

18

/

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.