CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-organized overview that efficiently catalogs composition rules, but its progressive-disclosure references point to files that are not bundled with the skill, and the body itself lacks executable code examples.

Suggestions

Bundle the referenced rule files (e.g. rules/architecture-avoid-boolean-props.md, rules/state-context-interface.md) and AGENTS.md so the signaled references actually resolve, or inline a minimal code example per rule.

Add at least one short executable code snippet illustrating a core pattern (e.g. a compound-component structure) so the body is actionable without external files.

If rule files are intentionally omitted in this distribution, replace the dangling file references with self-contained inline summaries.

DimensionReasoningScore

Conciseness

Lean and efficient — no padding explaining basic React/conceptual knowledge; every line states a rule or navigation pointer, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Rule names and one-line directives are concrete but no executable code or specific examples appear inline ('use composition', 'Move state into provider components'), and full detail is deferred to absent files — matching 'some concrete guidance but incomplete'.

2 / 3

Workflow Clarity

A single-purpose reference catalog with an unambiguous structure (priority table, categorized quick reference, How to Use section); per the simple-skills note, clear single-task organization scores 3.

3 / 3

Progressive Disclosure

The overview correctly signals one-level-deep references to rules/*.md and AGENTS.md, but those bundle files do not exist alongside SKILL.md, breaking navigation — structurally organized yet references are non-resolvable.

2 / 3

Total

10

/

12

Passed

Description

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.

A strong, well-constructed description that concisely states concrete capabilities, includes natural trigger terms, explicitly covers both what and when, and is clearly distinguishable from other skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions: 'refactoring components with boolean prop proliferation', 'building flexible component libraries', 'designing reusable APIs' — not vague, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('React composition patterns that scale') and when via an explicit 'Use when...' clause plus 'Triggers on tasks involving...', matching the clear-both anchor.

3 / 3

Trigger Term Quality

Includes natural terms users would say — 'compound components', 'render props', 'context providers', 'component architecture', 'React 19' — with good coverage of variations, matching the top anchor.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (React composition patterns) with distinct triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
databricks/devhub
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.