optimizing-gas-fees
Optimize blockchain gas costs by analyzing prices, patterns, and timing. Use when checking gas prices, estimating costs, or finding optimal windows. Trigger with phrases like "gas prices", "optimize gas", "transaction cost", "when to transact".
83
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 well-structured skill description that clearly identifies its niche (blockchain gas optimization), provides explicit trigger guidance, and includes natural user-facing keywords. The main weakness is that the specific capabilities could be more concrete—listing particular outputs or analyses rather than general verbs like 'analyzing' and 'estimating'.
Suggestions
Add more concrete action outputs, e.g., 'generate gas cost estimates, recommend optimal transaction windows, compare historical gas trends' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (blockchain gas costs) and some actions (analyzing prices, patterns, timing; checking gas prices, estimating costs, finding optimal windows), but the actions are somewhat general and not deeply concrete—e.g., it doesn't specify specific outputs like 'generate gas cost reports' or 'compare L1 vs L2 fees'. | 2 / 3 |
Completeness | Clearly answers both 'what' (optimize blockchain gas costs by analyzing prices, patterns, and timing) and 'when' (explicit 'Use when' clause with triggers, plus a 'Trigger with phrases' line listing specific keywords). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would actually say: 'gas prices', 'optimize gas', 'transaction cost', 'when to transact'. These cover common variations of how users would phrase requests about blockchain gas optimization. | 3 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche—blockchain gas cost optimization—with distinct trigger terms like 'gas prices' and 'optimize gas' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability—every command is concrete and executable. The main weaknesses are some unnecessary reference tables that pad the content without aiding Claude's task execution, and the lack of validation/verification steps for ensuring gas price data is fresh and accurate before making recommendations. The progressive disclosure is well-designed in principle, though bundle files weren't available to confirm referenced paths.
Suggestions
Add a validation step to verify RPC endpoint connectivity and data freshness before relying on gas price outputs (e.g., check block timestamp recency).
Remove or condense the Supported Chains and Price Tiers tables—these are static reference data better suited for the references/ directory rather than the main skill body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with concrete commands, but includes some unnecessary information like the supported chains table, price tiers table, and block time details that Claude could infer or that don't directly aid task execution. The overview section restates what the description already covers. | 2 / 3 |
Actionability | Every instruction provides fully executable bash commands with clear flags and options. The operations list is explicit, and each subcommand is demonstrated with copy-paste ready examples including variations. | 3 / 3 |
Workflow Clarity | Steps are clearly listed and sequenced, but there are no validation checkpoints or feedback loops. For operations involving real transactions and cost estimation, there's no guidance on verifying results, handling stale data, or confirming accuracy before acting on recommendations. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to errors.md and examples.md. The main content stays concise while pointing to detailed materials for error handling and extended examples. However, no bundle files were provided to verify these references exist. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.