360 Secure SkillHub
360 安全技能中心

Compensation

核心功能为薪酬相关的四阶段结构化工作流:明确目标与背景、设计沟通方案、执行验证谈判脚本、落地跟进迭代,配套检查清单覆盖风险与后续动作。典型场景:用户涉及薪酬谈判、录用offer、加薪需求,且需要系统性指导时使用。输入为用户的薪酬诉求与上下文,输出为分阶段可执行方案、风险提示及跟进指引。

clawkk
clawkk
热度 43.40
最近更新 2026-05-11 17:37:19
分类:效率依赖:纯提示词应用场景:个人理财 / 工作流 / 任务管理

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add compensation
Metadata
name
compensation
description
Offers, compensation framing, and negotiation planning. Use when evaluating offers or raises.

Compensation

Structured guidance for offers, pay, and negotiation (not legal or tax advice): confirm triggers, propose the stages below, and adapt if the user wants a lighter pass.

When to Offer This Workflow

Trigger conditions:

  • User mentions negotiation, offers, raises, compensation, or closely related work
  • They want a structured workflow rather than ad-hoc tips
  • They are preparing a review, rollout, or stakeholder communication

Initial offer: Explain the four stages briefly and ask whether to follow this workflow or work freeform. If they decline, continue in their preferred style.

Workflow Stages

Stage 1: Clarify context & goals

Anchor on market context and priorities. Ask what success looks like, constraints, and what must not break. Capture unknowns early.

Stage 2: Design or plan the approach

Translate goals into a concrete plan around total comp components. Compare alternatives and explicit trade-offs; avoid implicit assumptions.

Stage 3: Implement, validate, and harden

Execute with verification loops tied to negotiation script and BATNA. Prefer small steps, measurable checks, and rollback points where risk is high.

Stage 4: Operate, communicate, and iterate

Close the loop with written follow-ups: monitoring, documentation, stakeholder updates, and lessons learned for the next cycle.

Checklist Before Completion

  • Goals and constraints are explicit for compensation discussions
  • Risks and trade-offs are stated, not hand-waved
  • Verification steps match the change’s impact (tests, canary, peer review)
  • Operational follow-through is covered (monitoring, docs, owners)

Tips for Effective Guidance

  • Be procedural: stage-by-stage, with clear exit criteria
  • Ask for missing context (environment, scale, deadlines) before prescribing
  • Prefer checklists and concrete examples over generic platitudes
  • If the user declines the workflow, switch to freeform help without lecturing

Handling Deviations

  • If the user wants to skip a stage: confirm and continue with what they need.
  • If context is missing: ask targeted questions before strong recommendations.
  • Prefer concrete examples, trade-offs, and verification steps over generic advice.

Quality Bar

  • Each recommendation should be actionable (what to do next).
  • Call out failure modes relevant to compensation talks (relationship risk, miscommunication, or unrealistic asks).
  • Keep tone direct and respectful of the user’s time.