Use to assemble rate tables, accelerator logic, and plan governance templates.
Scanned 2/12/2026
Install to Claude Code
npx -y skills add gtmagents/gtm-agents --skill comp-mechanics --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Comp Mechanics?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/gtmagents-comp-mechanics)More formats (shields.io, HTML) on the badges page.
---
name: comp-mechanics
description: Use to assemble rate tables, accelerator logic, and plan governance templates.
---
# Compensation Mechanics Toolkit Skill
## When to Use
- Creating or refreshing comp plans during annual planning.
- Evaluating SPIFs or new incentive structures mid-year.
- Responding to finance/legal requests for documentation.
## Framework
1. **Plan Components** – outline quota basis, crediting rules, accelerators, caps, clawbacks.
2. **Rate Tables** – define payout rates by attainment band and attach accelerators/decels.
3. **Governance Checkpoints** – approvals, policy references, audit requirements.
4. **Communication Assets** – FAQs, plan summaries, change logs.
5. **Monitoring Hooks** – dashboards, variance alerts, and attestation cadence.
## Templates
- Compensation plan summary one-pager.
- Accelerator rate table spreadsheet.
- Governance checklist with approvals and deadlines.
## Tips
- Keep variable definitions consistent across roles to avoid confusion.
- Document all exceptions and approvals for audit readiness.
- Pair with `quota-health` to validate behavioral alignment.
---
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Create Mermaid diagrams for flowcharts, sequences, ERDs, and
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.
Diagnose stalled, looping, or over-recovered Paperclip issue trees and propose a no-code product-rule plan. Use when asked why work stopped, why it looped, or how to prevent a tree from going too deep.