quota-health

I was curious about quota management when I ran into your skill—it takes a practical approach to a problem that doesn't get enough attention in most systems. At a 61/100, there's solid foundation here, but I'd like to dig into how the implementation handles edge cases around quota exhaustion and recovery.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 61/100, which lands you in D territory. This evaluation is based on Anthropic's best practices for agentic skills. Your Spec Compliance is your strongest area (11/15)—the YAML frontmatter is clean and follows conventions. But Utility is dragging things down (10/20) because the framework lacks the concrete operational details needed to actually run this thing.

What's Working Well

• Clear structure – Five-step framework (Data Collection → Fairness Analysis → Signal Review → Dashboard/Recommendations → Governance) gives reps a logical path through quota analysis
• Real problem – You're addressing quota distribution fairness, which is genuinely underexplored in most sales ops workflows
• Consistent terminology – Quota, attainment, coverage, territory—terms stay consistent throughout, which helps clarity

The Big One: Missing Reference Files & Templates

This is your main blocker. You mention templates in lines 21–24 (quota health dashboard, CRO briefing outline, quota adjustment form) but don't actually provide them. That's a massive gap because without templates, someone using this skill has to reverse-engineer what you mean by "dashboard" or "CRO briefing."

The fix: Create a references/ directory with:

• quota-health-dashboard.md – actual KPI layout, quartile definitions, sample output
• cro-briefing-template.md – structured outline with risk/opportunity sections
• quota-adjustment-form.md – approval workflow, affected parties, comp plan constraints

This alone should net you +5 points and move Utility from 10/20 to 15/20.

Other Things Worth Fixing

1. Data collection step is vague – "Pull attainment, pipeline, coverage, territory metrics" doesn't tell you where or how. Specify Salesforce queries, API calls, or database schema. What's the exact WHERE clause? This adds utility and ease of use. (+3 points)

2. Gini coefficient mentioned but unexplained – You reference it in the fairness analysis but never define the formula, calculation thresholds, or what scores mean. Create references/fairness-metrics.md with the math and interpretation guides (e.g., <0.2 = fair, >0.35 = unfair). (+4 points)

3. No validation or feedback loop – Step 5 (Governance) mentions logging changes but doesn't explain approval workflows, rollback plans, or how to validate adjustments didn't break comp plans. Add a checklist: Finance approval → validate constraints → communicate → monitor first month → adjust if needed. (+3 points)

4. Description needs trigger phrases – "Use to analyze quota distribution, attainment fairness, and productivity signals" doesn't include keywords users would actually say. Add triggers like "quota balance", "fair distribution", "over-assigned reps". (+2 points)

Quick Wins

• Add references/ directory with three templated files → +12 points
• Specify Salesforce queries in data collection step → +3 points
• Define Gini thresholds and interpretation → +4 points
• Include approval/validation workflow in governance step → +3 points
• Update description with trigger phrases → +2 points

These four changes could push you from 61 to 85+ pretty quickly.

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