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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

92%

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

The body is a lean, highly actionable command reference with clear sequencing and compact tables, assuming Claude's competence throughout. Its only structural weakness is an orphaned reference file (implementation.md) that is not linked from the overview.

Suggestions

Either link references/implementation.md from the body (e.g. add an 'Implementation' section pointing to it) or remove it from the bundle to avoid an orphaned, undiscoverable reference.

Consider moving the long inline operation list in step 2 into a reference table or file to tighten the overview further.

Add a brief one-line note per command describing when to prefer it, so the sequencing doubles as a decision guide rather than a flat catalog.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — prerequisites, numbered commands, and compact tables — without explaining concepts Claude already knows about gas fees or EIP-1559. The only minor bloat is the long inline operation list in step 2, but it is functional and earns its place.	3 / 3
Actionability	Every operation ships as a concrete, copy-paste-ready bash command with specific flags and arguments (e.g. 'gas_optimizer.py estimate --operation uniswap_v2_swap --all-tiers'), fully executable with no pseudocode.	3 / 3
Workflow Clarity	Seven clearly sequenced, numbered steps each with a concrete command and expected output; these are independent read-only gas queries rather than a fragile batch/destructive process, so unambiguous single-action steps satisfy the bar without validation checkpoints.	3 / 3
Progressive Disclosure	The body points one level deep to clearly signaled reference files (errors.md, examples.md) and an external resources section, but references/implementation.md is an orphaned bundle file never referenced from the body, indicating imperfect content splitting.	2 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, concrete, and complete — it names specific actions, gives natural trigger phrases, and explicitly covers both what the skill does and when to use it. It is clearly distinguishable from other skills and free of vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'analyzing prices, patterns, and timing' — naming the domain and several specific operations rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Optimize blockchain gas costs by analyzing prices, patterns, and timing') and when ('Use when checking gas prices, estimating costs, or finding optimal windows') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides natural phrases users would say — 'gas prices', 'optimize gas', 'transaction cost', 'when to transact' — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Blockchain gas-fee optimization is a clear niche with distinct, domain-specific triggers unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 607d11b

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