aws-solution-architect

I checked out your AWS Solution Architect skill and noticed the grading came in at 66/100 — there's a solid foundation here, but I'm curious what trade-offs you made between comprehensive coverage and keeping the documentation maintainable at this scope.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 66/100, D territory — based on Anthropic's best practices for agentic skills. Your strongest area is Spec Compliance (11/15), but Writing Style is dragging you down hard at just 4/10. The core issue isn't that your content is bad — it's that you're treating this like a reference manual when it should be a focused, actionable guide.

What's Working Well

• Solid spec foundation — Your frontmatter is valid YAML with all required fields, and you're using proper naming conventions (hyphen-case). That's the baseline done right.
• Real AWS expertise — The architecture patterns and service selection show you actually know your stuff. Cost breakdowns and trade-offs feel grounded in real experience.
• Helpful layering attempt — Your HOW_TO_USE.md file shows you understand that progressive disclosure matters; you just need to push that idea further into the main skill.

The Big One: SKILL.md is 345 Lines of Bloat

This is your main bottleneck. You've got 6 detailed architecture patterns, extensive best practices, service catalogs, and cost estimates all crammed into the primary file. That's not a skill guide — that's an AWS reference manual.

Why it matters: Every line dilutes the signal. When someone asks Claude to use your skill, they get 345 lines to parse when they probably need 10-15 actionable steps. You're burying the workflow in encyclopedia content.

The fix: Move those 6 arc...