New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Clarify

by umputun in umputun/cc-thingz

This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality.

MITAuto-check passedAgent Workflows

Install Clarify

skills CLI
$ npx skills add umputun/cc-thingz --skill clarify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install umputun/cc-thingz clarify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/umputun/cc-thingz.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/workflow/skills/clarify .claude/skills/clarify && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
clarify
GitHub stars
484
Token cost
~2.1k tokens
SKILL.md length
1,007 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality.

  • Works in 5 steps: Identify the Confusion → Investigate → Explain (Gently) → …
  • Appears confused
  • SKILL.md covers Activation Triggers, Important Context, Workflow and Response Format, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Clarify is an agent skill from umputun/cc-thingz. This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality. Triggers on phrases like "I don't understand", "this doesn't make sense", "confused", "wait, shouldn't it...", "why is this happening", "I thought X did Y", contradictory statements, or frustration signals. Analyzes the confusion, explains the actual behavior, and determines if there's a real issue to address.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: various things for claude code. The licence is MIT.

When your agent uses it

  • Appears confused
  • Shows misalignment between expectations and reality
  • Phrases like I dont understand
  • This doesnt make sense

Example prompts

  • “t understand”
  • “this doesn”
  • “confused”
  • “/clarify”

Requirements

  • Pre-approved tools (allowed-tools): EnterPlanMode, AskUserQuestion

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify the Confusion
  2. Investigate
  3. Explain (Gently)
  4. Assess
  5. Plan the Fix (for real issues)

What it can do on your machine

Read from SKILL.md and the folder at commit 99e1c8d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • EnterPlanMode
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Clarify loads about 2.1k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 1,007 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~110
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from umputun/cc-thingz at commit 99e1c8d, republished under its MIT licence (© umputun). 1,007 words, ~2,116 tokens.

Download SKILL.mdSave it as .claude/skills/clarify/SKILL.md (or your agent's skills folder).
name
clarify
description
This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality. Triggers on phrases like "I don't understand", "this doesn't make sense", "confused", "wait, shouldn't it...", "why is this happening", "I thought X did Y", contradictory statements, or frustration signals. Analyzes the confusion, explains the actual behavior, and determines if there's a real issue to address.
allowed-tools
EnterPlanMode, AskUserQuestion

Clarify

Handle user confusion by verifying intent, explaining actual behavior, and determining if there's a real issue.

Primary goal: Clarify and explain, not fix. Most confusion stems from misunderstanding or forgetting, not from bugs.

Activation Triggers

  • "confused", "I'm confused", "this is confusing"
  • "I don't understand", "doesn't make sense", "makes no sense"
  • "wait, shouldn't it...", "but I thought..."
  • "why is this happening", "why does this..."
  • "I expected X but got Y"
  • "this is wrong", "something's off"
  • frustration signals, contradictory statements
  • questions that reveal misconceptions about system behavior

Important Context

Users often:

  • Work on multiple projects in parallel and may confuse behaviors between them
  • Forget how things were implemented especially after time away
  • Have outdated mental models based on old versions or different projects
  • Mix up similar concepts from different codebases or frameworks

But also:

  • Users are experienced developers - their instincts are often correct
  • Real bugs exist - about half of confusion cases point to actual issues
  • User expectations are reasonable - if something feels wrong, investigate thoroughly

Do not assume either way. Investigate before concluding. Both outcomes are equally valid:

  • User misremembered/mixed things up -> clarify with evidence
  • System has a genuine issue -> proceed to plan mode for fix

Workflow

Phase 1: Identify the Confusion
  1. Extract the core question - What specifically is the user asking about?
  2. Identify the expectation - What did the user expect to happen?
  3. Identify the reality - What is actually happening?
  4. Locate the gap - Where is the misalignment?
  5. Consider context mixing - Could user be thinking of a different project/feature?

Categories of confusion:

  • Memory gap - user forgot how it works, needs a reminder
  • Project mixing - user confused this with another project they're working on
  • Outdated mental model - user's understanding is based on old behavior
  • Architectural - misunderstanding system design, component relationships, data flow
  • Behavioral - expecting different runtime behavior than what occurs
  • Configuration - settings not producing expected results
  • Documentation - docs don't match implementation or are unclear
  • Conceptual - misunderstanding underlying concepts or patterns
  • Implementation - code doesn't work as assumed
Phase 2: Investigate

Before explaining, gather evidence:

  1. Read relevant code - Understand actual implementation
  2. Check configuration - Verify settings and their effects
  3. Review documentation - See what's documented vs actual behavior
  4. Trace the flow - Follow execution path if behavioral confusion

Do not guess or assume. Investigate the actual system state.

Phase 3: Explain (Gently)

Structure the explanation with patience and care:

  1. Acknowledge the confusion - Validate that it's understandable, confusion is normal
  2. State the expectation - "You expected X to do Y"
  3. State the reality - "Actually, X does Z because..."
  4. Explain why - Provide the reasoning/design decision behind the behavior
  5. Show evidence - Point to specific code, config, or docs

Tone guidelines:

  • Be gentle, not condescending - user may have simply forgotten
  • Avoid "you're wrong" framing - use "here's how it actually works"
  • If user mixed up projects, clarify without judgment
  • Remind that it's easy to forget details when working on multiple things

Keep explanations:

  • Concrete, not abstract
  • Backed by evidence from the codebase
  • Focused on the specific case, not general theory
Phase 4: Assess

Start with the most common cases first:

A) Memory gap - user simply forgot

  • User implemented this but forgot how it works
  • System is working exactly as designed
  • Resolution: gentle reminder with code references

