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

60%

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

35%

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 but largely generic, restating the description and offering abstract instructions with no executable guidance. The single referenced resource is missing, leaving the skill without the concrete patterns it promises.

Suggestions

Replace abstract instructions ('Apply relevant best practices') with concrete, actionable guidance — e.g. specific reentrancy guards, checks-effects-interactions ordering, or example Solidity snippets.

Create the referenced resources/implementation-playbook.md (or correct the path) so the promised detailed patterns and examples actually exist.

Remove the verbatim restatement of the description from the opening and the low-value 'Do not use' bullets to tighten the body.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and short, but the opening sentence restates the description verbatim and the two 'Do not use this skill when' bullets add little value, so it could be tightened.	2 / 3
Actionability	Guidance is purely abstract — 'Apply relevant best practices', 'Provide actionable steps and verification' — with no concrete code, commands, patterns, or examples, matching the describes-rather-than-instructs anchor.	1 / 3
Workflow Clarity	Steps are listed (clarify, apply, validate) but there is no real sequence or validation checkpoints; it reads as generic process boilerplate rather than a guided workflow.	2 / 3
Progressive Disclosure	A reference to resources/implementation-playbook.md is signaled, but that file does not exist and no references/scripts/assets directories are present, so navigation is incomplete and the structure is thin.	2 / 3
	Total	7 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-formed description that clearly states capabilities and explicit usage triggers with a distinct niche. Trigger-term coverage is the weakest point, relying on generic phrasing rather than the concrete vulnerability terms users would naturally mention.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the domain — 'prevent common vulnerabilities', 'implement secure Solidity patterns', 'auditing existing contracts', 'implementing security measures' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly states what it does ('Master... prevent... implement secure Solidity patterns') and when to use it via an explicit 'Use when...' clause, satisfying both halves.	3 / 3
Trigger Term Quality	Natural terms like 'writing smart contracts' and 'auditing existing contracts' are present, but coverage is generic and misses common variations (e.g. specific vulnerability names), so it lands between some-keywords and full coverage.	2 / 3
Distinctiveness Conflict Risk	The Solidity security niche is distinct and the triggers are specific to blockchain/smart-contract work, making conflict with unrelated skills unlikely.	3 / 3
	Total	11 / 12 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: e63f7dd

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