CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.45x
Quality

86%

Does it follow best practices?

Impact

99%

1.45x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A well-structured overview skill with executable commands, concrete correct/incorrect examples, and a validation-rich workflow plus commit checklist. Main weaknesses: several categories are pointer-only with the referenced rule files absent from the bundle, one reference points outside the skill directory, and the SPDX section ("Apache-2.0 OR MIT") contradicts the frontmatter license (AGPL-3.0).

Suggestions

Ensure all referenced rule files (gas-optimization, natspec, file-layout, naming-conventions, imports, visibility, general-rules, commands) actually ship in the skill bundle — sections 4, 6, and 7 are pointer-only and provide no guidance if those files are missing.

Replace the out-of-bundle reference ../../../contracts/docs/contract-style-guide.md with a path inside the skill directory, since skill bundles are deployed in isolation and that link will break.

Add one representative rule inline for each pointer-only category (e.g., a top naming or visibility rule) so the Quick Reference remains actionable even before opening the rule file, and reconcile the SPDX-License-Identifier (Apache-2.0 OR MIT) with the frontmatter license (AGPL-3.0).

DimensionReasoningScore

Conciseness

The body is efficient — a priority table, short Quick Reference sections with compact correct/incorrect snippets, and pointer-only sections ("See [rules/naming-conventions.md](rules/naming-conventions.md) for symbol naming conventions"). Not 5: version pins ("Contracts: `0.8.33` (exact)") are time-sensitive values not placed in a deprecated/old-patterns section, and phrases like "Best practices for developing Solidity smart contracts on Lineth blockchain. Contains rules covering..." lightly restate the description.

4 / 5

Actionability

Concrete, executable guidance dominates: copy-paste commands ("pnpm -F contracts run build", "pnpm -F contracts run lint:fix", "pnpm -F contracts run test"), executable Solidity examples ("function submit(bytes32[] calldata _proofs) external"), and explicit ordered layout templates ("1. Structs → 2. Enums → 3. Events → 4. Errors → 5. External Functions"). Not 5: sections 4, 6, and 7 are bare pointers with no inline substance, and none of the referenced rules/*.md files exist in the bundle, leaving those categories with zero actionable content as shipped.

4 / 5

Workflow Clarity

The Development Workflow is a clear 7-step sequence with explicit validation checkpoints and fix loops: "Compile and fix errors", "Run linter and fix warnings", "Run tests to verify behavior", "Verify NatSpec coverage", "Review gas patterns", plus a Commit Checklist gating the final step. This matches the anchor's explicit validation steps, feedback loops, and checklist for a complex process; the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

Good overview structure: the priority table ("Rule File" column) plus per-category "See [rules/...].md" links form well-signaled one-level-deep navigation. Not 5: the reference at "[Lineth Contract Style Guide](../../../contracts/docs/contract-style-guide.md)" points outside the skill bundle and will not resolve when the skill is deployed in isolation, "rules/commands.md" is referenced outside the navigation table, and no rules/*.md files are present in the bundle to verify, so several sections point to unverifiable destinations.

4 / 5

Total

17

/

20

Passed

Description

87%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 explicitly states what the skill covers and when to use it, in third person, with concrete natural-language triggers and a clearly bounded Solidity/Lineth niche. The only notable gap is that gas optimization — the body's CRITICAL priority category — is absent from the coverage list.

DimensionReasoningScore

Specificity

"Covers NatSpec documentation, naming conventions, file layout, and code style" lists several concrete coverage areas, and "writing, reviewing, or refactoring Solidity contracts" names specific actions. Not 5: it omits gas optimization even though the body marks it as the CRITICAL top-priority category; not 3 because coverage clearly exceeds 1-2 actions.

4 / 5

Completeness

Both halves are explicit: the what ("Solidity smart contract development guidelines for Lineth blockchain... Covers NatSpec documentation, naming conventions, file layout, and code style") and the 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.

5 / 5

Trigger Term Quality

"writing, reviewing, or refactoring Solidity contracts", "Solidity best practices", "contract structure", and "NatSpec docstrings" are phrases users would naturally say. Not 5: common synonyms/file extensions like ".sol files" or "smart contract security" are missing; not 3 because keyword coverage goes well beyond a single generic term.

4 / 5

Distinctiveness Conflict Risk

"Solidity smart contract development guidelines for Lineth blockchain" plus "NatSpec docstrings" carves out a clear niche with distinct triggers and minimal overlap risk; generic Solidity or general-coding skills are unlikely to collide with these triggers.

5 / 5

Total

18

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 missing, 1 suspicious

Warning

Total

15

/

16

Passed

Repository

LFDT-Lineth/lineth-monorepo

Path

.agents/skills/developing-smart-contracts/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.