Why Skillset
Explains why Skillset uses adaptive source to render honest provider-native agent loadouts.
Claude, Codex, and Cursor can all consume reusable agent guidance, but they do not share one file model or one capability set. Hand-maintaining a tree for each provider duplicates common intent, lets copies drift, and makes unsupported behavior easy to overlook.
Skillset gives a repository one authored source tree. It derives predictable details, validates the source contract, and renders each enabled target in that provider’s native shape. Authors can share a meaning when the providers genuinely share it and keep explicit provider-native configuration when they do not.
What Skillset optimizes for
- A smaller happy path. Authors describe information only they know; names, destinations, and compatible metadata are derived where possible.
- Honest portability. Near matches are modeled by intent. Missing or lossy destinations stay visible instead of becoming fake equivalence.
- Reviewable output. Generated files and lock provenance are deterministic, local to the repository, and suitable for ordinary code review.
- Early feedback. Schema errors, unsupported features, unsafe mappings, collisions, and drift appear before they become runtime surprises.
- Native results. Claude output looks like Claude, Codex output looks like Codex, and Cursor output looks like Cursor.
What Skillset does not do
Skillset is not a runtime manager or a universal agent-file format. It does not make every provider feature portable, hide target-specific tradeoffs, or treat generated output as source truth.
Skillset renders files. It does not install, trust, activate, symlink, or mutate user-level provider configuration. The build-versus-activation boundary keeps compilation reviewable and leaves runtime authority with the user and provider.
When it fits
Use Skillset when a repository needs reusable agent material across one or more providers, wants generated output committed or checked for drift, or needs a safe route for adopting existing provider-native work.
For a one-off file used by one provider, direct native authoring may be simpler. Skillset earns its place when derivation, validation, portability, or reproducibility removes more maintenance than the source layer adds.
Continue with the first-author journey or consult the feature support matrix for current provider evidence.