quota-health
Use to analyze quota distribution, attainment fairness, and productivity signals.
Profile →npx skills add majiayu000/claude-skill-registry --skill quota-health-gtmagents-gtm-agents-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Quota Health Review Skill ## When to Use - During annual planning to align quotas with territory potential. - Mid-year to diagnose underperformance risks or over-assignment. - Before launching compensation plan changes or SPIFs. ## Framework 1. **Data Collection** – pull attainment, pipeline, coverage, and territory metrics by rep/segment. 2. **Fairness Analysis** – compute attainment distribution, Gini coefficient, and coverage ratios. 3. **Signal Review** – identify chronic over/under assignments, ramp issues, or constrainted territories. 4. **Recommendation Engine** – suggest quota rebalancing, enablement, or hiring adjustments. 5. **Governance** – log proposed changes, approval needs, and communication strategy. ## Templates - Quota health dashboard (rep-level KPIs, quartiles, recommendations). - CRO briefing outline with risks/opportunities. - Quota adjustment request form with approvals. ## Tips - Pair with `territory-optimization` outputs to ensure coverage and quota stay in sync. - Normalize attainment for ramping reps to avoid skewed fairness scores. - Keep change logs auditable for finance and legal. ---
- When to Use
- Framework
- Templates
- Tips
What does the quota-health skill do?
Use to analyze quota distribution, attainment fairness, and productivity signals.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill quota-health-gtmagents-gtm-agents-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.