B) Project mixing - wrong mental context

  • User is thinking of a different project or codebase
  • This project works differently than user's current mental model
  • Resolution: clarify which project this is and how it differs

C) Outdated understanding

  • System changed since user last worked on it
  • Or user's mental model never matched reality
  • Resolution: explain current behavior with evidence

D) Documentation issue

  • System works correctly but docs are misleading/missing
  • Resolution: suggest updating docs, may use EnterPlanMode

E) Configuration issue

  • System can do what user expects but isn't configured for it
  • Resolution: suggest configuration changes

F) Real issue - design or implementation problem

  • User's expectation is reasonable AND system genuinely doesn't meet it
  • This indicates a bug, design flaw, or missing feature
  • Resolution: MUST proceed to Phase 5
Show full SKILL.md (346 more words)Show less
Phase 5: Plan the Fix (for real issues)

If Phase 4 identified a real issue (category F):

Step 1: Summarize and Assess Scope

Explain to user what fixing this involves:

Scope categories:

  • Trivial - Simple fix, single file, no side effects
  • Localized - Few files, contained to one component
  • Moderate - Multiple components affected, requires testing
  • Significant - Cross-cutting concern, affects multiple subsystems
  • Architectural - Fundamental design change, may require rethinking approach

Be explicit: "This is a [scope] change because [reason]."

User must understand the magnitude before deciding to proceed.

Step 2: Present Options (if multiple approaches exist)

When there are multiple valid solutions, use AskUserQuestion tool to present choices:

  • List 2-4 options with clear trade-off descriptions
  • Put recommended option first with "(Recommended)" suffix
  • Include "Do nothing" as an option when relevant:
    • Issue is cosmetic or low-impact
    • Workaround exists
    • Fix is risky relative to benefit
    • Issue is edge case that rarely occurs
  • Let user choose the approach
Step 3: Proceed to Plan Mode

After user confirms or selects an approach:

  1. Use EnterPlanMode - Create implementation plan for the chosen approach
  2. Plan should reflect the scope assessment from Step 1

CRITICAL: Do not attempt to fix issues without planning. Always use EnterPlanMode for:

  • Bug fixes
  • Design changes
  • Missing features
  • Documentation updates that require code understanding

Response Format

## Understanding Your Confusion

