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.
59
67%
Does it follow best practices?
Impact
—
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 an excellent 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 for 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 | Highly distinctive with a clear niche focused specifically on React composition and architecture patterns. The specific mention of compound components, render props, boolean prop proliferation, and React 19 API changes makes it unlikely to conflict 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 primarily as a table of contents rather than a standalone instructional document. While it is well-organized with clear categorization and prioritization, it lacks any concrete code examples, executable patterns, or actionable guidance within the SKILL.md itself. The complete deferral of all substantive content to external rule files means Claude gains almost nothing actionable from reading this file alone.
Suggestions
Add at least one concrete before/after code example inline (e.g., showing boolean prop proliferation refactored to a compound component pattern) so the SKILL.md is actionable on its own.
Include a brief decision workflow: 'If you see X, apply pattern Y' with specific triggers and actions, rather than just listing rule names.
Add a minimal executable example for the highest-priority pattern (architecture-avoid-boolean-props) directly in the Quick Reference section so Claude can immediately apply the most impactful pattern without needing to read external files.
Remove or condense the 'When to Apply' section since it largely duplicates information already conveyed by the skill description and the rule category table.
| 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 columns adds structure but limited actionable value. | 2 / 3 |
Actionability | The skill provides no concrete code examples, no executable commands, and no specific patterns—it is entirely an index/catalog of rule names with brief descriptions. All actual guidance is deferred to external rule files, leaving the SKILL.md itself as a table of contents with no actionable content. | 1 / 3 |
Workflow Clarity | There is a clear prioritized sequence of categories and a 'How to Use' section directing to rule files, but there are no validation checkpoints, no decision trees for choosing patterns, and no workflow for actually applying these patterns during a refactoring task. | 2 / 3 |
Progressive Disclosure | The skill references external rule files and a compiled AGENTS.md, which is good progressive disclosure structure. However, since no bundle files are provided, we cannot verify these references exist. The SKILL.md itself is almost entirely an index with too little standalone content—it over-delegates without providing enough quick-start value inline. | 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
49eeda2
- 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.