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.

1.19x
Quality

73%

Does it follow best practices?

Impact

100%

1.19x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/cloud-profile/skills/vercel-composition-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

A clean, well-organized index that respects token budget and assumes reader competence, but it currently functions as a table of contents for files missing from the bundle. Without the rule files, the skill delivers only one-line directives with no code examples, limiting its standalone actionability.

Suggestions

Ship the referenced bundle: create the rules/ files for all nine listed rule IDs (only two paths are shown) and the AGENTS.md compiled document, or inline the highest-priority rules so the skill works standalone.

Add one short incorrect/correct code pair for the top-priority rule (architecture-avoid-boolean-props) directly in SKILL.md so concrete guidance survives even when rule files are not loaded.

List a file path for every rule in the Quick Reference rather than only two, and split the crammed React 19 line ("Don't use forwardRef; use use() instead of useContext()") into two distinct rules since it merges unrelated guidance.

DimensionReasoningScore

Conciseness

The ~75-line body is a lean index that assumes React competence and never explains known concepts (no 'what is a compound component' padding). Minor trim candidates remain: the 'When to Apply' list duplicates the description's triggers almost verbatim, and "These patterns make codebases easier for both humans and AI agents to work with as they scale" is motivational padding — anchor 4, not 5.

4 / 5

Actionability

Each rule carries a concrete one-line directive ("Don't add boolean props to customize behavior; use composition", "Move state into provider components for sibling access"), but the body contains no code examples — all executable detail is deferred to rules/*.md files ("Read individual rule files for detailed explanations and code examples") that are absent from the bundle, leaving key details missing. This matches anchor 3 ('some concrete guidance but incomplete') rather than 4.

3 / 5

Workflow Clarity

The lookup flow is clear and coherently sequenced: a priority table routes to category sections, each rule names its file prefix, and 'How to Use' explains exactly what each rule file contains (why / incorrect / correct / context). It is a reference skill with no destructive or batch operations, so validation checkpoints don't apply, but there is no explicit decision flow for matching a task to rules, keeping it below 5.

4 / 5

Progressive Disclosure

The overview shape is right — a compact index with well-signaled one-level-deep pointers ("rules/architecture-avoid-boolean-props.md", "AGENTS.md") — but none of the referenced files exist in the bundle (no rules/ directory and no AGENTS.md are present), so every reference dead-ends. Scored against the actual bundle structure, navigation is broken, which exceeds the 'minor organization gaps' allowed at anchor 4 and lands at anchor 3.

3 / 5

Total

14

/

20

Passed

Description

70%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 well-targeted, third-person description with explicit, doubly-stated trigger guidance and natural React vocabulary. Its main weakness is that the capability statement is a topic label ("React composition patterns that scale") rather than a list of concrete actions, leaving the 'what' side thinner than the 'when' side.

Suggestions

Replace the label-style opening with concrete capabilities, e.g. 'Apply compound-component, context, and explicit-variant patterns to refactor boolean-prop-driven components', so the description states what the skill does rather than only its topic.

Trim the fluff phrase 'that scale' and add common trigger synonyms such as 'prop drilling' or 'component design' to broaden natural-term coverage.

DimensionReasoningScore

Specificity

The 'what' is a topic label — "React composition patterns that scale" — with no capability verbs, while concrete activities appear only in the when-clause ("refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs"). The domain is named with some concrete specifics, but the capability side is not comprehensive, matching anchor 3 rather than 4.

3 / 5

Completeness

Both parts are explicitly present: what ("React composition patterns that scale") and a doubly-stated when ("Use when refactoring components..." / "Triggers on tasks involving compound components, render props, context providers, or component architecture"). The 'what' reads as a subject label with mild fluff ("that scale") rather than concrete capabilities, keeping it below anchor 5.

4 / 5

Trigger Term Quality

"compound components", "render props", "context providers", and "boolean prop proliferation" are natural phrases React developers actually say, giving good keyword coverage. Common synonyms such as "prop drilling" or "component design" are missing, so it falls short of anchor 5's comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to React ("React composition patterns", "render props", "React 19 API changes") with mostly distinct triggers and low conflict risk. Broad triggers like "component architecture" and "designing reusable APIs" create minor overlap with general React style-guide or API-design skills, fitting anchor 4 rather than 5.

4 / 5

Total

15

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

BigSimmo/PsychSift

Path

.claude/cloud-profile/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.