compliance-statement-library

I found your compliance library while reviewing skill implementations — the idea of standardizing compliance statements across different regulations is genuinely useful, but the execution feels like it's caught between being a reference tool and an active validator, which is dragging the overall score down to 70.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

TL;DR

You're at 70/100, C grade — solid fundamentals, but there are some clear friction points keeping you from the B range. This is based on Anthropic's skill grading standards across five pillars: Progressive Disclosure, Ease of Use, Spec Compliance, Writing Style, and Utility.

What's strong: Your writing style scores an 8/10 — the tone is professional and instructional throughout. Spec compliance is solid at 11/15 with valid YAML frontmatter and proper naming conventions.

What's dragging it down: Utility is 14/20 because your templates are described but not actually provided, and there's no validation workflow. Ease of Use is 18/25 because the skill lacks trigger phrases in the description and doesn't have a clear step-by-step workflow.

What's Working Well

• Professional compliance tone — you maintain objectivity throughout without marketing fluff, which is exactly what financial services needs
• Clear conceptual framework — the five elements (Disclosure Record Form, Statement Metadata, Usage Guidelines, Localization Requirements, Change Tracking) are well-structured
• Proper naming conventions — kebab-case format and valid YAML frontmatter follow the standards

The Big One: No Actual Template Content

This is your main friction point. You describe three template types but don't provide the actual structure or...