architecture-pattern-selector

I spent some time with your architecture-pattern-selector skill and found myself impressed by how you've structured the decision tree—most pattern selection tools either oversimplify or drown you in options, but this one actually guides you through the trade-offs. Your progressive disclosure approach keeps things lean while still delivering real utility, which is exactly why you landed that solid 92.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 92/100, A-territory—that's production-ready. This is based on Anthropic's skill best practices. Your strongest pillar is Utility (20/20, perfect score), which makes sense—you're solving a real problem that teams actually face. The weakest area is Spec Compliance (12/15), which is mostly about trigger phrases in your description and some reference organization minutiae.

What's Working Well

• Decision matrix scoring system - You didn't just list patterns, you built an actual evaluation framework with weighted criteria. That's the difference between a reference doc and a tool that prevents bad architecture decisions.
• Layered structure with depth - SKILL.md stays focused while decision-matrix.md and pattern-comparison.md give people the details they need without bloating the overview. That's solid PDA.
• Strong anti-patterns section - Calling out "You're not Netflix" and other reality checks is exactly what engineers need to hear before they cargo-cult architecture decisions.
• Clear 4-step workflow - The numbered selection framework with specific output templates gives people something actionable to follow.

The Big One

Your description is light on trigger phrases. Right now it's pretty generic about "cto-architect" scenarios,...