c-pro
Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill c-proOverall
score
70%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope around C programming and system-level development. It provides explicit trigger guidance and specific capability areas. The main weakness is that trigger terms could include more natural variations users might actually type when seeking help.
Suggestions
Add more natural trigger terms users might say, such as 'segfault', 'malloc/free', 'pointers', '.c files', 'low-level programming', or 'buffer overflow'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'memory management, pointer arithmetic, system calls' and specific domains: 'embedded systems, kernel modules, performance-critical code'. | 3 / 3 |
Completeness | Clearly answers both what ('Write efficient C code with proper memory management...') and when ('Use PROACTIVELY for C optimization, memory issues, or system programming') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'C code', 'memory management', 'embedded systems', 'kernel modules', but missing common variations users might say like 'segfault', 'malloc', 'pointers', 'low-level programming', '.c files'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on C programming with distinct triggers like 'kernel modules', 'embedded systems', 'pointer arithmetic' that are unlikely to conflict with general programming skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable overview of C programming concerns but lacks the concrete, executable examples that would make it truly actionable. The content is moderately concise but includes generic boilerplate that doesn't add value. The workflow guidance is present but missing explicit validation checkpoints critical for memory-sensitive C development.
Suggestions
Add concrete, executable C code examples demonstrating proper malloc/free patterns, error checking, and include guards
Include an explicit validation workflow: compile with warnings -> run valgrind -> fix issues -> verify clean output
Remove the generic 'Use this skill when' boilerplate and replace with domain-specific triggers like 'memory leak debugging' or 'embedded optimization'
Add a minimal but complete example showing a properly structured C file with header, error handling, and cleanup
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary boilerplate (generic 'Use this skill when' section that adds little value) and the persona statement 'You are a C programming expert' is redundant. However, the focus areas and approach sections are reasonably lean. | 2 / 3 |
Actionability | Provides general guidance and checklists but lacks concrete, executable code examples. Statements like 'every malloc needs free' and 'Check all return values' are good principles but not copy-paste ready implementations. No actual C code snippets demonstrating the patterns. | 2 / 3 |
Workflow Clarity | The 'Approach' section provides a numbered list but lacks explicit validation checkpoints or feedback loops. For memory-critical C programming, there should be explicit validate-fix-retry cycles (e.g., run valgrind -> fix leaks -> re-run). The workflow is implicit rather than explicit. | 2 / 3 |
Progressive Disclosure | References 'resources/implementation-playbook.md' for detailed examples which is good, but the main content could be better organized. The sections are present but the 'Use this skill when' boilerplate takes up space that could be used for more actionable content. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.