I review skills in the OSS codebases to identify the best practices that go into defining the skills that are used in a codebase. When I write about skills, I tend to keep it to the meta and overview of the sections defined.
---name: vercel-react-best-practicesdescription: React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.license: MITmetadata: author: vercel version: "1.0.0"---
The description defined the following things:
When this skill should be used:
should be used when writing, reviewing, or refactoring React/Next.js code
2. When this skill should be triggered:
Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements
Usually, you can expect the rest of skills document elaborating on description in metadata.
This skill is defined in web/.agents/skills and it has the following metadata:
---name: vercel-composition-patternsdescription: 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.license: MITmetadata: author: vercel version: '1.0.0'---
The description defined the following things:
When this skill should be used?
Use when refactoring components with boolean prop proliferation, etc., or
Building flexible component libraries or
Designing reusable APIs.
2. When this skill should be triggered?
Triggers on tasks involving compound components etc.,
Usually, you can expect the rest of skills document elaborating on description in metadata.