How do I install the Clarity skill?

Run npx skillmds@latest add clearmeasurelabs/clarity in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Clarity safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Clarity?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Clarity free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Clarity?

ClearMeasureLabs (@clearmeasurelabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Clarity by clearmeasurelabs — Agent Skill

Name: Clarity
Author: ClearMeasureLabs

Clarity

Checks whether a project, feature, or team is running blind or running with clarity -- Pillar 1 of The Five Pillars (vision, strategy, measurement). Use when kicking off a project, when a team can't agree on why a feature matters, before writing a strategy doc, or as a quarterly health check.

File contents

/clarity -- Create Clarity

Pillar 1 of The Five Pillars. Checks whether a project, feature, or team is running blind or running with clarity.

When to invoke

Kicking off a new project or engagement
A team can't agree on why a feature matters
Before writing a strategy doc, ask this first
Quarterly, as a health check on an ongoing project

What it checks

Vision / Mission / Purpose -- Can the team state, in one sentence, why this software exists and who it serves? Ask 2-3 team members independently; compare answers.
Strategy / Plan -- Is there a written path from today to the vision that goes below the executive/management layer? Has the team had a chance to critique and strengthen it?
Measurement -- Is there a scorecard today, even if some numbers are zero? Is it reported on a fixed cadence (weekly is the book's recommendation)?

Inputs

There's no API for this one -- clarity lives in people's heads, not a system. Source it from whatever is available, in this order of preference:

Direct answers -- ask 2-3 team members the "why does this exist" question yourself (in chat, in a doc, or have the user relay answers) and compare them.
Written artifacts -- a README, strategy doc, project charter, or wiki page pasted in or found in the repo.
Absence -- if neither exists, that absence is the finding for Vision/Strategy; say so rather than guessing.

Example output

Clarity scorecard -- Project Atlas

Sub-pillar Score Finding

Vision 🟡 Yellow 2 of 3 team members gave the same answer ("faster onboarding for new hires"); the third said "whatever the backlog says."

Strategy 🔴 Red No written plan below the PM's head -- engineers can't say what happens after this quarter.

Measurement 🟢 Green Weekly scorecard exists (#atlas-metrics channel), tracking onboarding time-to-first-commit.

Biggest gap: Strategy. Fastest fix: PM writes a one-page plan (this quarter → next → the vision) and reviews it with the team this week, not just the leads.

Draft vision statement (adopt or edit): "Atlas exists so a new engineer can ship their first PR in under a day."

Sub-pillar	Score	Finding
Vision	🟡 Yellow	2 of 3 team members gave the same answer ("faster onboarding for new hires"); the third said "whatever the backlog says."
Strategy	🔴 Red	No written plan below the PM's head -- engineers can't say what happens after this quarter.
Measurement	🟢 Green	Weekly scorecard exists (`#atlas-metrics` channel), tracking onboarding time-to-first-commit.

Reference

See ../../docs/FIVE_PILLARS.md.

---name: claritydescription: Checks whether a project, feature, or team is running blind or running with clarity -- Pillar 1 of The Five Pillars (vision, strategy, measurement). Use when kicking off a project, when a team can't agree on why a feature matters, before writing a strategy doc, or as a quarterly health check.---# /clarity -- Create Clarity**Pillar 1 of The Five Pillars.** Checks whether a project, feature, or team is running blind or running with clarity.## When to invoke- Kicking off a new project or engagement- A team can't agree on why a feature matters- Before writing a strategy doc, ask this first- Quarterly, as a health check on an ongoing project## What it checks1. **Vision / Mission / Purpose** -- Can the team state, in one sentence, why this software exists and who it serves? Ask 2-3 team members independently; compare answers.2. **Strategy / Plan** -- Is there a written path from today to the vision that goes below the executive/management layer? Has the team had a chance to critique and strengthen it?3. **Measurement** -- Is there a scorecard today, even if some numbers are zero? Is it reported on a fixed cadence (weekly is the book's recommendation)?## InputsThere's no API for this one -- clarity lives in people's heads, not a system.Source it from whatever is available, in this order of preference:1. **Direct answers** -- ask 2-3 team members the "why does this exist" question yourself (in chat, in a doc, or have the user relay answers) and compare them.2. **Written artifacts** -- a README, strategy doc, project charter, or wiki page pasted in or found in the repo.3. **Absence** -- if neither exists, that absence *is* the finding for Vision/Strategy; say so rather than guessing.## Example output> **Clarity scorecard -- Project Atlas**>> | Sub-pillar | Score | Finding |> | --- | --- | --- |> | Vision | 🟡 Yellow | 2 of 3 team members gave the same answer ("faster onboarding for new hires"); the third said "whatever the backlog says." |> | Strategy | 🔴 Red | No written plan below the PM's head -- engineers can't say what happens after this quarter. |> | Measurement | 🟢 Green | Weekly scorecard exists (`#atlas-metrics` channel), tracking onboarding time-to-first-commit. |>> **Biggest gap:** Strategy. **Fastest fix:** PM writes a one-page plan (this quarter → next → the vision) and reviews it with the team this week, not just the leads.>> **Draft vision statement (adopt or edit):** "Atlas exists so a new engineer can ship their first PR in under a day."## ReferenceSee [../../docs/FIVE_PILLARS.md](../../docs/FIVE_PILLARS.md#pillar-1-create-clarity----dont-run-your-project-blind).

Frequently asked questions