Content
81%Weight 40%Scale 1-5Reviews 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).
| Dimension | Reasoning | Score |
|---|---|---|
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 |