/build-and-compile
Building, compiling, and resolving dependency issues across languages
Claude Code
$ npx -y skills add vstorm-co/pydantic-deepagents --skill build-and-compile --agent claude-code
Codex
$ npx skills add vstorm-co/pydantic-deepagents --skill build-and-compile -a codex -y
Cursor
$ npx skills add vstorm-co/pydantic-deepagents --skill build-and-compile -a cursor -y
Gemini CLI
$ npx skills add vstorm-co/pydantic-deepagents --skill build-and-compile -a gemini-cli -y
GitHub Copilot
$ npx skills add vstorm-co/pydantic-deepagents --skill build-and-compile -a github-copilot -y
OpenCode
$ npx skills add vstorm-co/pydantic-deepagents --skill build-and-compile -a opencode -y
Windsurf
$ npx skills add vstorm-co/pydantic-deepagents --skill build-and-compile -a windsurf -y
SKILL.md
build-and-compile.SKILL.mdname: build-and-compile
description: "Building, compiling, and resolving dependency issues across languages"
tags: [build, compile, dependencies, benchmark]
version: "1.0.0"
Build & Compile
Strategies for building code and resolving dependency issues.
Build System Detection
Check for build files in order:
- `Makefile` → `make` (read it first to understand targets)
- `CMakeLists.txt` → `cmake -B build && cmake --build build`
- `pyproject.toml` / `setup.py` → `pip install -e .`
- `package.json` → `npm install && npm run build`
- `Cargo.toml` → `cargo build --release`
- `go.mod` → `go build ./...`
- No build system → compile directly (`gcc`, `g++`, `rustc`, etc.)
Compilation Strategies
C/C++
- Always read the Makefile/CMakeLists first
- Common flags: `-O2 -Wall -lm -lpthread`
- Missing headers → `apt-get install lib<name>-dev`
- Linking errors → check library order (dependencies last: `-lfoo -lbar -lm`)
Python
- Use virtual environments when possible
- `pip install -e .` for editable installs
- Missing modules → check `requirements.txt`, `pyproject.toml`
- Version conflicts → read the actual error, pin versions
Multi-language projects
- Build dependencies first (C libraries before Python bindings)
- Check for Cython, SWIG, or FFI bridges
- Environment variables often needed: `LD_LIBRARY_PATH`, `PYTHONPATH`
Dependency Resolution
1. Read the FULL error message — the missing dependency is usually named 2. Search for the package: `apt-cache search <name>`, `pip search <name>` 3. Install the minimum needed — don't install everything 4. If a package is unavailable, check for alternatives or build from source
Common Build Failures
| Error | Likely Cause | Fix | |-------|-------------|-----| | `fatal error: foo.h: No such file` | Missing dev headers | `apt-get install libfoo-dev` | | `undefined reference to` | Missing library at link time | Add `-lfoo` flag | | `No module named 'foo'` | Missing Python package | `pip install foo` | | `command not found: make` | Build tools missing | `apt-get install build-essential` | | `version 'GLIBC_X.Y' not found` | Binary built for newer system | Rebuild from source |
Read more
name: build-and-compile description: "Building, compiling, and resolving dependency issues across languages" tags: [build, compile, dependencies, benchmark] version: "1.0.0"
Build & Compile
Strategies for building code and resolving dependency issues.
Build System Detection
Check for build files in order:
- `Makefile` → `make` (read it first to understand targets)
- `CMakeLists.txt` → `cmake -B build && cmake --build build`
- `pyproject.toml` / `setup.py` → `pip install -e .`
- `package.json` → `npm install && npm run build`
- `Cargo.toml` → `cargo build --release`
- `go.mod` → `go build ./...`
- No build system → compile directly (`gcc`, `g++`, `rustc`, etc.)
Compilation Strategies
C/C++
- Always read the Makefile/CMakeLists first
- Common flags: `-O2 -Wall -lm -lpthread`
- Missing headers → `apt-get install lib<name>-dev`
- Linking errors → check library order (dependencies last: `-lfoo -lbar -lm`)
Python
- Use virtual environments when possible
- `pip install -e .` for editable installs
- Missing modules → check `requirements.txt`, `pyproject.toml`
- Version conflicts → read the actual error, pin versions
Multi-language projects
- Build dependencies first (C libraries before Python bindings)
- Check for Cython, SWIG, or FFI bridges
- Environment variables often needed: `LD_LIBRARY_PATH`, `PYTHONPATH`
Dependency Resolution
1. Read the FULL error message — the missing dependency is usually named 2. Search for the package: `apt-cache search <name>`, `pip search <name>` 3. Install the minimum needed — don't install everything 4. If a package is unavailable, check for alternatives or build from source
Common Build Failures
| Error | Likely Cause | Fix | |-------|-------------|-----| | `fatal error: foo.h: No such file` | Missing dev headers | `apt-get install libfoo-dev` | | `undefined reference to` | Missing library at link time | Add `-lfoo` flag | | `No module named 'foo'` | Missing Python package | `pip install foo` | | `command not found: make` | Build tools missing | `apt-get install build-essential` | | `version 'GLIBC_X.Y' not found` | Binary built for newer system | Rebuild from source |
Open-source, self-hosted Claude Code - a terminal AI assistant and the Python framework behind it. Tool-calling, sandboxed execution, multi-agent teams, skills, checkpoints, unlimited context - on Pydantic AI, any model.
Other skills on pydantic-deepagents.
data-formats
Working with diverse data formats: binary, text, structured, and custom
environment-discovery
Systematic exploration of unknown environments before starting work
performant-code
Writing efficient code that handles large data and tight constraints
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about build-and-compile.
- Which coding agents can use build-and-compile?
- build-and-compile installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

