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.

Quality

61%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/c-pro/SKILL.md

Quality

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 (C programming and system-level work) with specific capabilities and explicit usage triggers. The main weakness is the trigger term coverage could be expanded to include more natural user phrases like 'segfault', 'malloc', or 'buffer' that users commonly mention when facing C-related issues.

Suggestions

Add more natural trigger terms users commonly say: 'segfault', 'malloc/free', 'buffer overflow', '.c files', 'header files', 'linker errors'

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/free', 'buffer overflow', '.c files', or 'low-level programming'.	2 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on C language and system-level programming; distinct triggers like 'kernel modules', 'embedded systems', and 'pointer arithmetic' make it unlikely to conflict with general coding skills.	3 / 3
	Total	11 / 12 Passed

Implementation

37%

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 guidance that would make it truly actionable. The content reads more like a checklist of considerations than a practical guide with specific commands, code patterns, or validation workflows. The absence of any code examples for a programming skill is a significant gap.

Suggestions

Add executable code examples for key patterns like proper malloc/free pairing, error checking, and include guards

Include specific tool commands (e.g., 'valgrind --leak-check=full ./program', 'clang-tidy -checks=* file.c')

Create a clear workflow with validation steps for memory-safe C development: write -> compile with warnings -> static analysis -> valgrind check -> fix -> repeat

Remove the generic 'Use this skill when' boilerplate and persona statement to improve conciseness

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. Mentions tools (valgrind, gdb, clang-tidy) without showing actual commands or usage patterns. The 'Approach' section lists principles rather than copy-paste ready instructions.	2 / 3
Workflow Clarity	No clear sequenced workflow for C development tasks. The numbered 'Approach' items are principles, not steps. Missing validation checkpoints for memory management workflows, which are critical for the stated focus on memory leaks and malloc/free patterns.	1 / 3
Progressive Disclosure	References 'resources/implementation-playbook.md' for detailed examples, which is good progressive disclosure. However, the main content organization is flat with no clear navigation structure, and it's unclear what the playbook contains or when exactly to use it.	2 / 3
	Total	7 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: Dokhacgiakhoa/antigravity-ide
Commit: 332e58b

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.