solidity

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

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 79/100, solidly in C territory (70-79 range). This is based on Anthropic's skill best practices framework. Your strongest area is Ease of Use at 22/25—the metadata and trigger coverage are really solid. The weakness is Progressive Disclosure Architecture at 19/30, which is about how efficiently you're using tokens and structuring content for layered discovery.

What's Working Well

• Trigger coverage is chef's kiss — You've got regex patterns for .sol files, pragma statements, ERC standards, and specific security tools. Developers will actually find this skill when they need it.
• Security-first design — The CEI pattern enforcement, NatSpec requirements, and security checklist with actual checkboxes make this genuinely useful for the domain. Real value here.
• Complete contract template — You're not just explaining concepts; you've got a working example with comments. That's the kind of thing that saves time.
• Consistency throughout — You're using the same terminology (CEI, NatSpec, forge) consistently, so developers aren't confused about different ways to do the same thing.

The Big One: Duplicate Content Wasting Tokens

Here's what's holding you back the most: You're listing Trail of Bits skills twice — once in <security_tools> and again in <related_skills> with nearly identical descriptions. In a 299-line skill, that's meaningful token waste.

Why it matters: Progressive Disclosure Architecture rewards dense, non-redundant content. Duplication signals poor information architecture.

The fix: Keep the Trail of Bits skills in <related_skills> only. Then in <security_tools>, just reference them: "See for Trail of Bits security tooling." This gets you +3 points and makes the skill more maintainable.

Other Things Worth Fixing

1. Add a table of contents — At 299 lines, you need explicit navigation. Add a <!-- TOC --> after the frontmatter listing your XML sections. This is a quick +2 points and makes the skill way easier to scan. Files over 100 lines really benefit from this.

2. Convert quick_start to checkbox format — Your workflow is numbered (1. Create contract... 2. Import...), but the security_checklist already uses checkboxes. Be consistent: - [ ] Create contract with SPDX license and pragma. Gives developers a completion tracking tool. +1 point.

3. Extract advanced patterns to references — Things like upgradeable contracts or ERC implementations could live in a references/ directory instead of inline. Keeps the main file lean and lets developers dive deep if they want. +2 points.

Quick Wins

Priority order for impact:

• Remove duplicate Trail of Bits content (+3 points)
• Add TOC for navigation (+2 points)
• Move advanced patterns to references (+2 points)
• Checkbox-ify the workflow (+1 point)

Those four changes would likely push you to 87/100 and solid B territory.

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.