c-pro

Write efficient C code with proper memory management, pointer

Quality

58%

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

67%

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

The body is concise and well-organized with domain-appropriate tooling references, but it provides no executable code examples and its only progressive-disclosure reference points to a non-existent file. Workflow steps lack explicit validation feedback loops.

Suggestions

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

Include explicit validation checkpoints in the Approach workflow, such as 'run valgrind; if leaks reported, fix allocations and re-run until clean.'

Fix or create the referenced 'resources/implementation-playbook.md' bundle file (or remove the reference) so progressive-disclosure links resolve to real files.

Dimension	Reasoning	Score
Conciseness	The body is lean: short bulleted focus areas, a numbered approach, and an output list with no padded explanations of C concepts Claude already knows. Every section earns its place.	3 / 3
Actionability	Guidance is concrete in spots (Makefile flags '-Wall -Wextra', valgrind, clang-tidy, CUnit) but there is no executable code or copy-paste example; the 'Approach' list reads as principles ('every malloc needs free', 'profile before optimizing') rather than runnable instructions.	2 / 3
Workflow Clarity	The 'Approach' list provides a rough sequence but lacks explicit validation checkpoints (e.g., 'run valgrind; if leaks, fix and re-run') despite involving destructive/risky operations like memory management. No feedback loop is documented, capping workflow clarity at 2 per the guidelines.	2 / 3
Progressive Disclosure	The skill references one external file ('resources/implementation-playbook.md') for detailed examples, but that path does not exist in any bundle directory, so the reference is broken rather than a well-signaled one-level-deep link. The body itself is otherwise well-organized into clear sections.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 conveys a focused C-programming niche but is marred by a truncated, cut-off sentence ('pointer') that weakens its action coverage and trigger phrasing. It answers 'what' but omits any explicit 'when to use' guidance.

Suggestions

Complete the truncated sentence to list concrete actions, e.g., 'Write efficient C code with proper memory management, pointer arithmetic, and thread safety.'

Add an explicit trigger clause such as 'Use when writing, debugging, or optimizing C code, or when memory management and systems programming are involved.'

Avoid the cut-off wording ('pointer') and use third-person action verbs consistent with the rubric's good examples.

Dimension	Reasoning	Score
Specificity	The description names the domain ('C code') and one concrete action ('Write efficient C code with proper memory management, pointer'), but the action list is truncated mid-phrase ('pointer') and only captures writing rather than the full range (debugging, profiling, threading) covered in the body.	2 / 3
Completeness	It states what the skill does (write efficient C code with memory management) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	'C code' and 'memory management' are relevant keywords a user might say, but the sentence is cut off and lacks common variations a user would naturally phrase (e.g., 'C programming', 'systems programming', 'C memory leaks').	2 / 3
Distinctiveness Conflict Risk	'C code with proper memory management' is a reasonably specific niche distinct from general coding skills, but the truncated wording and absence of trigger context leave it somewhat generic and able to overlap with generic code skills.	2 / 3
	Total	8 / 12 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: a3068b7

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