m11-ecosystem · 13eholder — Claude Code skill: what it does, how to install
m11-ecosystem — a skill that gives a coding agent one set of choices for building and maintaining a C++ project: CMake, a package manager, static analysis and a sanitizer.
MIT 1 installs ★ 14 updated 2026-02-14
npx skills add 13eholder/Modern-Cpp-Skills --skill m11-ecosystem -a claude-codeWhat m11-ecosystem does
Ask a coding agent how to build the project and this skill narrows it to one answer. CMake generates the build, dependencies come from vcpkg or Conan, and libraries do not get installed by hand.
The file is a reference, not a build script: one question about reproducibility, a small table of tools, and the checks to switch on. Reproducible means CMake plus a vcpkg.json manifest. The other branch is manual paths. Clang-Tidy handles static analysis, fsanitize=address is there for memory bugs.
Where it takes a side: hand-pinned library paths are called the bad branch, so expect the agent to push a manifest first when your project has none. ASan is credited with catching 90% of memory errors, which is the argument for turning it on early.
What it helps with
- move a project off hand-written build scripts onto CMake
- pick vcpkg or Conan for a dependency set
- pin dependencies in
vcpkg.jsonso builds repeat - wire Clang-Tidy and AddressSanitizer into the workflow
- explain to the agent why manual library paths are a dead end
Example prompts for the agent
- Switch this project to CMake and add a
vcpkg.jsoninstead of the hardcoded library paths. - Should we use vcpkg or Conan here? Pick one and justify it for this build.
- Turn on
fsanitize=addressand Clang-Tidy, then tell me what each one catches.
How to install m11-ecosystem
1Skills CLI (Vercel)
npx skills add 13eholder/Modern-Cpp-Skills --skill m11-ecosystem -a claude-code2Manually: put the files in place
~/.claude/skills/m11-ecosystem/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/m11-ecosystem/
1Skills CLI (Vercel)
npx skills add 13eholder/Modern-Cpp-Skills --skill m11-ecosystem -a codex2Manually: put the files in place
.agents/skills/m11-ecosystem/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add 13eholder/Modern-Cpp-Skills --skill m11-ecosystem -a cursor2Manually: put the files in place
.cursor/skills/m11-ecosystem/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install 13eholder/Modern-Cpp-Skills m11-ecosystem2Manually: put the files in place
.github/skills/m11-ecosystem/SKILL.md1Skills CLI (Vercel)
npx skills add 13eholder/Modern-Cpp-Skills --skill m11-ecosystem -a gemini-cli2Platform CLI
gemini skills install https://github.com/13eholder/Modern-Cpp-Skills --path m11-ecosystemManually: put the files in place
.devin/skills/m11-ecosystem/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add 13eholder/Modern-Cpp-Skills --skill m11-ecosystem -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about m11-ecosystem
How do I install m11-ecosystem in Claude Code?
Run npx skills add 13eholder/Modern-Cpp-Skills --skill m11-ecosystem -a claude-code. The skill file lands at ~/.claude/skills/m11-ecosystem/SKILL.md.
What does m11-ecosystem do?
It hands the agent a fixed set of choices for building and maintaining a C++ project: CMake for the build, vcpkg or Conan for dependencies, Clang-Tidy and AddressSanitizer for checks.
vcpkg or Conan — how does the skill tell them apart?
vcpkg is described as the MSFT package manager that builds dependencies from source. Conan runs on Python and caches binaries.
Source text
SKILL.md · MIT
---
name: m11-ecosystem
description: "Mastering C++ Ecosystem: CMake, vcpkg, Conan, Sanitizers, Tooling."
---
# C++ Ecosystem
## Core Question
**How do I build and maintain this?**
- **Build**: CMake (Standard).
- **Deps**: vcpkg or Conan (Don't manual install).
- **Quality**: Clang-Tidy + AddressSanitizer.
## Thinking Prompt
1. **Is the build reproducible?**
- Yes? → CMake + Manifest (vcpkg.json).
- No? → Manual paths (Bad).
2. **Are you checking for bugs?**
- `fsanitize=address` (ASan) catches 90% of memory errors.
## Quick Reference
| Tool | Purpose |
| -------------- | ---------------------------------------- |
| **CMake** | Build System Generator. |
| **vcpkg** | MSFT Package Manager (Source based). |
| **Conan** | Python Package Manager (Binary caching). |
| **ASan** | Address Sanitizer (Memory bugs). |
| **Clang-Tidy** | Static Analysis / Linter. |
© 13eholder · MIT · 13eholder/Modern-Cpp-Skills
Similar skills
All skills for Programming languages →m11-ecosystem by other authors comes first.