c-pro

Write efficient C code with proper memory management, pointer

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

53%Weight 40%Scale 1-5

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

The skill body is concise and covers a sensible range of C focus areas, but it offers no executable code, lacks validation checkpoints in its workflow, and points to a reference file that does not exist in the bundle. Actionability and progressive disclosure are the weakest areas.

Suggestions

Add at least one complete, executable code example (e.g., a malloc/free pair with return-value checks) so guidance is copy-paste ready rather than descriptive.

Create the referenced resources/implementation-playbook.md (or fix the path) so the in-body reference resolves to a real file; bundle it under references/ with clear one-level navigation.

Insert explicit validation checkpoints into the Approach workflow (e.g., 'Run valgrind; only proceed on clean output' and 'Compile with -Wall -Wextra and resolve all warnings').

Dimension	Reasoning	Score
Conciseness	The body is mostly tight bullet lists that respect token budget; only minor over-explanation ('You are a C programming expert specializing in systems programming and performance') flatters Claude but is brief, fitting 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	Guidance is concrete in places (compiler flags '-Wall -Wextra', tool names 'valgrind/gdb/clang-tidy', 'CUnit') but provides no executable code or copy-paste commands, matching 'some concrete guidance but incomplete'.	3 / 5
Workflow Clarity	The numbered Approach and Output sections give a sequence, but there are no validation checkpoints or feedback loops despite output verification being implied, matching 'steps listed but validation gaps'.	3 / 5
Progressive Disclosure	The body references 'resources/implementation-playbook.md' but no references/scripts/assets bundle exists, so the reference points to a missing file and structure is minimal, fitting 'minimal structure; references are buried/invalid'.	2 / 5
	Total	12 / 20 Passed

Description

50%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear domain and a couple of concrete capabilities but is truncated mid-word and entirely lacks a 'Use when...' trigger clause, capping completeness and trigger usefulness. It is reasonably distinct from other skills.

Suggestions

Complete the truncated description (the word 'pointer' is cut off) and add 2-3 more concrete capabilities (e.g., pthreads, valgrind debugging, POSIX system calls).

Append an explicit 'Use when...' clause naming natural trigger phrases users would say (e.g., 'Use when writing, optimizing, or debugging C systems code, or when managing memory and pointers').

Include common synonyms/extensions like 'C99/C11', '.c/.h files', or 'embedded C' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the C domain plus two concrete capabilities ('efficient C code', 'memory management', 'pointer') but is truncated and not comprehensive, matching the score-3 anchor of 'names domain and 1-2 concrete actions'.	3 / 5
Completeness	A clear 'what' is present ('Write efficient C code with proper memory management') but there is no 'when should Claude use it' clause, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Only 'C code' appears as a relevant keyword with no synonyms or natural user phrases, fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Efficient C code with memory management and pointers' is a mostly distinct systems-programming niche with only minor overlap risk against adjacent skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/c-pro/SKILL.md
Commit: 1f67c44

Reviewed: 1 day 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.