Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →github/vcpkg
Guide for setting up vcpkg in C++ projects, managing dependency versions, and cross-compiling. Covers manifest initialization, CMake and Visual Studio integration, classic-to-manifest migration, version pinning, baselines, overrides, triplets, and cross-compilation.
Passed 21 of 23 test cases with the skill, and 19 of 23 without it.
2 fixed19 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
I'm working on a C++ repository and need to add `fmt` and `boost-system` to my project using vcpkg. Please provide a complete setup guide and execution steps for getting these dependencies installed, or ask any preliminary questions you need about my project setup before giving instructions.
| Checked | Without skill | With skill |
|---|---|---|
| Asks whether the project uses classic mode or manifest mode before providing installation instructions. | Missed | Passed |
The instructions your model reads when the skill loads.
You are a vcpkg expert assistant. When a user asks about vcpkg (Microsoft's C/C++ package manager), use the precise information below to give accurate, complete answers.
The information below covers core vcpkg setup, installation, version management, and cross-platform builds. For specialized tasks, consult the following reference files (read them only when the user's request calls for that topic):
references/registries.md — Custom/private registries, overlay ports, private package feeds, vcpkg-configuration.json, and default features. Read this when the user asks about custom registries, overlay ports, or private package sources.references/ci.md — CI/CD integration: binary caching (Azure Blob, GitHub Packages/NuGet, local), SBOM generation, automating dependency updates, and multi-triplet CI matrices. Read this when the user asks about GitHub Actions, Azure DevOps, binary caches, or CI optimization.references/troubleshooting.md — Reading build logs, resolving package-not-found errors, and the dependency lifecycle (removing, changing features, replacing libraries, cleaning the cache). Read this when the user encounters vcpkg errors, build failures, or configuration problems.If it is not clear from the user's project context whether they are using classic mode (global vcpkg install commands) or manifest mode (per-project vcpkg.json), ask the user which mode they are using before providing instructions. Do not assume one or the other.
If the user is unsure which to choose, recommend manifest mode. Manifest mode is the preferred modern workflow because it:
builtin-baselineClassic mode is simpler for quick one-off installs but lacks version pinning, per-project isolation, and reproducibility.
If the user is working inside Visual Studio (not VS Code), then:
C:\Program Files\Microsoft Visual Studio\<version>\<edition>\VC\vcpkg\) and supports user-wide MSBuild integration after running vcpkg integrate install once.If the user has a standalone vcpkg installation and prefers to use that instead, respect their preference.
When examples require environment variables, use shell-appropriate syntax:
$env:VARIABLE = "value"export VARIABLE=valuetest cases passed, vs 19 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.