financial-product-blueprint

I took a look at your financial-product-blueprint skill, and I'm curious about the approach—with a 59/100 score, there's clearly some solid foundational thinking here, but I'm wondering if the spec compliance and progressive disclosure could be tightened up to make this more production-ready for teams that need to move fast on financial modeling.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 59/100, F territory. This is graded against Anthropic's best practices for agentic skills. Your strongest area is Writing Style (8/10)—the tone is clean and professional. The real drag is Utility (10/20) and Progressive Disclosure Architecture (15/30). The core problem: you're trying to cram a complex framework into 32 lines without depth layers or concrete examples, which makes it hard for developers to actually use this.

What's Working Well

• Solid foundational structure — Your five-area framework (Product Overview, Pricing, Compliance, Operational Hooks, Templates) is logically organized and covers the right domains
• Clean writing voice — Mostly imperative and factual; no marketing fluff. Keeps the focus on execution
• Valid YAML frontmatter — Metadata is properly formatted with required fields in place
• Financial domain specificity — You're clearly thinking about real pain points (versioning, CRM sync, compliance)

The Big One: Missing Reference Files & Concrete Templates

This is your biggest bang-for-buck fix. Right now, everything's compressed into SKILL.md with no external depth layers. You mention "Rate card + incentive tracker" and "Product fact sheet" but provide zero actual templates or examples. When a developer invokes this skill, they get conceptual guidanc...