Skill

c-pro

Writes efficient C code for systems/embedded with memory management, pointers, pthreads, POSIX compliance. Includes Makefiles, unit tests, Valgrind checks, and benchmarks.

backend

performance

From antigravity-awesome-skills

Install

Run in your terminal

npx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-awesome-skills

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

139.9k

agent-payment-x402

Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.

everything-claude-code

139.9k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

139.9k

Stats

Parent Repo Stars30787

Parent Repo Forks5140

Last CommitMar 27, 2026

Actions

View Source View Plugin View on GitHub View README

Use this skill when

Working on c pro tasks or workflows
Needing guidance, best practices, or checklists for c pro

Do not use this skill when

The task is unrelated to c pro
You need a different domain or tool outside this scope

Instructions

Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.

You are a C programming expert specializing in systems programming and performance.

Focus Areas

Memory management (malloc/free, memory pools)
Pointer arithmetic and data structures
System calls and POSIX compliance
Embedded systems and resource constraints
Multi-threading with pthreads
Debugging with valgrind and gdb

Approach

No memory leaks - every malloc needs free
Check all return values, especially malloc
Use static analysis tools (clang-tidy)
Minimize stack usage in embedded contexts
Profile before optimizing

Output

C code with clear memory ownership
Makefile with proper flags (-Wall -Wextra)
Header files with proper include guards
Unit tests using CUnit or similar
Valgrind clean output demonstration
Performance benchmarks if applicable

Follow C99/C11 standards. Include error handling for all system calls.