c-pro

Write efficient C code with proper memory management, pointer

1.01x

Quality

22%

Does it follow best practices?

Impact

90%

1.01x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/c-pro/SKILL.md

The canonical home for this skill is c-pro in sickn33/antigravity-awesome-skills

Quality

Content

22%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like a persona description than actionable guidance. It lists general C programming principles that Claude already knows without providing concrete code examples, specific patterns, or executable workflows. The boilerplate 'use/don't use' sections with the placeholder 'c pro' suggest this was auto-generated with minimal customization.

Suggestions

Add concrete, executable code examples for key patterns (e.g., a proper malloc/free pattern with error handling, a thread-safe data structure template, include guard format).

Replace the generic 'Approach' list with a sequenced workflow: e.g., 1. Write code → 2. Compile with `-Wall -Wextra -Werror` → 3. Run `clang-tidy` → 4. Run `valgrind --leak-check=full` → 5. Fix issues and re-validate.

Remove the generic 'Use this skill when' / 'Do not use this skill when' boilerplate and the line 'You are a C programming expert' — these waste tokens on things Claude doesn't need to be told.

Add specific Makefile templates, header guard patterns, and valgrind invocation commands rather than just naming them in the Output section.

Dimension	Reasoning	Score
Conciseness	The skill has some unnecessary boilerplate (the generic 'Use this skill when' / 'Do not use this skill when' sections add no value and just repeat 'c pro'). The focus areas and approach sections are reasonably lean but list things Claude already knows well (e.g., 'every malloc needs free', 'check all return values').	2 / 3
Actionability	There are no concrete code examples, no executable commands, no specific patterns or templates. Everything is described at a high level ('use valgrind', 'check return values') without showing how. This is vague direction rather than executable guidance.	1 / 3
Workflow Clarity	The 'Approach' section lists general principles rather than a sequenced workflow. There are no validation checkpoints, no feedback loops for debugging or memory checking, and no clear step-by-step process for completing a C programming task.	1 / 3
Progressive Disclosure	There is a reference to 'resources/implementation-playbook.md' for detailed examples, which is good. However, the main content is poorly organized—mixing meta-instructions, focus areas, approach, and output expectations without clear hierarchy or navigation to supplementary materials.	2 / 3
	Total	6 / 12 Passed

Description

22%Scale 1-3

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 description is clearly truncated mid-sentence, rendering it incomplete and ineffective for skill selection. It lacks a 'Use when...' clause, lists no concrete actions beyond vaguely writing C code, and provides insufficient detail for Claude to distinguish it from other programming skills.

Suggestions

Complete the truncated sentence and add specific concrete actions (e.g., 'Writes C programs, debugs memory leaks, manages dynamic allocation with malloc/free, handles pointer arithmetic and data structures').

Add an explicit 'Use when...' clause with trigger terms like 'C programming', 'malloc', 'free', 'segfault', 'pointer arithmetic', 'buffer overflow', 'structs', '.c files'.

Ensure the description clearly differentiates this skill from general programming skills by emphasizing C-specific concerns like manual memory management, compilation, and low-level system programming.

Dimension	Reasoning	Score
Specificity	The description mentions 'memory management' and 'pointer' but is clearly truncated and does not list concrete actions. It vaguely references writing C code without specifying what tasks it performs (e.g., debugging, optimization, code generation).	1 / 3
Completeness	The description is truncated and incomplete—it partially addresses 'what' (write C code) but has no 'when' clause or explicit trigger guidance. The missing 'Use when...' clause alone would cap this at 2, but the truncation makes even the 'what' portion inadequate.	1 / 3
Trigger Term Quality	Contains some relevant keywords like 'C code', 'memory management', and 'pointer' that users might naturally mention, but the description appears cut off and is missing common variations like 'malloc', 'free', 'segfault', 'buffer', 'structs', etc.	2 / 3
Distinctiveness Conflict Risk	Mentioning 'C code', 'memory management', and 'pointer' provides some specificity to the C programming domain, but 'write efficient code' is generic enough to overlap with other programming-related skills.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/c-pro/SKILL.md
Commit: 0159794

Reviewed: 2 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.