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 guidance but nothing they can immediately execute.

The fix: Create three reference files:

• references/product-fact-sheet-template.md — actual markdown table with fields (Name, Eligibility, Features, Terms)
• references/pricing-calculator-example.md — sample rate card with scenario modeling
• references/compliance-checklist.md — step-by-step validation criteria

Link these from SKILL.md as "See example pricing table". This moves you from 15/30 to ~25/30 on PDA and adds ~3 points to Utility.

Other Things Worth Fixing

1. Add trigger phrases to the description — Currently: "Template for packaging financial products..." Change to: "Use when asked to 'create product blueprint', 'build rate card', 'document underwriting policy', or 'structure lending/payments product'." (+2 points on Spec Compliance)

2. Define your terminology hierarchy — You use "blueprint," "fact sheet," "pack," and "card" interchangeably. Open with: "Blueprint = comprehensive document containing (1) Product Fact Sheet, (2) Rate Card, (3) Enablement Pack." Removes confusion. (+3 points on Ease of Use)

3. Add validation steps — After the framework, include: "Quality Checks: (1) Pricing accuracy verified by Finance, (2) Legal review of disclosures, (3) CRM field mapping tested, (4) Expiration dates < 12 months." This gives users a feedback loop. (+3 points on Utility)

Quick Wins

1. Create three reference files with actual templates (biggest ROI—+10 points)
2. Add trigger phrases to frontmatter description (+2 points)
3. Define terminology hierarchy in opening (+3 points)
4. Add validation/quality check section (+3 points)

These four changes alone would bump you from 59 to ~77/100.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.