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 solid skill description that clearly defines its niche in blockchain gas optimization with explicit trigger guidance and a 'Use when' clause. 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'. Overall it performs well across all dimensions.
Suggestions
Add more concrete action outputs, e.g., 'generate gas price trend charts, compare historical gas costs, recommend optimal transaction windows based on network congestion patterns' 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 generic and not deeply concrete—e.g., it doesn't specify specific outputs like 'generate gas price charts' or 'compare L1 vs L2 costs'. | 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' clause listing specific user phrases). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms that 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 | Blockchain gas cost optimization is a very specific niche. The trigger terms ('gas prices', 'optimize gas', 'transaction cost') are distinct and unlikely to conflict with other skills unless there's another blockchain-related skill. | 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 highly actionable commands and good progressive disclosure to reference files. Its main weaknesses are some unnecessary inline reference tables that inflate token count, and the lack of validation/verification steps when acting on gas price recommendations. The workflow is more of a command catalog than a guided process with checkpoints.
Suggestions
Move the Supported Chains and Price Tiers tables to a reference file to reduce token usage in the main skill body.
Add a validation step such as 'verify the gas estimate against a live gas tracker before submitting transactions' to improve workflow safety.
Trim the Overview section since the numbered instructions already convey what the tool does.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary elements like the supported chains table (block times, native tokens) and price tier details that could be in a reference file. The overview section restates what the commands already demonstrate. | 2 / 3 |
Actionability | Every instruction provides concrete, copy-paste-ready bash commands with clear flags and options. The available operations are explicitly enumerated, and each command variant is shown with real arguments. | 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 or handling unexpected outputs 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. Core commands are inline while detailed scenarios and error handling are appropriately delegated to reference files. | 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
c8a915c
- 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.