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.

88

1.19x
Quality

82%

Does it follow best practices?

Impact

100%

1.19x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is vercel-composition-patterns in vercel-labs/agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A well-organized overview with a sound index structure (priority table, categorized quick reference, how-to-use), but it defers all executable code examples and detailed rules to bundle files that are missing, which weakens actionability and leaves progressive disclosure unfulfilled.

Suggestions

Include at least one small executable before/after code example in the body (e.g., for architecture-avoid-boolean-props) so the skill remains actionable even when the rule files are absent.

Provide the referenced bundle files (rules/*.md and AGENTS.md) or remove the references — currently they point to non-existent files, breaking progressive disclosure.

Expand 'How to Use' into a short sequenced checklist (locate the matching rule category by priority -> read the rule file -> apply the corrected pattern -> verify the result) to give a clearer workflow path.

DimensionReasoningScore

Conciseness

Lean index-style body that assumes React competence and avoids explaining basics Claude already knows; the only padding is the benefit sentence 'make codebases easier for both humans and AI agents to work with as they scale,' which is minor.

3 / 3

Actionability

Rule directives are concrete ('Don't add boolean props to customize behavior; use composition,' 'Use children for composition instead of renderX props') but the body contains no executable code, and the promised code examples are deferred to rule files that are not present — key details are missing.

2 / 3

Workflow Clarity

There is no real multi-step workflow (it is a pattern reference), and 'How to Use' offers only a loose single-step hint ('Read individual rule files for detailed explanations and code examples') with no sequencing or checkpoints; the simple-skill exemption does not apply since this is a multi-rule catalog over 50 lines.

2 / 3

Progressive Disclosure

The overview is well-structured with clearly signaled one-level references ('rules/architecture-avoid-boolean-props.md,' 'AGENTS.md'), but those referenced files do not exist in the bundle, so the disclosure structure is claimed but not actually realized — navigation leads to missing files.

2 / 3

Total

9

/

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, specific, third-person description with explicit trigger clauses and a clearly bounded React composition niche. The only minor weak spot is the mildly abstract/buzzwordy lead phrase 'patterns that scale,' which does not pull any dimension below 3.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'refactoring components with boolean prop proliferation,' 'building flexible component libraries,' and 'designing reusable APIs' — matching the score-3 anchor's pattern of distinct concrete actions rather than the generic score-2 example; not vague.

3 / 3

Completeness

Clearly states what ('React composition patterns that scale') and gives explicit when guidance via both 'Use when...' and 'Triggers on...' clauses, satisfying both halves of the score-3 anchor.

3 / 3

Trigger Term Quality

Uses natural React terms a developer would actually say — 'compound components,' 'render props,' 'context providers,' 'boolean prop proliferation,' 'component architecture' — giving good coverage rather than generic jargon.

3 / 3

Distinctiveness Conflict Risk

Niche is clearly scoped to React composition patterns with distinct triggers (compound components, render props, context providers), making it unlikely to fire for unrelated skills; written in third person with no voice penalty.

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
Draculabo/AntigravityManager
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.