c-pro

Write efficient C code with proper memory management, pointer

Quality

14%

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 ./skills/c-pro/SKILL.md

Quality

Discovery

22%

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 truncated mid-sentence, rendering it incomplete and largely ineffective for skill selection. It hints at C programming specifics like memory management and pointers but fails to articulate concrete actions or provide any trigger guidance for when Claude should select this skill.

Suggestions

Complete the truncated sentence and add a full 'Use when...' clause with explicit triggers such as 'Use when the user asks for help writing C code, debugging memory issues, working with pointers, or managing dynamic allocation.'

List specific concrete actions the skill performs, e.g., 'Writes C code, debugs segfaults, manages dynamic memory allocation with malloc/free, handles pointer arithmetic, and reviews code for memory leaks.'

Add natural trigger terms and file extensions users would mention, such as '.c files', '.h headers', 'malloc', 'free', 'segfault', 'buffer overflow', 'valgrind'.

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 mid-sentence, so it fails to fully answer 'what does this do' and completely lacks any 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent.	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 overflow', or file extensions like '.c' and '.h'.	2 / 3
Distinctiveness Conflict Risk	The mention of C-specific concepts like 'memory management' and 'pointer' provides some distinctiveness from general coding skills, but the vagueness and truncation mean it could still overlap with general programming or systems programming skills.	2 / 3
	Total	6 / 12 Passed

Implementation

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

This skill is essentially a generic description of C programming best practices that Claude already knows, wrapped in boilerplate template sections. It provides no executable code examples, no concrete workflows, and no novel information that would help Claude perform C programming tasks better than it already can. The content fails to justify its token cost.

Suggestions

Replace the generic 'Focus Areas' and 'Approach' lists with concrete, executable code examples showing specific patterns (e.g., a memory pool implementation, proper error-handling wrapper for malloc, a Makefile template with recommended flags).

Add a clear workflow with validation steps, e.g., 'Write code → Compile with -Wall -Wextra -Werror → Run valgrind --leak-check=full → Fix issues → Re-validate' with actual commands.

Remove all boilerplate sections ('Use this skill when', 'Do not use this skill when', 'Limitations') and the generic 'Instructions' bullets that add no C-specific value.

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the most critical patterns and examples directly in the skill.

Dimension	Reasoning	Score
Conciseness	The content is padded with boilerplate sections ('Use this skill when', 'Do not use this skill when', 'Limitations') that add no value for Claude. It explains general concepts Claude already knows (what memory management is, what valgrind does) without providing any concrete, novel information. The 'Instructions' section is generic filler applicable to any skill.	1 / 3
Actionability	There is zero executable code, no concrete commands, no specific examples, and no copy-paste ready snippets. The content reads as a high-level description of C programming topics rather than actionable guidance. Statements like 'every malloc needs free' and 'check all return values' are vague directions Claude already knows.	1 / 3
Workflow Clarity	There is no clear multi-step workflow or sequenced process. The 'Approach' section lists general principles rather than steps to follow. There are no validation checkpoints, no feedback loops, and no concrete process for tasks like memory debugging or building projects.	1 / 3
Progressive Disclosure	There is a reference to `resources/implementation-playbook.md` for detailed examples, which shows some attempt at progressive disclosure. However, no bundle files exist to support this reference, and the main content itself is poorly organized with generic boilerplate sections rather than a clear overview-to-detail structure.	2 / 3
	Total	5 / 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: sickn33/antigravity-awesome-skills
Commit: 1930a07

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