CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/vercel-composition-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%Weight 40%Scale 1-5

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

The body is a clean, concise index with sensible priorities, but it is an index to a library that is not shipped: both the per-rule files and the AGENTS.md full document referenced throughout are absent from the bundle, leaving dead links where the substance should be. As delivered, the skill provides only one-line rule summaries with no executable examples or detailed guidance.

Suggestions

Ship the referenced detail files or inline their substance: every path the body points to (rules/architecture-avoid-boolean-props.md, rules/state-context-interface.md, and AGENTS.md) is missing from the bundle, so the progressive-disclosure structure is entirely broken.

Add a minimal code snippet for each HIGH-priority rule (or at least architecture-avoid-boolean-props and architecture-compound-components) inside SKILL.md so the guidance is actionable even without the rule files.

Trim token cost by removing the repository-root AGENTS.md/AGENT_GUIDE.md disclaimer and merging the 'Rule Categories by Priority' table into the Quick Reference sections, which currently duplicate the same category list.

DimensionReasoningScore

Conciseness

The body is mostly a lean catalog of one-line rules with no explanation of concepts Claude already knows, fitting 'efficient; minor instances of over-explanation that could be trimmed'. It is not a 5 because of redundancy: the priority table repeats the categories re-listed in Quick Reference, 'When to Apply' duplicates the frontmatter description, and the four-line AGENTS.md disclaimer about repository-root files is meta-noise that earns no tokens.

4 / 5

Actionability

The one-line rules are concrete directives ('Don't add boolean props to customize behavior; use composition', 'Don't use forwardRef; use use() instead of useContext()'), but there is no code, no worked example, and the promised detail ('Read individual rule files for detailed explanations and code examples') points at files that do not exist in the bundle — so guidance is present but incomplete with key details missing, matching the 3 anchor. It is not a 4/5 because nothing in the body is executable as-is, and not a 2 because the one-liners are specific principles rather than vague hints.

3 / 5

Workflow Clarity

This is a reference-catalog skill with no multi-step process or destructive/batch operations, so no validation checkpoints are required. Usage is unambiguous for this genre: a priority table tells the agent which categories matter most, and 'How to Use' gives one clear navigation action (read the relevant rule file). It falls short of 5 because the skill exceeds a simple single-action scope yet offers no guidance on how to select or apply rules during a real task (e.g., during a refactor or review), and the instruction to read rule files cannot actually be followed.

4 / 5

Progressive Disclosure

The body is designed as an overview with well-signaled, one-level-deep references (rules/*.md and AGENTS.md), but scoring against the actual bundle structure shows none of the referenced files exist — there is no AGENTS.md and no rules/ directory. Every navigation path out of SKILL.md is broken, so the progressive-disclosure structure does not exist in practice ('minimal structure; references are buried' in the sense of being dead). It is not a 3 because that anchor assumes working references that are merely poorly signaled, and not a 1 because the in-body overview itself is well organized and the intended split is one level deep.

2 / 5

Total

13

/

20

Passed

Description

78%Weight 40%Scale 1-5

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 description with an explicit and well-phrased 'Use when'/'Triggers on' clause, rich domain-specific trigger vocabulary, and a clearly delineated React composition niche. Its only weakness is that the 'what' leans on an abstract tagline ('React composition patterns that scale') rather than enumerating concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain ('React composition patterns') and several specific areas of coverage — 'refactoring components with boolean prop proliferation', 'compound components, render props, context providers', and 'React 19 API changes' — which matches the anchor 'lists several specific actions; minor gaps in coverage'. It is not a 5 because it describes coverage areas rather than concrete performed actions, and the tagline 'that scale' adds no specific capability.

4 / 5

Completeness

Both 'what' and 'when' are present: the 'what' is 'React composition patterns... Includes React 19 API changes' and the 'when' is explicit with concrete triggers ('Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving...'). It falls just short of the 5 anchor because the 'what' is stated as a somewhat abstract tagline ('patterns that scale') rather than concrete capabilities, matching the 4 anchor 'when' could be more explicit or specific is met but the 'what' could be sharper.

4 / 5

Trigger Term Quality

Strong natural vocabulary users would actually say: 'boolean prop proliferation', 'compound components', 'render props', 'context providers', 'building flexible component libraries', 'designing reusable APIs'. This fits 'good keyword coverage; a few natural terms missing' — notable omissions include 'prop drilling', 'component API design', and 'children composition', and there are no file-extension-style synonyms, so the comprehensive-with-synonyms anchor (5) is not fully met.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (React component architecture/composition) with distinctive triggers like 'boolean prop proliferation', 'compound components', and 'render props' that are unlikely to fire for unrelated skills — matching 'clear niche with distinct triggers; minimal conflict risk'. The only mild overlap is with generic React coding-guideline skills, but the specialized vocabulary keeps conflict risk minimal.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

calesthio/OpenMontage

Path

.agents/skills/vercel-composition-patterns/SKILL.md

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.