CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

95

1.37x
Quality

Does it follow best practices?

Impact

91%

1.37x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, actionable reference skill with excellent conciseness, concrete code, and a well-sequenced validated workflow. Its one weakness is progressive disclosure: the body points to a rules/ bundle and an external contract-style-guide that are not present in the skill bundle.

Suggestions

Include the referenced rules/*.md files (gas-optimization, natspec, file-layout, naming-conventions, imports, visibility, general-rules, commands) in the skill bundle so the signaled one-level-deep references actually resolve.

Either ship ../../../contracts/docs/contract-style-guide.md alongside the skill or rewrite that reference to point to a bundled local file, since the cross-tree path is not part of the bundle.

Consider a short note clarifying that rule files live outside the bundle, so Claude does not attempt to follow dead links when the skill is invoked standalone.

DimensionReasoningScore

Conciseness

The body is lean: a priority table, correct/incorrect code blocks, ordered structure lists, and concrete commands, with no padding or re-explanation of what Solidity or Linea is. The only minor redundancy is the brief 'When to Apply' list echoing frontmatter triggers, but every token otherwise earns its place.

3 / 3

Actionability

Provides copy-paste-ready executable Solidity examples with explicit correct/incorrect contrast, specific commands ('pnpm -F contracts run build'), and concrete ordered file-layout templates — fully actionable, not abstract.

3 / 3

Workflow Clarity

The 7-step Development Workflow is clearly sequenced with validation checkpoints (compile->fix, lint->fix, test) and a Commit Checklist; while not a destructive/batch operation, the explicit verify NatSpec and review gas steps give clear feedback loops.

3 / 3

Progressive Disclosure

The overview is well structured with one-level-deep, clearly signaled references (priority table linking rules/gas-optimization.md, rules/natspec.md, etc.), but no bundle files exist — the referenced rules/*.md paths and ../../../contracts/docs/contract-style-guide.md do not resolve to real files, so the actual bundle structure is missing.

2 / 3

Total

11

/

12

Passed

Description

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.

A well-crafted description: third-person voice, concrete capabilities, explicit 'Use when' triggers, and a distinct Linea/Solidity niche. Third person is maintained throughout with no first/second person.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('writing, reviewing, or refactoring Solidity contracts') plus specific coverage areas ('NatSpec documentation, naming conventions, file layout, and code style'), matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (Linea Solidity development guidelines covering NatSpec/naming/layout/style) and when via a clear 'Use when writing, reviewing, or refactoring... or when the user asks about...' trigger clause.

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered: 'Solidity', 'Linea blockchain', 'smart contract', 'NatSpec docstrings', and 'best practices', giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (Solidity contracts on Linea) with distinct, specific triggers unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 missing, 1 suspicious

Warning

Total

15

/

16

Passed

Repository
Consensys/linea-monorepo
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.