presets-vs-kits Skill
Use when writing or reviewing code that must work in both CMake Presets and Kits/Variants modes. Covers configure, build, test, environment, and generator paths. Triggers: "presets vs kits", "useCMakePresets", "works in both modes". Published by microsoft in vscode-cmake-tools.
Decision snapshot
Is this a fit?
Testing, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is presets-vs-kits Skill?
Use when writing or reviewing code that must work in both CMake Presets and Kits/Variants modes. Covers configure, build, test, environment, and generator paths. Triggers: "presets vs kits", "useCMakePresets", "works in both modes". Published by microsoft in vscode-cmake-tools. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Writing
- Testing use cases
- Writing use cases
Declared skill metadata
- Source file: .github/skills/presets-vs-kits/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use presets-vs-kits Skill
- Use it for testing.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-cmake-tools
- Skill file: .github/skills/presets-vs-kits/SKILL.md
What it does
Use when writing or reviewing code that must work in both CMake Presets and Kits/Variants modes. Covers configure, build, test, environment, and generator paths. Triggers: "presets vs kits", "useCMakePresets", "works in both modes".
Skill instructions
Presets Mode vs Kits/Variants Mode Guide for writing code that works correctly in both operating modes of CMake Tools. Any shared code path (configure, build, test, environment, targets) must handle both modes. --- The two modes CMake Tools operates in one of two mutually exclusive modes per project folder: | | Presets mode | Kits/variants mode | |---|---|---| | Source of truth | CMakePresets.json / CMakeUserPresets.json | Kit selection + variant settings | | When active | cmake.useCMakePresets is 'always', or 'auto' and preset files exist | cmake.useCMakePresets is 'never', or 'auto' and no preset files exist | | Runtime check | CMakeProject.useCMakePresets === true | CMakeProject.useCMakePresets === false | How the mode is determined typescript // src/config.ts export type UseCMakePresets = 'always' | 'never' | 'auto'; // src/cmakeProject.ts — doUseCMakePresetsChange() const usingCMakePresets = useCMakePresets === 'always' ? true : useCMakePresets === 'never' ? false : await this.has
Verified compatibility and discovery
Frequently asked questions
What is presets-vs-kits?
presets-vs-kits is a open-source AI agent skill with Copy skill directory. Use when writing or reviewing code that must work in both CMake Presets and Kits/Variants modes. Covers configure, build, test, environment, and generator paths.
Who is presets-vs-kits best for?
presets-vs-kits is best for reusing agent instructions, scripts, and references, testing workflows, writing workflows.
How do I install presets-vs-kits?
Install or run presets-vs-kits using Copy skill directory. Check presets-vs-kits for the latest setup command.
Is presets-vs-kits actively maintained?
presets-vs-kits may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
