vercel-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. Includes React 19 API changes.
74
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/vercel-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 strong skill description that clearly defines its scope around React composition patterns with specific, actionable trigger terms. It uses proper third-person voice, includes both 'Use when' and 'Triggers on' clauses, and names concrete patterns and scenarios that make it highly distinguishable from other React-related skills. The description is concise yet comprehensive.
| 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, component architecture'. Also mentions 'React 19 API changes'. | 3 / 3 |
Completeness | Clearly answers both 'what' (React composition patterns that scale, including compound components, render props, context providers, React 19 API changes) and 'when' (explicit 'Use when' clause covering refactoring, building libraries, designing APIs, plus a 'Triggers on' clause listing specific pattern types). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'refactoring components', 'boolean prop proliferation', 'component libraries', 'reusable APIs', 'compound components', 'render props', 'context providers', 'component architecture', 'React 19'. These cover a good range of terms a developer would naturally use when seeking help with React composition patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Carves out a clear niche focused specifically on React composition and architecture patterns, distinct from general React development, styling, testing, or state management skills. The specific mention of compound components, render props, boolean prop proliferation, and React 19 API changes makes it unlikely to conflict with other 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 primarily as a table of contents rather than a standalone instructional document. While it is well-organized with clear categorization and priority levels, it contains zero executable code examples and defers all actionable content to external rule files that are not provided in the bundle. The skill would benefit significantly from including at least one concrete before/after code example demonstrating the core pattern (e.g., boolean prop proliferation → compound component refactor).
Suggestions
Add at least one concrete before/after code example in the body showing the primary pattern (e.g., refactoring boolean props into compound components) so the skill is actionable without reading external files.
Include a brief step-by-step workflow for the most common use case (e.g., 'Refactoring a component with boolean prop proliferation') with specific steps and validation criteria.
Add a minimal executable example for the React 19 API changes (e.g., showing the old forwardRef pattern vs. the new approach) since this is time-sensitive information that benefits from inline examples.
Trim the 'When to Apply' section which largely duplicates the skill description, and use that space for actionable content instead.
| 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 'When to Apply' section largely restates the description. The priority table with 'Prefix' column adds structure overhead without clear payoff in the body itself. | 2 / 3 |
Actionability | The skill provides no concrete code examples, no executable commands, and no specific implementation guidance. It is entirely a table of contents pointing to external rule files. Claude would not know what to actually do from this content alone—every actionable detail is deferred to referenced files that are not provided. | 1 / 3 |
Workflow Clarity | There is a clear priority ordering and categorization of rules, which provides some workflow structure. However, there are no step-by-step processes for refactoring, no validation checkpoints, and no guidance on how to sequence applying these patterns when refactoring a component. | 2 / 3 |
Progressive Disclosure | The skill attempts progressive disclosure by referencing individual rule files and a compiled AGENTS.md, which is a good structure. However, since no bundle files are provided, we cannot verify these references exist. More importantly, the SKILL.md itself contains almost no substantive content—it's nearly all navigation with no quick-start content or minimal examples to be useful standalone. | 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
- databricks/devhub
- Commit
6338825
- 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.