memory-safety-patterns

Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory bugs.

Quality

61%

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/memory-safety-patterns/SKILL.md

Quality

Content

36%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 content is a thin, generic template: it describes intent without concrete actions and relies on a reference file that is not present in the bundle. It needs executable guidance and a real referenced resource to be useful.

Suggestions

Replace generic bullets like 'Apply relevant best practices and validate outcomes' with concrete, executable steps or code snippets for RAII, smart pointers, and ownership patterns.

Provide a real implementation-playbook.md file (or correct the path) so the referenced detailed patterns actually exist; verify the bundle path matches the body.

Add explicit validation checkpoints for risky operations (e.g., leak checks, sanitizer runs, borrow-checker outcomes) to give the workflow real error-recovery feedback loops.

Dimension	Reasoning	Score
Conciseness	The body is short and not bloated, but several lines ('Apply relevant best practices', 'Provide actionable steps and verification') are generic filler that could be tightened into concrete guidance.	3 / 5
Actionability	Guidance is abstract — 'Apply relevant best practices and validate outcomes' offers only high-level hints with no concrete code, commands, or specific steps to execute.	2 / 5
Workflow Clarity	Only a rough generic sequence is present ('Clarify goals... Apply best practices... validate outcomes') with no real checkpoints, and the only detailed reference points to a file that does not exist.	2 / 5
Progressive Disclosure	Section structure exists and a one-level-deep reference is signaled, but the referenced resources/implementation-playbook.md is absent, so the disclosure path is broken.	3 / 5
	Total	10 / 20 Passed

Description

87%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 specifies concrete capabilities, distinct trigger conditions, and a clear domain niche across Rust, C++, and C. Minor additions of natural synonyms could push trigger-term coverage to the top level.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (RAII, ownership, smart pointers, resource management) across Rust, C++, and C, with only minor gaps in coverage.	4 / 5
Completeness	Clearly states what it does (implement memory-safe programming with RAII/ownership/smart pointers) and when to use it (writing safe systems code, managing resources, preventing memory bugs) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases like 'safe systems code', 'managing resources', and 'preventing memory bugs' give good keyword coverage, though a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	A clear memory-safety niche across three specific languages with distinct triggers, minimizing overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/memory-safety-patterns/SKILL.md
Commit: 3eff4af

Reviewed: 23 days 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.