# Values Check

> Pressure-tests a decision, plan, or piece of client-facing work against Clear Measure's core values before you commit to it. Use before finalizing a client proposal, staffing decision, or scope change, when a decision "feels off," or when onboarding a new hire to how decisions get made.

- Skill: `clearmeasurelabs/values-check` (Agent Skill)
- Install (CLI): `npx skillmds@latest add clearmeasurelabs/values-check`
- Raw SKILL.md: https://api.skillmd.com/api/skills/clearmeasurelabs/values-check/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ClearMeasureLabs (https://skillmd.com/u/clearmeasurelabs)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/clearmeasurelabs/values-check

---


# /values-check -- Clear Measure Values Check

Pressure-tests a decision, plan, or piece of client-facing work against Clear Measure's core values before you commit to it.

## When to invoke

- Before finalizing a client proposal, staffing decision, or scope change
- When a decision "feels off" but you can't articulate why
- Onboarding a new hire to how Clear Measure expects decisions to be made

## What it checks

For the decision or plan under review, walk through each value and ask the associated question:

- **Serving Others First** -- does this put the client's/teammate's interest ahead of ours where they conflict?
- **Empowered Employees** -- does this equip people to do their best work, or does it route every decision through one person?
- **Building Relationships** -- does this build trust, or does it trade trust for short-term speed?
- **Excellence** -- does this meet Clear Measure's bar, or does it just meet the minimum?
- **Authenticity** -- can we say this plainly to the client/team, or does it require spin?
- **Trusted Partner** -- would we be comfortable with the client seeing exactly how this decision was made?

## Inputs

- **The decision or plan itself** -- the user pastes the proposal, staffing plan, or scope-change text directly; this skill doesn't pull from a tracker, it evaluates whatever text it's given
- If the plan only exists verbally, ask the user to state it in a sentence or two first -- don't infer the plan from surrounding conversation

## Example output

> **Values check -- proposal to bill this sprint's bug fixes as a new feature**
>
> | Value | Result |
> | --- | --- |
> | Serving Others First | 🚩 Flag -- this favors our billing convenience over the client's accurate understanding of what they're paying for. |
> | Empowered Employees | ✅ Pass |
> | Building Relationships | 🚩 Flag -- if the client later notices, this trades short-term revenue for long-term trust. |
> | Excellence | ✅ Pass |
> | Authenticity | 🚩 Flag -- we would not want to explain this line item plainly to the client. |
> | Trusted Partner | 🚩 Flag |
>
> **Concrete change to resolve:** Bill the fixes under a "defect remediation" line item at the agreed support rate, and note in the client update which defects were pre-existing vs. newly introduced this sprint.

## Reference

See [../../docs/VALUES.md](../../docs/VALUES.md) or [clearmeasure.com/about-us/our-values](https://clearmeasure.com/about-us/our-values/).