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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill optimizing-gas-fees88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 with strong trigger term coverage and explicit 'Use when' guidance. The main weakness is that the capabilities could be more specific about concrete actions (e.g., 'compare gas across networks', 'predict optimal transaction windows', 'calculate fee estimates'). Overall, it effectively communicates its purpose and when to use it.
Suggestions
Expand specificity by listing concrete actions like 'compare gas prices across networks, predict optimal transaction windows, calculate fee estimates in USD'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (blockchain gas costs) and some actions (analyzing prices, patterns, timing), but lacks comprehensive concrete actions like specific optimization techniques or what outputs it produces. | 2 / 3 |
Completeness | Clearly answers both what (optimize blockchain gas costs by analyzing prices, patterns, timing) and when (explicit 'Use when...' clause with specific triggers and a 'Trigger with phrases' section). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'gas prices', 'optimize gas', 'transaction cost', 'when to transact', plus implicit terms like 'checking gas prices', 'estimating costs', 'optimal windows'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on blockchain gas optimization with distinct triggers like 'gas prices' and 'transaction cost' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%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, actionable skill with excellent conciseness and clear command examples. The content appropriately delegates detailed error handling and examples to reference files. The main weakness is the lack of explicit validation steps or feedback loops for verifying gas estimates before proceeding with transactions.
Suggestions
Add a validation step after cost estimation (e.g., 'Verify the estimate looks reasonable before proceeding with transaction')
Include a brief workflow showing how to check current prices, estimate, then decide whether to proceed or wait for optimal window
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting only necessary information without explaining basic concepts Claude already knows. Tables and command examples are compact and informative. | 3 / 3 |
Actionability | Every section provides copy-paste ready bash commands with clear flags and options. The available operations list and chain support table give concrete, executable guidance. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no validation checkpoints or feedback loops for error recovery. For operations involving real transactions and costs, explicit verification steps would improve reliability. | 2 / 3 |
Progressive Disclosure | Content is well-organized with a clear overview, structured sections, and appropriate references to external files (errors.md, examples.md) for detailed information. Navigation is straightforward with one-level-deep references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.