Content
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an extensive reference catalog of Aptos Move gas optimization patterns but fails as an actionable skill. It is far too verbose, lacks a clear workflow for Claude to follow when analyzing a contract, and dumps all content into a single monolithic file. The code examples are a strength but are undermined by the lack of structure and process guidance.
Suggestions
Add a clear sequential workflow at the top: 1) Read the contract, 2) Identify expensive patterns (with specific checklist), 3) Apply optimizations, 4) Measure before/after gas, 5) Verify correctness — with explicit validation steps between stages.
Cut content by at least 50%: remove trigger phrase repetition, eliminate BAD examples (just show the GOOD pattern with a one-line note about what to avoid), condense checklists, and remove the report template or move it to a separate file.
Split into multiple files: keep SKILL.md as a concise overview with workflow, move detailed patterns to PATTERNS.md, the report template to REPORT_TEMPLATE.md, and measurement techniques to MEASUREMENT.md.
Fix the gas profiling example — `gas::remaining_gas()` is not a real Aptos Move API. Provide an actually executable measurement approach or clearly note limitations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines. It repeats trigger phrases already in the YAML description, explains basic concepts Claude knows (what vectors are, what O(n) means), includes a full report template, and has extensive checklists that could be drastically condensed. Many patterns are shown with both BAD and GOOD examples when just the GOOD pattern with a brief note would suffice. | 1 / 3 |
Actionability | The code examples are concrete and mostly executable Move code, which is good. However, the gas profiling section uses a non-existent `gas::remaining_gas()` API, the simulation command is generic, and the skill is more of a reference catalog than actionable step-by-step guidance for analyzing a specific contract. It describes patterns rather than instructing Claude on how to systematically analyze and optimize a given contract. | 2 / 3 |
Workflow Clarity | There is no clear sequential workflow for performing a gas analysis. The skill is organized as a reference catalog of patterns and checklists but lacks a defined process: how to start analyzing a contract, what order to check things, when to validate, and how to iterate. The checklists at the end are helpful but disconnected from any workflow. No validation checkpoints or feedback loops exist for the optimization process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no bundle files to reference. It mentions `STORAGE_OPTIMIZATION.md` but no such file exists. All content—expensive operations, optimization patterns, measurement, checklists, report template—is inlined in a single massive file with no meaningful separation or navigation structure. | 1 / 3 |
Total | 5 / 12 Passed |