A Skillset target is an enabled provider adapter selected for a compiler run. It receives provider-native output produced by a render, which a build can write. A runtime is a concrete application or harness that may consume that output. Adding a runtime does not add a target, and rendering provider output does not prove activation.
Use the feature support matrix for the exhaustive registry-owned view of feature status across every canonical target. The authored provider pages explain how to interpret those facts: native output shapes, important unsupported or provider-native boundaries, and the evidence behind current claims. Status terms are defined once in the feature-reference support vocabulary.
Providers
- Claude — Skillset support and provider-specific guidance for the
claudetarget. - Codex — Skillset support and provider-specific guidance for the
codextarget. - Cursor — Skillset support and provider-specific guidance for the
cursortarget.
Reading Provider Support
A support cell describes what Skillset can render for one feature and target. It does not prove that a runtime installed, trusted, discovered, or invoked the result. Open the linked feature page for authoring shape, diagnostics, qualifications, and evidence; open the provider page for target-level constraints that cut across features.
Provider evidence is checked into the repository so ordinary builds stay deterministic and offline. Maintainers refresh that evidence through the feature-registry provider evidence procedure.
The hosted provider-validation record lists exact external pins, the surfaces each validator actually covers, negative canaries, and the internal-conformance fallback for uncovered provider behavior.
Skillset renders files. It does not install, trust, activate, symlink, or mutate user-level provider configuration. See Build Versus Activation.