low-level-dev-skills
Over 140 skills for systems programming: compilers, debuggers, profilers, firmware, the Linux kernel and binary analysis.
- 279 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The skills remain text instructions, but they suggest debugging, profiling and binary analysis commands that the agent then runs in your project.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/low-level-dev-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skills remain text instructions, but they suggest debugging, profiling and binary analysis commands that the agent then runs in your project.
This is third-party code. Review the repository files before installing.
What it does
A collection of more than 140 skills for low-level development in C and C++, Rust and Zig. The skills are grouped by task: compilers (`gcc`, `clang`, `llvm`, `pgo`), debuggers (`gdb`, `lldb`, `core-dumps`), profilers (`linux-perf`, `valgrind`, `flamegraphs`), build systems (`cmake`, `ninja`, `bazel`), sanitizers and fuzzing, ELF and linker analysis. Separate groups cover firmware and bare metal (`freertos`, `zephyr`, `stm32-baremetal`), drivers and the Linux kernel, processor architecture, compiler internals and MLIR, eBPF, WebAssembly, CUDA GPU programming, HPC with OpenMP and MPI, and reverse engineering. After installation the skills are invoked by name: `/gdb Set a conditional breakpoint`, `/linux-perf` or `/binary-hardening`.
Who it is for. Engineers who write in C, C++, Rust and Zig, build firmware or drivers and want the agent to know the flags and techniques of their tools.
Good fit when
- A program segfaults in production and the cause is traced through a core file with GDB.
- A C++ build takes tens of minutes and ccache, PCH and split DWARF are being tuned.
- STM32 firmware is written without libraries from a datasheet, configuring UART, SPI and DMA.
- Memory problems in Rust code are hunted with Miri and sanitizers.
- A binary is inspected with readelf and objdump and checked for RELRO and PIE hardening.
Not a fit when
- The project is entirely Python, JavaScript or Go with no native extensions.
- Work involves a single tool and 140 skills are excess: install individual skills with `--skill` instead.
- The team forbids third-party instructions in the agent context without an audit.
Example request
Record a CPU profile of this binary with `perf`, build a flamegraph and explain which functions consume the most time.Limitations
The skills supply reference instructions, while compilers, debuggers and profilers must be installed separately. Because of the volume, coverage is uneven: some areas have only one or two skills. A full installation adds over a hundred descriptions to the agent directory, which can clutter skill selection, so the README offers bundles by language and task. The `--global` flag installs the set for all projects. The last commit is from June 2026. The reverse engineering and kernel security sections hold dual-use topics, to be applied only to your own code and samples you have the right to analyze.
How to disable. Delete the skill directories from the agent's skills directory, for example `.claude/skills/`. A global installation is removed in the agent's home directory.
FAQ
How do I install all the skills at once?
Run `npx skills add mohitmishra786/low-level-dev-skills --all`. Add `--global` to make the skills work in all projects.
How do I install only the Rust skills?
Pass the list of names to `--skill`, for example `rustc-basics cargo-workflows rust-debugging rust-profiling rust-ffi rust-cross`. The README has ready bundles by language and task.
Which agents does the set work with?
The README names Claude Code, Cursor, Codex, GitHub Copilot, Cline, Windsurf, Gemini CLI and other agents, over thirty in all. Each takes the skills from its own directory, for example `.claude/skills/` or `.cursor/skills/`.
How is a skill invoked?
With a slash command and a question: `/gcc How do I enable link-time optimization?` or `/cmake What's the modern way to find packages?`. The agent also loads a skill on its own when the request matches the topic.
Are there skills for embedded systems?
Yes, two groups: Embedded with FreeRTOS, Zephyr, OpenOCD and linker scripts, and Bare-metal with processor startup, MMIO, interrupts, GPIO, UART, SPI, I2C, DMA and STM32.
Discussion
No questions or reviews yet.
Related
SkillsOver 200 skills by stack and practice: React, Next.js, Rails, Rust, Python, debugging, TDD and UI review
24 skills for microcontroller firmware: build, flash, GDB debugging, UART, Modbus, CAN, logic analyzers and static analysis
Four skills on Python, Rust and Go code: style, package boundaries and review drawn from experienced engineers' practice.
Three Intel skills for Linux perf: profiling, finding bottlenecks in code and perf output, and tuning Phoronix benchmarks
160 free skills for the full development cycle: backend, frontend, deployment and VibeCoding workflows, documented in Chinese.
Methods for an agent in one CLI: comparing options, solving problems and changing code in steps, 20 slash commands in all.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| low-level-dev-skills (this card) | no | 279 | |
| Rust Skills | no | 672 | a neighbouring card about Rust; here Rust is one part of a set alongside C, C++, Zig, firmware and the Linux kernel |
| Embedded Skills | no | 787 | a neighbouring card about embedded systems; here they are only one part of the set, which centers on compilers, debugging and profiling |
README in short
The README starts with a skills.sh link and install commands, then lists bundles by language and topic and usage examples. Tables of skills by group follow, with a short purpose for each.