CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 for C optimization, memory issues, or system programming.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/c-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 compact and well-sectioned with no external-reference debt, but it reads more like a best-practices checklist than an operational skill. It contains no executable code or commands, its workflow has only implicit validation, and about a fifth of the content is boilerplate filler.

Suggestions

Remove the boilerplate 'Use this skill when', 'Do not use this skill when', and 'Instructions' sections, whose generic lines ('Working on c pro tasks or workflows', 'Apply relevant best practices and validate outcomes') duplicate the frontmatter description without adding value.

Add concrete executable examples for the lowest-informationality items: a valgrind command (e.g., `valgrind --leak-check=full ./program`), a minimal Makefile snippet showing the recommended -Wall -Wextra flags, and a malloc-with-return-value-check pattern.

Reframe the Approach list as a sequenced workflow with explicit validation checkpoints, e.g., 'run clang-tidy, then valgrind; fix and re-run until both are clean before delivering code'.

DimensionReasoningScore

Conciseness

The Focus Areas, Approach, and Output sections are lean, but roughly ten lines are generic template filler — "Working on c pro tasks or workflows", "Clarify goals, constraints, and required inputs" — that add no value. Not 4 because this padding is more than minor over-explanation; not 2 because the substantive sections are efficient and the total is short.

3 / 5

Actionability

Concrete guidance exists via specific tools and flags ("clang-tidy", "-Wall -Wextra", "C99/C11", "valgrind and gdb") but there is no executable code or command anywhere — no valgrind invocation, no Makefile snippet, and "CUnit or similar" is vague. Not 4 because copy-paste-ready commands or examples are entirely absent; not 2 because the named tools and practices are specific, not high-level hints.

3 / 5

Workflow Clarity

The Approach section lists a coherent sequence of principles ("every malloc needs free", "Profile before optimizing") but validation checkpoints are only implicit — "Valgrind clean output demonstration" appears as an output expectation, not a step. Not 4 because there is no explicit validate-and-fix loop; not 2 because the listed steps are well defined rather than gappy.

3 / 5

Progressive Disclosure

The body is 45 lines with clear, well-organized sections (Use when, Instructions, Focus Areas, Approach, Output) and no need for external references — none are mentioned and none exist in the bundle. This satisfies the under-50-line simple-skill exception for a top score.

5 / 5

Total

14

/

20

Passed

Description

83%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 strong: it states concrete capabilities in third person, names specific domains, and includes an explicit 'Use for' trigger clause with natural phrases. Its only weaknesses are minor — a few missing natural synonyms and slightly generic trigger terms like 'memory issues' that could overlap with adjacent skills.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — "proper memory management, pointer arithmetic, and system calls" plus domains like "embedded systems, kernel modules" — matching the several-specific-actions anchor. Not 5 because coverage has minor gaps (threading, debugging, and build tooling are never mentioned in the description).

4 / 5

Completeness

Explicitly answers both parts: the "what" ("Write efficient C code with proper memory management, pointer arithmetic, and system calls") and the "when" ("Use for C optimization, memory issues, or system programming") with concrete trigger phrases. Not 4 because the when-clause is already explicit and specific rather than needing more detail.

5 / 5

Trigger Term Quality

"C optimization", "memory issues", and "system programming" are phrases users would naturally say, giving good keyword coverage. Not 5 because common synonyms like "memory leak", "segfault", or file extensions (.c, .h) are missing.

4 / 5

Distinctiveness Conflict Risk

The C systems-programming niche is clear and "C optimization" is a distinct trigger, but "memory issues" and "system programming" are broad enough to overlap with debugging or other systems-language skills. Not 5 due to this minor overlap risk; not 3 because the C-specific framing keeps it mostly distinct.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/c-pro/SKILL.md

Reviewed

Table of Contents

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.