CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

71%

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

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 body is compact and well-sectioned but carries almost no substance: guidance is generic boilerplate that would apply to any skill, the sole concrete action points to a resource file that is missing from the bundle, and no actual security patterns, checks, or workflow steps appear. It reads as a template skeleton rather than an operational skill.

Suggestions

Ship resources/implementation-playbook.md (or remove the reference): the dangling reference is the body's only concrete instruction and currently points to nothing.

Replace the generic Instructions bullets with skill-specific steps, e.g., a triage workflow for audits (map external calls, check access control on privileged functions, verify checks-effects-interactions, re-test) so the body instructs rather than describes.

Inline a small quick-start set of the highest-value secure patterns (reentrancy guard, checks-effects-interactions, access-control modifier, CEI in token transfers) instead of the filler 'Do not use this skill when' section.

DimensionReasoningScore

Conciseness

The body is lean (~35 lines) with zero over-explanation of concepts Claude already knows, and sections are compact. Not a 5 because the generic 'Instructions' bullets ('Clarify goals, constraints, and required inputs'), the vacuous 'Do not use this skill when' section, and the opening line duplicating the frontmatter description are filler that does not earn its place.

4 / 5

Actionability

The only concrete instruction in the entire body is 'If detailed examples are required, open resources/implementation-playbook.md'; everything else — 'Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification' — is abstract direction with no specific steps, patterns, code, or commands. Not a 1 because the conditional pointer to the playbook is a real, executable instruction; not a 3 because no concrete guidance for any actual task (writing, auditing, hardening a contract) is present.

2 / 5

Workflow Clarity

'Clarify goals → apply best practices → validate outcomes' is a rough sequence, but it is a generic template applicable to any skill, with no domain-specific steps and no validation method behind 'validate outcomes'. Not a 1 because a rough sequence with a verification mention exists; not a 3 because the steps are boilerplate rather than defined for smart-contract work, and no checkpoints are actually specified.

2 / 5

Progressive Disclosure

Sections are well organized (Use when / Do not use / Instructions / Resources) and the reference is clearly signaled one level deep in a Resources section. However, the referenced file resources/implementation-playbook.md does not exist in the bundle (no resources/ directory is present), so the only promised detailed content is unreachable — structure is present but navigation breaks in practice, which fits anchor 3 better than 4.

3 / 5

Total

11

/

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.

A strong description: it clearly states what the skill does and when to use it, with natural, domain-specific trigger phrases. The main gap is that 'security measures' and 'common vulnerabilities' remain generic where more distinctive terms (audit, DeFi, reentrancy) would sharpen both specificity and trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'writing smart contracts, auditing existing contracts, implementing security measures for blockchain applications' — alongside 'prevent common vulnerabilities and implement secure Solidity patterns'. It falls short of a 5 because 'prevent common vulnerabilities' and 'security measures' stay generic rather than naming specific capabilities.

4 / 5

Completeness

It explicitly answers both: what — 'Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns'; when — 'Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications'. This matches the anchor-5 pattern of concrete what plus explicit 'Use when' triggers; a 4 would require the when to be less explicit, which it is not.

5 / 5

Trigger Term Quality

'smart contracts', 'auditing existing contracts', 'Solidity', and 'blockchain applications' are phrases users would naturally say when needing this skill. Not a 5: common variations like 'audit', 'DeFi', 'Web3', or specific vulnerability names (reentrancy, overflow) are absent from the description.

4 / 5

Distinctiveness Conflict Risk

'Solidity' and 'smart contract' triggers give a clear niche with minimal conflict risk, but 'implementing security measures for blockchain applications' is broad enough to overlap with general security or blockchain-development skills. Mostly distinct with minor overlap risk — an anchor-4 fit; not 5 because of that broad clause.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

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.