Conan Vcpkg

This covers both Conan and vcpkg for managing C++ dependencies, which is helpful since you'll inevitably hit projects using either one. The decision tree is practical: vcpkg if you want simple setup and MSVC integration, Conan if you need binary caching or cross-compilation profiles. The manifest examples (vcpkg.json and conanfile.txt) show the actual integration with CMake, and the common dependency lookup table saves you from guessing package names between ecosystems. The Conan 2.x examples are current, which matters since the API changed significantly from 1.x. One honest take: both tools still involve more ceremony than modern language package managers, but this at least gives you the working patterns without trial and error.

skills.sh installs: 659
GitHub stars: 279
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add mohitmishra786/low-level-dev-skills --skill conan-vcpkg --agent claude-code

Installs into .claude/skills of the current project.

Files

Conan and vcpkg

Purpose

Guide agents through C/C++ dependency management with Conan and vcpkg: declaring dependencies, integrating with CMake, managing binary compatibility, and choosing the right tool for a given project.

Triggers

"How do I add a C++ library dependency with Conan?"
"How do I use vcpkg with CMake?"
"What's the difference between Conan and vcpkg?"
"How do I add zlib/openssl/fmt with a package manager?"
"How do I create a vcpkg.json manifest?"
"My Conan package build is failing — how do I debug it?"

Workflow

1. Conan vs vcpkg decision

Which package manager?
├── Team uses MSVC on Windows primarily → vcpkg (better MSVC integration)
├── Need binary packages (no source builds in CI) → Conan (binary cache)
├── Need cross-compilation support → Conan (profiles) or Zig-based builds
├── Need a specific version of a package → Conan (flexible versioning)
├── Quick project setup, just need it to work → vcpkg (simpler)
└── Open-source project, broad audience → vcpkg (GitHub-integrated)