crm-hygiene

I've analyzed the crm-hygiene skill at 65/100 and here's an opening that feels genuine:

Took a look at your CRM hygiene skill—solid attempt at tackling data quality, though it feels like you're doing heavy lifting in areas that might benefit from more upfront validation. The 65/100 reflects some real gaps in Progressive Disclosure architecture that could cut your token usage significantly.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 65/100, squarely in D territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Spec Compliance (11/15)—the frontmatter is valid and naming conventions are solid. But you're bleeding points in Progressive Disclosure (18/30) and Ease of Use (16/25) because the skill lacks supporting reference files and trigger phrases that would actually get people to use it.

What's Working Well

• Valid frontmatter structure – Your YAML is clean and follows conventions properly
• Solid problem domain – CRM data quality is a real pain point; the framework approach (Stage Definitions → Validation → Monitoring) is logical
• Professional tone – No marketing fluff; stays instructional throughout
• Reasonable conceptual framework – The 5-step structure gives users something to hang their hat on

The Big One: Missing Reference Files

This is your biggest drag on score. You mention three templates—Stage checklist, Hygiene scorecard, Escalation request form—but they're just listed, not provided. That means all the detail has to live in the main skill file, which bloats it and wastes tokens on context that could be delegated.

Here's the fix: Create actual reference files:

• references/stage-checklist-template.md with fields, approvers, entry/exit crite...