developing-smart-contracts
Solidity smart contract development guidelines for Linea 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.
91
86%
Does it follow best practices?
Impact
99%
1.47xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly defines its scope (Solidity smart contract development for Linea), provides explicit trigger conditions via a 'Use when...' clause, and lists specific topics covered. It uses proper third-person voice and includes natural keywords that users would employ when seeking help with Solidity development.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and topics: NatSpec documentation, naming conventions, file layout, code style, writing/reviewing/refactoring Solidity contracts. | 3 / 3 |
Completeness | Clearly answers both what ('Solidity smart contract development guidelines covering NatSpec documentation, naming conventions, file layout, and code style') and when ('Use when writing, reviewing, or refactoring Solidity contracts, or when the user asks about Solidity best practices, contract structure, or NatSpec docstrings'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'Solidity', 'smart contract', 'Linea blockchain', 'NatSpec', 'docstrings', 'best practices', 'contract structure', 'naming conventions', 'code style'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Solidity contracts specifically for Linea blockchain. The combination of blockchain-specific context and Solidity development guidelines makes it unlikely to conflict with general coding or other blockchain skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-organized skill that excels at progressive disclosure and conciseness, serving as an effective overview document that points to detailed rule files. Its main weakness is that the SKILL.md itself provides limited actionable, executable content—most concrete guidance is deferred to referenced files that weren't provided for evaluation. The workflow could benefit from explicit validation steps during the development process, not just at commit time.
Suggestions
Add a brief executable code example inline (e.g., a minimal contract skeleton showing correct pragma, license, NatSpec, and file layout) so the skill is actionable even without reading all rule files.
Expand the commit checklist into a development workflow with explicit validation checkpoints, e.g., 'After writing contract → run `pnpm -F contracts run lint:fix` → fix errors → verify NatSpec coverage → commit'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. It avoids explaining what Solidity, NatSpec, or smart contracts are, respecting Claude's existing knowledge. Every section serves a clear purpose with minimal padding. | 3 / 3 |
Actionability | The skill provides some concrete guidance (exact pragma versions, file layout ordering, lint command, import rules) but mostly delegates to external rule files for actual code examples and detailed instructions. The quick reference sections are summaries rather than executable guidance. | 2 / 3 |
Workflow Clarity | The commit checklist provides a clear verification sequence, and the priority table gives good ordering. However, the actual development workflow lacks explicit validation checkpoints or feedback loops—e.g., no 'compile and check for errors before proceeding' step, and the checklist is a simple list without error recovery guidance. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: a concise overview with a prioritized table, quick reference summaries for each category, and clearly signaled one-level-deep references to individual rule files. Navigation is easy and well-organized. | 3 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Consensys/linea-monorepo
- Commit
8ff65cd
- 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.