tech-stack-recommender

I've been poking around tech stack selection problems lately, and I see you're tackling the decision-making side of it—how did you land on this particular approach for guiding those choices?

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 70/100, solidly in C territory. This is based on Anthropic's skill grading rubric across five pillars. Your strongest area is Spec Compliance (12/15)—the frontmatter and naming are clean. Weakest area is Progressive Disclosure Architecture (15/30)—you're packing 448 lines into a single file when you could be more strategic about layering content.

What's Working Well

• Clear decision framework (lines 20-41) with ASCII diagrams showing inputs and outputs—this actually gives people a visual anchor for how to use the skill
• Excellent stack templates (lines 187-307) that show real-world examples for SaaS, e-commerce, and enterprise scenarios—people can see themselves in these
• Strong metadata and triggers in the frontmatter—terms like "selecting frameworks," "language selection," and "infrastructure choices" are solid discovery hooks
• Practical evaluation checklist (lines 327-348) that gives people a way to validate their choice after the fact

The Big One: Missing Reference Files

You're listing two reference files that don't actually exist: framework-comparison.md and migration-playbooks.md (lines 444-447). This is a PDA violation because you're claiming a layered structure you haven't actually built.

Here's the fix: Either create those files and move your detailed comparison content into them, or remove the References section. If you go with creating them, you'd move those 4 stack templates (120 lines of repetition) into `references/stack-tem...