**What you expected**: [user's expectation]
**What actually happens**: [actual behavior]

## Why This Happens

[Explanation with evidence - code references, config, docs]

## Assessment

[One of: Not an issue / Documentation issue / Real issue / Configuration issue]

[If real issue]:
This is a real issue that should be addressed. I recommend switching to plan mode to design a proper fix.

Should I enter plan mode to plan the solution?

Guidelines

Mindset:

  • Users are experienced developers - trust their instincts
  • About half of confusion cases are real issues, half are misunderstandings
  • Users work on many projects - confusion between them is normal
  • Memory is fallible - be patient when reminding how things work

Approach:

  • Never dismiss confusion as "user error" - investigate first
  • Never assume something is broken without evidence either
  • Always back explanations with evidence from the actual codebase
  • If unsure, ask clarifying questions before investigating
  • Keep the tone helpful, not condescending
  • If the confusion reveals a real problem, treat it as valuable feedback
  • Don't over-explain - focus on the specific confusion, not general tutorials

Fixing:

  • Investigate first, then determine outcome
  • If it's a misunderstanding -> explain clearly with evidence
  • If it's a real issue -> proceed to plan mode for fix
  • Use EnterPlanMode when investigation confirms a genuine bug/flaw

© umputun, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/workflow/skills/clarify of umputun/cc-thingz.

Open the folder on GitHubat commit 99e1c8d

Compare with similar skills

Clarify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Clarify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Clarify this skillumputun/cc-thingz484—~2.1kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from umputun/cc-thingz

All 16 skills in this repo

  • Exec

    umputun/cc-thingz

    Execute plan tasks sequentially using subagents. An agent skill from umputun/cc-thingz.

    484 GitHub stars~8k tokensUpdated 2 days ago
    Auto-check passed

  • New

    umputun/cc-thingz

    A skill your agent uses when user asks to create a release, cut a release, or publish a version.

    484 GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check: notes

  • Root Cause Investigator

    umputun/cc-thingz

    Systematic root cause analysis for errors, bugs, and unexpected behaviors using 5-Why methodology.

    484 GitHub stars~879 tokensUpdated 2 days ago
    Auto-check passed

  • Ask Codex

    umputun/cc-thingz

    Consult OpenAI Codex for investigation, debugging, or code review.

    484 GitHub stars~2.6k tokensUpdated 2 days ago
    Auto-check: notes

  • Backlog

    umputun/cc-thingz

    Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item.

    484 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check: notes

  • Brainstorm

    umputun/cc-thingz

    Use before any creative work or significant changes. An agent skill from umputun/cc-thingz.

    484 GitHub stars~1.7k tokensUpdated 2 days ago
    Auto-check: notes

Categories

Questions about Clarify

What does Clarify do?

This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality. Clarify is an agent skill from umputun/cc-thingz. This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality.

When should I use Clarify?

Clarify fits situations like: appears confused; shows misalignment between expectations and reality; phrases like I dont understand; this doesnt make sense.

How do I install Clarify in Claude Code?

Run `npx skills add umputun/cc-thingz --skill clarify -a claude-code`. Or copy the skill folder (plugins/workflow/skills/clarify in umputun/cc-thingz) into .claude/skills/clarify in your project. Claude Code loads it when a task matches its description.

How do I install Clarify in Codex?

Run `npx skills add umputun/cc-thingz --skill clarify -a codex`. Or copy the skill folder (plugins/workflow/skills/clarify in umputun/cc-thingz) into .agents/skills/clarify in your project. Codex loads it when a task matches its description.

Can I use Clarify in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add umputun/cc-thingz --skill clarify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clarify, .gemini/skills/clarify, .github/skills/clarify and .opencode/skills/clarify in your project.

What does Clarify need to run?

SKILL.md names no scripts, command-line tools or credentials: Clarify is instructions for the agent only. Its frontmatter pre-approves these tools: EnterPlanMode, AskUserQuestion.

Does Clarify access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Clarify safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Clarify use?

Clarify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clarify use?

About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Clarify?

Skills that share tags, products or a category with Clarify: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clarify?

umputun (a GitHub user) maintains it in umputun/cc-thingz, which has 484 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 5, 2026.

Source: umputun/cc-thingz on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.