developing-smart-contracts

Solidity smart contract development guidelines for Lineth blockchain. Use when writing, reviewing, or refactoring Solidity contracts, or when the user asks about Solidity best practices, contract structure, or NatSpec docstrings. Covers NatSpec documentation, naming conventions, file layout, and code style.

1.89x

Quality

85%

Does it follow best practices?

Impact

87%

1.89x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 concise and highly actionable, with a clear sequenced workflow and validation checkpoints. Its main weakness is progressive disclosure: it points readers to rules/*.md and a contracts/docs style guide that do not exist in the skill bundle.

Suggestions

Create the referenced rules/*.md files (gas-optimization, natspec, file-layout, naming-conventions, imports, visibility, general-rules, commands) so the 'See rules/...' links resolve, or remove the dead links.

Verify the external reference '../../../contracts/docs/contract-style-guide.md' resolves from the skill's installed location, or replace it with an in-bundle reference.

Add an explicit feedback loop to the Development Workflow (e.g., 'If lint/test fails, fix and re-run before proceeding') to lift workflow clarity toward 5.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with terse bullets, a priority table, and code blocks; it does not over-explain concepts Claude already knows. It sits above the 3 anchor (no unnecessary explanation) but the inline Quick Reference code blocks duplicate detail that is also promised in the rule files, keeping it just short of the 5 anchor's 'every token earns its place'.	4 / 5
Actionability	Provides copy-paste-ready correct/incorrect Solidity examples and concrete executable commands ('pnpm -F contracts run build', 'lint:fix', 'test'), covering the common cases, matching the 5 anchor for fully executable guidance.	5 / 5
Workflow Clarity	The 7-step Development Workflow sequences write -> compile -> lint -> test -> NatSpec/gas review -> commit, with build/lint/test commands and a commit checklist as checkpoints. It is below 5 because there is no explicit 'if it fails, fix and retry' feedback loop, and above 3 because most checkpoints (compile, lint, test, checklist) are present and concrete.	4 / 5
Progressive Disclosure	The body is well-structured as an overview with one-level-deep links to rule files ('See [rules/gas-optimization.md](rules/gas-optimization.md)'), but no rules/, references/, scripts/, or assets/ directories exist, so the referenced files are missing. Per the 'score against the actual bundle structure' guideline, the broken/absent references cap this at 3.	3 / 5
	Total	16 / 20 Passed

Description

92%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 well-crafted description that clearly states capabilities, explicit use-when triggers, and a distinct Lineth/Solidity niche. Voice is correctly third person with no fluff. Only minor gap is a few missing synonym trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('writing, reviewing, or refactoring Solidity contracts') plus explicit coverage areas (NatSpec documentation, naming conventions, file layout, code style), giving comprehensive coverage rather than the 4 anchor's 'minor gaps'.	5 / 5
Completeness	Explicitly answers both 'what' (Solidity contract development guidelines for Lineth) and 'when' ('Use when writing, reviewing, or refactoring Solidity contracts, or when the user asks about Solidity best practices, contract structure, or NatSpec docstrings') with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('Solidity contracts', 'Solidity best practices', 'contract structure', 'NatSpec docstrings') but a few natural variants/synonyms (e.g., 'smart contracts', 'Solidity code review') are missing, so it sits above the 3 anchor but short of the 5 anchor's synonym/file-extension completeness.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Solidity on Lineth blockchain) with distinct triggers and minimal overlap with other skills, matching the 5 anchor for a clear niche with distinct triggers.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 8 missing, 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: Consensys/linea-monorepo
Path: .agents/skills/developing-smart-contracts/SKILL.md
Commit: 24fa37a

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