build-contracts

Builds all cosmwasm contracts

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/smartcontracts/SKILL.md

Quality

Content

87%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 maximally concise and actionable for a single-command skill, but it performs a batch build with no verification of success, which caps workflow clarity. Adding an explicit check that the build succeeded (and ideally artifact location) would raise the workflow score.

Suggestions

Add a verification step after the build, e.g. check the exit code or confirm generated .wasm artifacts exist in artifacts/ or target/wasm32-unknown-unknown/release/.

State where build artifacts are output so downstream steps can locate them.

Note expected failure handling (e.g. re-run on failure, report compiler errors) to turn the batch build into a feedback loop.

Dimension	Reasoning	Score
Conciseness	A single lean sentence gives one executable command and its location with no padding or over-explanation; every token earns its place, matching the 5 anchor.	5 / 5
Actionability	"execute [make build-contracts] from the project root directory" is copy-paste-ready, fully executable, and specifies the working directory; for a single-purpose skill this covers the common case per the 5 anchor.	5 / 5
Workflow Clarity	Building "all" contracts is a batch operation and the workflow has no validation/verification step (e.g. confirm the build succeeded, check artifacts), so workflow clarity is capped at 3 per the batch-operation guideline.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no need for external references and is organized under a single clear section, qualifying for the simple-skill exception to score 5.	5 / 5
	Total	18 / 20 Passed

Description

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

The description is third-person, specific, and clearly defines a niche, but it omits any "Use when" trigger guidance, capping completeness. Adding explicit trigger conditions and a few synonyms (compile, wasm) would lift the trigger and completeness scores.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks to compile or build CosmWasm contracts for deployment.'

Include natural synonyms/variants such as 'compile', 'wasm', or '.wasm' to broaden trigger-term coverage.

Optionally note scope (e.g. which workspace/contracts) to reduce overlap with generic build skills.

Dimension	Reasoning	Score
Specificity	Names a concrete domain (cosmwasm contracts) and one specific action ("Builds"), matching the 1-2 concrete actions anchor; it is not 2 because "Builds" is a concrete verb rather than the generic "Processes", and not 4 because only a single action is covered.	3 / 5
Completeness	A clear "what" is present ("Builds all cosmwasm contracts") but there is no "Use when..." trigger guidance, so completeness is capped at 3 per the missing-trigger guideline.	3 / 5
Trigger Term Quality	"build", "cosmwasm", and "contracts" are natural terms a developer would say, but coverage lacks common variations or synonyms (e.g. compile, wasm, .wasm); fits the 3 anchor rather than 4's broader keyword set.	3 / 5
Distinctiveness Conflict Risk	CosmWasm contract building is a narrow, mostly distinct niche with minor overlap risk against other build skills; it is not 5 because the description lacks explicit distinct trigger phrases present in the 5 anchor example.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: akash-network/node
Path: .agents/skills/smartcontracts/SKILL.md
Commit: 096bff5

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