cost-estimator

I was curious how you'd approach cost estimation for LLM applications—there's a lot of variables to juggle. Your skill handles the complexity pretty cleanly, though the Progressive Disclosure could be tightened up to save tokens in the common path.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 81/100, solid B territory. This is based on Anthropic's skill best practices. Your strongest area is Writing Style (9/10)—clean, objective, no marketing fluff. The weakest link is Progressive Disclosure Architecture (18/30)—you've got good content, but it's all crammed into one 438-line file without the supporting structure that saves tokens and improves navigation.

What's Working Well

• Metadata is locked in — Your description nails the trigger phrases (planning budgets, build vs buy, TCO analysis), so users will find this when they need it
• Practical templates — The Project Budget Template and Quick Estimate sections give people a real starting point, not just theory
• Solid pricing foundations — Including concrete AWS/GCP pricing tables makes this immediately useful for actual estimation work
• Consistency — TCO, infrastructure costs, and development cost frameworks stay consistent throughout; no terminology confusion

The Big One: Missing Reference Files

Your references section mentions cloud-pricing.md and build-vs-buy.md (line 436-437), but these files don't exist. This is a -5 point hit because it breaks the Progressive Disclosure chain—you're promising layered detail that never materializes.

Fix: Either create those two files and move your detailed pricing tables (currently 77 lines, lines 44-121) into cloud-pricing.md, or strip the references section. If you go the file route, keep ...