Skip to content
Back to skills

Compensation

ASecurity

Offers, compensation framing, and negotiation planning. Use when evaluating offers or raises.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
testinggodocumentation

Works with

  • cli

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned October 6, 2026

npx -y skills add aAAaqwq/openclaw-team --skill compensation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Compensation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Compensation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aaaaqwq-compensation/badge)](https://www.skillsdirectory.com/skills/aaaaqwq-compensation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.

Files in this skill

  • .clawhub/origin.json144 B
  • SKILL.md2.6 KB
  • _meta.json131 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…