Name: modular-ds-config-components
Rating: 67.2 (1 reviews)
Author: primer

modular-ds-config-components

Use when: building or evaluating a props-based, "all-in-one" Primer React component for an established, stable pattern. Covers when config components are appropriate, opinionated defaults, the props-driven customization surface, escape hatches to presentational components, and composing rather than duplicating behavior.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

73%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 content is exceptionally lean and well-structured, with strong progressive disclosure and a clear adoption checklist. Its weakness is actionability: the body is mostly policy ('must not', 'owns', 'escape hatches') rather than executable, copy-paste guidance for actually composing or testing a config component.

Suggestions

Add one concrete, runnable snippet showing the intended composition pattern (config component built from a named presentational component + behavior hook), not just the List usage example, to lift actionability toward copy-paste ready.

Tighten the 'Adoption surfaces' checklist into an explicit ordered workflow with a validation checkpoint (e.g., 'run matching export snapshot tests; fix before publishing the changeset') to close the feedback-loop gap.

Name the specific behavior hooks or slot mechanism entry points to call instead of referring abstractly to 'behavior hooks' and 'the slots skill', so 'build by composing' is executable rather than directional.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, covering only non-obvious Primer-specific decisions (config vs presentational, escape boundaries, data-component ownership, changeset policy) with no padding about what components or props are.	5 / 5
Actionability	Guidance is concrete in principle (a runnable List example, a named escape boundary, explicit changeset rules) but the 'must/must not' items are largely policy statements rather than copy-paste executable steps, and 'build by composing presentational components and behavior hooks' lacks the actual hooks/API to call.	3 / 5
Workflow Clarity	The 'Adoption surfaces' section gives a clear sequenced checklist of what a public API change must include (exports, tests, stories, docs metadata, changeset), with only minor validation/checkpoint gaps since it does not explicitly state verify-before-publish feedback loops.	4 / 5
Progressive Disclosure	The 52-line body is well-organized into clearly signaled sections and points one level deep to sibling skills (modular-ds-presentational-components), contributor-docs/style.md, and the slots skill; no bundle files exist to verify, but the inline/external split is appropriate with only minor organization gaps.	4 / 5
	Total	16 / 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.

The description is specific, trigger-rich, and explicitly pairs 'what' with a 'Use when' clause, sharply distinguishing config components from presentational ones. It is a strong, low-conflict trigger description with only minor synonym coverage gaps.

Dimension	Reasoning	Score
Specificity	The description names concrete actions ('building or evaluating a props-based, all-in-one Primer React component') and a specific scope ('opinionated defaults, props-driven customization surface, escape hatches, composing rather than duplicating'), giving several specific capabilities with only minor coverage gaps.	4 / 5
Completeness	It opens with 'Use when:' and immediately states the trigger conditions ('building or evaluating a props-based... component for an established, stable pattern'), then enumerates what the skill covers, explicitly answering both what and when with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms like 'config components', 'all-in-one component', 'opinionated defaults', 'escape hatches', and 'composing rather than duplicating' match what a contributor would say, with only a few common synonyms missing.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply scoped ('props-based, all-in-one Primer React component for an established, stable pattern') and explicitly contrasted with presentational components, yielding clear triggers with minimal overlap risk against sibling skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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: primer/react
Path: .github/skills/modular-ds-config-components/SKILL.md
Commit: 2909f19

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.