Skillset configuration is layered. Start with the narrowest layer that expresses the intent, then use a provider override only when the shared form cannot carry the same meaning.
| If you need to… | Start here |
|---|---|
| Select providers or configure project-wide compilation | Project configuration |
| Add metadata to a skill, agent, or rule | Frontmatter |
| Change one provider’s output or behavior | Target overrides |
| Express portable or provider-native tool intent | Tools policy |
How the Layers Relate
A Skillset workspace supplies project-wide settings. Defaults then flow through a cascade: workspace defaults, plugin defaults, source-unit fields, and finally provider-specific fields. A more specific layer should refine the shared intent rather than define a second copy of it.
For the files behind those layers, see the workspace layout, rule source, and preprocessing reference.
Exact Contracts and Inspection
The generated schemas and examples are the exhaustive field reference. Use skillset check to validate source, skillset lookup to inspect schema and compatibility facts, and skillset explain to trace how a source unit resolves for each provider.