solidity-security

Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications.

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/solidity-security/SKILL.md

Quality

Content

43%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 well-structured and token-lean, but it offers no concrete executable guidance and defers all detail to a referenced playbook file that does not exist in the bundle. Validation and workflow steps are present only as abstract boilerplate.

Suggestions

Add at least one copy-paste-ready example (e.g. a Checks-Effects-Interactions pattern snippet or an OpenZeppelin ReentrancyGuard import) so the skill is actionable without the missing playbook.

Create the referenced 'resources/implementation-playbook.md' (or remove the dangling reference) so progressive-disclosure navigation actually resolves.

Replace the abstract 'Instructions' bullets with a concrete sequenced workflow including a real validation checkpoint, e.g. '1. Identify external calls -> 2. Apply CEI pattern -> 3. Run slither --check-reentrancy -> 4. Only proceed if clean'.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not explain concepts Claude already knows (no 'what is reentrancy' padding), but the generic 'Instructions' bullets ('Clarify goals...', 'Apply relevant best practices...') add little value, keeping it just below a 5.	4 / 5
Actionability	No concrete code, commands, or executable examples appear; guidance is abstract ('Apply relevant best practices and validate outcomes') and the only concrete pointer, 'resources/implementation-playbook.md', does not exist in the bundle, leaving minimal executable guidance.	2 / 5
Workflow Clarity	A rough sequence exists (clarify goals -> apply practices -> validate -> verify) but the steps are poorly defined and validation is only mentioned abstractly with no concrete checkpoints or feedback loops, matching the 2 anchor.	2 / 5
Progressive Disclosure	Sections are well-organized and the reference is one level deep and clearly signaled, but 'resources/implementation-playbook.md' is a broken link (the file is absent), so navigation does not actually resolve.	3 / 5
	Total	11 / 20 Passed

Description

73%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 clearly scopes a distinct Solidity security niche with an explicit trigger clause and solid keyword coverage. Its main weakness is that the stated capabilities are abstract ('master best practices', 'prevent vulnerabilities') rather than a concrete list of what the skill does.

Suggestions

Replace abstract capability verbs ('Master... best practices', 'prevent common vulnerabilities') with concrete actions such as 'audit contracts for reentrancy and access-control flaws', 'apply Checks-Effects-Interactions', and 'recommend OpenZeppelin guard patterns'.

Add user-natural synonyms to the trigger clause, e.g. 'DeFi security', 'smart contract audit', or 'Web3 security review', to broaden trigger matching.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of actions ('prevent common vulnerabilities', 'implement secure Solidity patterns'), but the actions are abstract rather than a comprehensive list of concrete capabilities, matching the 3 anchor.	3 / 5
Completeness	Both 'what' and 'when' are present, with an explicit 'Use when...' clause listing concrete triggers; held at 4 rather than 5 because the 'what' ('Master... best practices') is high-level rather than naming concrete deliverables.	4 / 5
Trigger Term Quality	Good natural keyword coverage ('smart contracts', 'auditing existing contracts', 'blockchain applications', 'Solidity'), but missing common synonyms a user might say like 'DeFi security' or 'smart contract audit', fitting the 4 anchor.	4 / 5
Distinctiveness Conflict Risk	The Solidity/blockchain smart-contract-security niche is clearly scoped with distinct triggers ('Solidity patterns', 'smart contracts', 'blockchain applications'), giving minimal overlap with other skills.	5 / 5
	Total	16 / 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/solidity-security/SKILL.md
Commit: 3eff4af

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