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

57%

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

47%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 body is well-structured and concise for a simple skill, with genuinely C-specific focus areas and output expectations. Its main weaknesses are the absence of executable code examples and a lack of any real build→validate workflow with checkpoints.

Suggestions

Add a minimal executable example — a short C snippet plus a Makefile with -Wall -Wextra and a valgrind command — so guidance is copy-paste ready.

Replace the principle list with a sequenced workflow: write code → compile with warnings → run tests → run valgrind → fix leaks/re-run, with an explicit validation checkpoint before declaring done.

Remove the generic templated 'Use this skill when / Do not use this skill when' and 'Instructions' boilerplate (e.g. 'Working on c pro tasks') since the frontmatter description already covers triggers.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly efficient, but it carries generic templated filler ('Working on c pro tasks or workflows', 'Clarify goals, constraints, and required inputs') that adds no C-specific value and could be trimmed.	3 / 5
Actionability	It names concrete tools and flags (clang-tidy, valgrind, gdb, CUnit, -Wall -Wextra, include guards) but provides no executable C code, Makefile, or copy-paste commands, leaving guidance as principles rather than runnable examples.	3 / 5
Workflow Clarity	The numbered 'Approach' list is a set of principles (every malloc needs free, check return values, profile before optimizing) rather than a sequenced workflow, and there is no build→test→validate feedback loop or validation checkpoint.	2 / 5
Progressive Disclosure	At ~45 lines with clear section headers (Focus Areas, Approach, Output) and no bundle files needed, the content is well-organized for a simple skill, with only minor clutter from the generic templated sections.	4 / 5
	Total	12 / 20 Passed

Description

67%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 is specific and clearly distinguishes a C systems-programming niche with an explicit trigger clause, scoring well on specificity and completeness. It is held back by trigger-term naturalness (missing common variations like 'memory leak' or 'segfault') and minor overlap risk from the generic 'memory issues' phrase.

Suggestions

Add natural user phrasings to the trigger clause, e.g. 'Use when the user mentions memory leaks, segfaults, pointer bugs, or needs to optimize or debug C code'.

Tighten 'memory issues' to something more distinctive like 'C memory leaks and allocation bugs' to reduce overlap with general debugging skills.

Prefer a standard 'Use when...' construction over 'Use PROACTIVELY for...' to match the most natural trigger phrasing.

Dimension	Reasoning	Score
Specificity	Lists several specific concrete actions and areas — 'memory management, pointer arithmetic, and system calls' plus 'embedded systems, kernel modules, and performance-critical code' — giving comprehensive coverage with only minor gaps.	4 / 5
Completeness	Clearly answers 'what' (write efficient C code with memory/pointer/syscall handling) and provides an explicit 'when' trigger ('Use PROACTIVELY for C optimization, memory issues, or system programming'), though the 'PROACTIVELY' phrasing is slightly less natural than a 'Use when...' clause.	4 / 5
Trigger Term Quality	'C optimization, memory issues, or system programming' are relevant keywords, but common natural variations users would actually say (e.g. 'memory leak', 'segfault', 'debug C', 'optimize C code') are missing.	3 / 5
Distinctiveness Conflict Risk	C systems programming is a clear niche with distinct triggers, but 'memory issues' could overlap marginally with debugging skills for other languages, leaving minor overlap risk.	4 / 5
	Total	15 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/c-pro/SKILL.md
Commit: 3eff4af

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