viem

I took a look at your viem skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

You're at 80/100 (B Grade)

This is a solid skill with good fundamentals. You're hitting strong marks on Spec Compliance (13/15) and Utility (17/20), which means the core skill is well-structured and actually solves a real problem. The areas holding you back are mostly around refinement—better discoverability and tighter token economy.

What's Working Well

• Strong trigger coverage. You've got both intent triggers ("read from blockchain", "write to blockchain") and artifact patterns with regex—that's good thinking for matching different LLM outputs.
• Solid code examples. The PublicClient/WalletClient setup and waitForTransactionReceipt patterns give LLMs concrete, copyable code to work with. That's exactly what makes a skill useful.
• Clear constraints. You've spelled out what's banned and required (error handling, gas estimation, confirmation waits)—LLMs understand these boundaries well.

The Big One: Missing Migration Trigger

Here's what jumped out: you mention viem replaces ethers.js but have no trigger for it. This is leaving discovery on the table. A lot of developers coming to AI asking "how do I migrate from ethers?" won't find your skill because you don't have that trigger phrase.

Fix: Add to your triggers array:

triggers:
  - 'ethers.js replacement'
  - 'migrate from ethers'
  - 'ethers to viem'

This alone could bump you +1-2 points just by improving Ease of Use (Discoverability).

Other Things Worth Fixing

1. Evolution section is padding. Your "Extension Points and Timelessness" subsections read like forward-looking fluff rather than actionable guidance. Either move this to a reference file or trim it—saves tokens and keeps focus sharp. +2 points potential.

2. Constraints voice inconsistency. You've got "Missing error handling for blockchain operations"—that's a second-person critique mixed with your imperative voice elsewhere. Pick one: either "Omit error handling..." or reframe as noun phrases. Small but it reads cleaner. +1 point.

3. Add a trigger for error handling context. You emphasize it heavily, so add triggers like "blockchain error handling" or "transaction failures"—helps LLMs route to your skill when they're dealing with real-world failure scenarios.

Quick Wins

• Add the three ethers.js migration triggers (biggest bang for buck)
• Trim the evolution section for token efficiency
• Fix the voice inconsistency in constraints
• Consider adding error handling as a trigger

You're in good shape here—these are polish-level fixes that'll push you to 85-87/100 range.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.