Token导航 LogoToken导航

Agent Skill · 待分类

sales-compensation(销售报酬)

sales-compensation 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

sales-compensation 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 4,182。

总安装 792周安装 34GitHub Stars 3下载 277核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:sales-compensation(销售报酬)
来源仓库:https://github.com/oldwinter/skills
仓库路径:skills/sales-compensation
安装命令:
npx skills add https://github.com/oldwinter/skills --skill sales-compensation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill sales-compensation

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

用于处理 GitHub 仓库、Issue 和 Pull Request 协作信息。适合围绕代码变更和仓库状态进行整理与分析。可结合来源仓库 README 核验具体用法和权限范围。安装前建议确认是否会触发命令执行或文件读写操作。sales-compensation 属于待分类类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/sales-compensation

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/oldwinter/skills --skill sales-compensation;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

sales-compensation 怎么安装?

在终端执行 npx skills add https://github.com/oldwinter/skills --skill sales-compensation。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

sales-compensation 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

sales-compensation 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

sales-compensation 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

sales-compensation 用的人多吗?

公开数据是累计安装 792 次,近一周安装 34 次,下载 277 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

sales-compensation 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
sales-compensation

销售报酬 · 本页

7923只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Sales Compensation

Scope

Covers

  • Designing compensation plans for revenue roles (typically SDR/BDR, AE, AM/CSM with expansion)
  • Setting OTE, base/variable mix, quota, and ramp
  • Defining commission mechanics (crediting rules, accelerators, clawbacks, payout timing)
  • Aligning incentives with long-term customer value (retention / NRR), not just bookings
  • Producing rep-facing plan docs + admin rules so payouts are actually operable

When to use

  • “Design a comp plan for our first AEs/SDRs.”
  • “What should our OTE and base/variable split be?”
  • “Set quotas and a ramp plan for new reps.”
  • “Create accelerators + rules so reps don’t game discounting.”
  • “Our reps close bad-fit deals that churn—align comp with retention/NRR.”

When NOT to use

  • You need legal/tax/HR advice, employment compliance guidance, or jurisdiction-specific plan language (use qualified professionals)
  • You’re designing executive compensation or equity plans (different problem)
  • You don’t yet have basic GTM foundations (ICP, pricing, what counts as a closed-won) — do that first, then return
  • You want an overly complex “formula soup” plan that can’t be explained in one page or administered reliably

Inputs

Minimum required

  • Company stage + GTM motion (inbound/outbound/PLG/enterprise) and primary sales roles
  • What you sell + pricing model + typical ACV/ARR and sales cycle length
  • Your economic constraints: gross margin, CAC payback target (or runway), budget for sales comp
  • Target outcomes for the period (bookings/revenue/NRR) and the time horizon you care about (e.g., 90-day retention, annual renewals)
  • Current baseline (if any): pipeline conversion, win rate, ramp time, churn/NRR
  • Constraints: simplicity tolerance, payout timing preference, risk tolerance (for the company and for reps)

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md, then proceed.
  • If key data is missing, make explicit assumptions and include:

- Assumptions & unknowns - Sensitivity ranges (e.g., quota/rates under low/base/high scenarios) - Validation plan (what to measure in the next 30–90 days)

Outputs (deliverables)

Produce a Sales Comp Plan Pack in Markdown (in-chat; or as files if requested), in this order:

  1. Context snapshot (roles, stage, goals, constraints, time horizon)
  2. Comp philosophy (what behaviors you want; what you want to prevent)
  3. Role → metric mapping (what gets paid on, and why it’s controllable)
  4. OTE + pay mix table (base/variable split by role + rationale)
  5. Quota + ramp model (quota by period + ramp schedule + any draw/guarantee)
  6. Commission mechanics spec (crediting, rates, accelerators, splits, discount policy, payout timing, clawbacks)
  7. Retention-alignment addendum (choose one approach; define measurement + timing)
  8. Admin & governance (required CRM fields, payout process, disputes, exceptions, change control)
  9. Rep-facing one-pager + FAQ (copy/paste)
  10. Risks / Open questions / Next steps (always included)

Templates: references/TEMPLATES.md

Workflow (7 steps)

