scalability-advisor

I found your scalability-advisor skill while reviewing distributed systems tooling—the way you've structured the guidance around architectural patterns rather than just optimization tricks is genuinely useful. Scored it an 83, and I think the main lift for a 90+ would be tightening up the PDA structure to reduce token overhead in the explanatory sections.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 83/100, solid B territory. This evaluation's based on Anthropic's skill best practices—specifically looking at Progressive Disclosure Architecture, ease of use, spec compliance, writing style, and utility. Your strongest area is Writing Style (9/10)—the content is concise and technically sound. Weakest is PDA (18/30)—mostly because you've packed everything into one 466-line file instead of using a layered reference structure.

What's Working Well

• Trigger phrase specificity: You nailed the discovery angle with concrete scenarios like "planning growth," "diagnosing bottlenecks," and "10x-1000x load changes." That's exactly how developers search for skills.
• Stage-based framework: Breaking scaling into Startup → Growth → Scale stages with clear metrics (10k users, 100k users, etc.) makes it actionable rather than abstract advice.
• Copy-paste ready content: Your SQL queries, formulas, and ASCII architecture diagrams are genuinely useful—the kind of thing someone can actually use without modification. That earned you a +2 bonus.
• Decision criteria: Each "When to Move to Stage X" section has concrete thresholds. That's rare and valuable.

The Big One: Missing Reference Files Breaking PDA

Your SKILL.md references two files that don't exist:

• bottleneck-diagnosis.md
• `capacity-calculator.md...