generate-tests

Creates comprehensive test suites for Move contracts with 100% coverage requirement. Triggers on: 'generate tests', 'create tests', 'write test suite', 'test this contract', 'how to test', 'add test coverage', 'write unit tests'.

Quality

68%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/generate-tests/SKILL.md

Quality

Discovery

89%

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 solid skill description that clearly identifies its niche (Move contract testing), states the key requirement (100% coverage), and provides an extensive list of natural trigger phrases. The main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond 'creates comprehensive test suites' — e.g., mentioning specific testing patterns, assertion types, or coverage strategies.

Suggestions

Expand the capability description to list more specific actions, e.g., 'Creates comprehensive test suites for Move contracts including unit tests, error case validation, and edge case coverage with 100% coverage requirement.'

Dimension	Reasoning	Score
Specificity	It names the domain (Move contracts) and the general action (creates test suites with 100% coverage), but doesn't list multiple specific concrete actions like testing specific features, edge cases, error paths, etc.	2 / 3
Completeness	Clearly answers both 'what' (creates comprehensive test suites for Move contracts with 100% coverage requirement) and 'when' (explicit trigger phrases listed after 'Triggers on:').	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'generate tests', 'create tests', 'write test suite', 'test this contract', 'how to test', 'add test coverage', 'write unit tests' — these are all phrases a user would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific niche of Move contracts (a blockchain smart contract language). Unlikely to conflict with general testing skills or other language-specific testing skills.	3 / 3
	Total	11 / 12 Passed

Implementation

47%

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

The skill has a well-structured workflow with clear steps and a proper validation feedback loop for achieving 100% coverage, and the Common Pitfalls section adds genuinely useful domain-specific knowledge. However, it is significantly too verbose—repeating concepts across the checklist, ALWAYS/NEVER rules, and workflow steps—and the code examples, while concrete-looking, are all against a fictional module making them illustrative rather than truly executable.

Suggestions

Cut the content by ~50%: merge the ALWAYS/NEVER rules and checklist into a single concise section, and remove the test template structure which duplicates the step-by-step examples.

Replace the fictional my_module examples with a single, minimal but complete and compilable Move test module, or explicitly frame the examples as templates with clear placeholder markers.

Extract the Common Pitfalls section into a separate referenced file (e.g., TESTING_PITFALLS.md) to keep the main skill focused on the core workflow.

Remove explanatory text like 'Test basic functionality works correctly' and 'Test unauthorized access is blocked' that merely restate what the section headers already convey.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines. It over-explains testing categories Claude already understands, provides extensive boilerplate code for a hypothetical module that isn't real (my_module), and repeats the same patterns multiple times (e.g., the test template structure largely duplicates the step-by-step examples). The ALWAYS/NEVER rules and checklist heavily overlap with each other and with the workflow steps.	1 / 3
Actionability	The code examples are syntactically concrete and use real Move test annotations (#[test], #[expected_failure]), but they reference a fictional module (my_module) with fictional functions and error codes, making them not truly executable. The coverage commands (aptos move test --coverage) are concrete and copy-paste ready, but the test code itself is illustrative pseudocode dressed as real code.	2 / 3
Workflow Clarity	The 6-step workflow is clearly sequenced from creating the test module through verifying coverage. Step 6 includes an explicit validation checkpoint (run coverage, check report, fix gaps, repeat until 100%), forming a proper feedback loop for the coverage requirement.	3 / 3
Progressive Disclosure	The skill references external files (TESTING.md, SECURITY.md, related skills) which is good, but the body itself is monolithic with extensive inline code that could be split into referenced examples. The Common Pitfalls section alone is substantial and could be a separate reference file. No bundle files are provided to support the referenced paths.	2 / 3
	Total	8 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: aave/aptos-aave-v3
Commit: 919362b

Reviewed: about 16 hours 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.