react-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture.
79
67%
Does it follow best practices?
Impact
99%
1.43xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/react-composition-patterns/skills/react-composition-patterns/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly defines its niche in React composition patterns. It excels at providing both concrete actions and explicit trigger conditions, using natural developer terminology. The description is concise yet comprehensive, making it easy for Claude to distinguish this skill from general React development skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and patterns: 'refactoring components with boolean prop proliferation', 'building flexible component libraries', 'designing reusable APIs', and names specific patterns like 'compound components, render props, context providers'. | 3 / 3 |
Completeness | Clearly answers both what ('React composition patterns that scale') and when ('Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs') with explicit trigger guidance ('Triggers on tasks involving compound components, render props, context providers, or component architecture'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'refactoring components', 'boolean prop proliferation', 'component libraries', 'compound components', 'render props', 'context providers', 'component architecture'. These are terms React developers naturally use when facing these problems. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche focused specifically on React composition and component architecture patterns. The specific triggers like 'boolean prop proliferation', 'compound components', 'render props' are distinct enough to avoid conflicting with general React skills or other frontend skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions as an index/table of contents rather than a standalone skill document. It provides no concrete code examples, no executable patterns, and no actionable guidance—everything is deferred to external rule files that aren't included in the bundle. While the organization and categorization are reasonable, the skill body itself delivers almost no value without the supporting files.
Suggestions
Add at least one concrete before/after code example for the highest-priority pattern (architecture-avoid-boolean-props) directly in the SKILL.md so it provides standalone value.
Include a brief decision workflow: 'When you see X, apply pattern Y' with specific code-level indicators (e.g., 'If a component has 3+ boolean props controlling rendering, refactor to compound components').
Provide a minimal executable example of the compound component pattern with context provider, showing the complete pattern rather than just naming it.
Remove the priority table prefixes column and 'When to Apply' section (which restates the description) to save tokens for actual actionable content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary framing (e.g., 'These patterns make codebases easier for both humans and AI agents to work with as they scale') and the priority table with prefixes adds structure without much actionable value. The 'When to Apply' section largely restates the skill description. | 2 / 3 |
Actionability | The skill provides no concrete code examples, no executable patterns, and no specific implementation guidance. It is entirely a catalog/index of rule names with vague one-line descriptions, deferring all actual content to external rule files that are not provided. | 1 / 3 |
Workflow Clarity | There is a clear priority ordering and categorization of rules, and the 'How to Use' section explains how to navigate the rule files. However, there are no workflow steps for actually applying these patterns during refactoring, no validation checkpoints, and no decision tree for choosing between patterns. | 2 / 3 |
Progressive Disclosure | The skill attempts progressive disclosure by referencing individual rule files and a compiled AGENTS.md, with one-level-deep references. However, no bundle files are provided, so the referenced paths (rules/*.md, AGENTS.md) cannot be verified, and the SKILL.md itself contains almost no standalone useful content—it's essentially just a table of contents with nothing actionable at the top level. | 2 / 3 |
Total | 7 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
5e92b71
- 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.