1) Intake + plan boundaries (what problem are we solving?)

  • Inputs: User context; references/INTAKE.md.
  • Actions: Confirm roles in scope, selling motion, time horizon (bookings vs retention), budget constraints, and “must-not” behaviors (discounting, churny deals, channel conflict). Identify what data you do/don’t have.
  • Outputs: Context snapshot + assumptions/unknowns + decision on time horizon.
  • Checks: Success is measurable (who/what/by when) and the plan scope is explicit.

2) Define role responsibilities + “what gets paid on”

  • Inputs: Role definitions; pipeline stages; revenue recognition basics; retention model.
  • Actions: Choose 1 primary performance metric per role (e.g., ARR bookings, qualified meetings, expansion ARR, gross profit). Define “crediting” rules (when a deal counts, splits, renewals).
  • Outputs: Role → metric mapping + crediting rules draft.
  • Checks: The metric is (a) measurable, (b) attributable, and (c) reasonably controllable by the rep.

3) Set OTE + base/variable mix (pay risk where it belongs)

  • Inputs: Talent market bands (if known), role seniority, sales cycle, role risk, stage.
  • Actions: Set OTE targets and the base/variable mix per role. Choose a default mix (often ~50/50 for many AE roles) and adjust based on cycle length, product maturity, and expected rep autonomy.
  • Outputs: OTE + pay mix table with rationale and guardrails.
  • Checks: OTE is economically viable for the business and believable to candidates; pay mix matches controllability and sales cycle length.

4) Build quota + ramp model (make “on target” realistic)

  • Inputs: Targets; baseline conversion (or assumptions); expected ramp time; territory/segment definitions.
  • Actions: Create a quota model (top-down + bottom-up cross-check). Define ramp schedule, draw/guarantee (if used), and what happens if the plan changes mid-year.
  • Outputs: Quota + ramp tables (low/base/high scenarios).
  • Checks: A rep at OTE can realistically hit quota with the assumed pipeline and conversion.

5) Define commission mechanics (simple, compute-able, enforceable)

  • Inputs: OTE/Quota; metric definitions; discount/margin constraints.
  • Actions: Set rates, accelerators/decelerators, and payout timing. Add guardrails: discount approval thresholds, deal qualification minimums, splits/overlays, clawbacks/chargebacks, and edge-case rules.
  • Outputs: Commission mechanics spec + 2–3 worked payout examples.
  • Checks: A Sales Ops/admin can calculate payouts from CRM data without manual interpretation.

6) Add retention/quality alignment (avoid paying for churn)

  • Inputs: Retention/NRR goals; churn timing; implementation/onboarding reality; data availability.
  • Actions: Choose one retention-alignment approach (e.g., partial holdback until 90 days, commission adjustment on early churn, pay on collected revenue, or NRR multipliers). Define measurement windows and how disputes are handled.
  • Outputs: Retention-alignment addendum (chosen approach + rationale + admin rules).
  • Checks: The approach is understandable to reps and proportional to their influence on retention.

7) Quality gate + finalize (rep-ready + admin-ready)

  • Inputs: Draft pack.
  • Actions: Run references/CHECKLISTS.md and score using references/RUBRIC.md. Produce the rep-facing one-pager + FAQ. Always include Risks / Open questions / Next steps and a 30–90 day validation plan.
  • Outputs: Final Sales Comp Plan Pack.
  • Checks: The plan can be explained in one page, computed from CRM fields, and aligns incentives with business + customer outcomes.

Quality gate (required)

Examples

Example 1 (first AE comp plan, seed-stage SaaS): “Use sales-compensation. We’re seed-stage B2B SaaS, $12k ACV, 45-day cycle. Hiring first 2 AEs. Goal: $600k ARR this year. Output: a Sales Comp Plan Pack with OTE/pay mix, quotas+ramp, commission mechanics, and a rep-facing FAQ.”

Example 2 (retention-aligned comp, churn problem): “Use sales-compensation. Reps optimize for bookings and we churn in the first 90 days. We want comp to reflect retention/NRR without being overly complex. Output: a Sales Comp Plan Pack with a retention-alignment addendum and clear admin rules.”

Boundary example: “Write a legally binding compensation agreement for California employees and tell me what’s compliant.” Response: explain this skill produces a comp-plan spec and rep-facing materials, but legal/compliance review must be done by qualified counsel.

平台分布

Codex

36.97%
按下载量换算102

Claude

26.73%
按下载量换算74

Cursor

18.21%
按下载量换算50

Gemini CLI

9.86%
按下载量换算27

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills