Agent skill

Clarify

by mag123c in mag123c/toktrack

Adaptive requirements clarification with auto-depth routing.

MITAuto-check passed

Install Clarify

skills CLI
$ npx skills add mag123c/toktrack --skill clarify -a claude-code

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

GitHub CLI
$ gh skill install mag123c/toktrack 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/mag123c/toktrack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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
193
Token cost
~1.3k tokens
SKILL.md length
516 words
Files
7 (incl. references)
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Adaptive requirements clarification with auto-depth routing.

  • Works in 6 steps: Record: Log original request + identify… → Question: AskUserQuestion (specific… → Escalation Check: Check escalation… → …
  • SKILL.md covers Chain (MUST), Core Model, Reference Files (load as… and Step 0: Route — Complexity…, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Clarify is an agent skill from mag123c/toktrack. Adaptive requirements clarification with auto-depth routing. Shallow (Q&A) for simple tasks, Deep (exploration + DRAFT + PLAN) for complex ones. Escalates automatically when ambiguity persists.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `deep/DEEP.md`, `references/checkpoint.md` and `references/doc-roles.md`).

The repository describes itself as: Ultra-fast token & cost tracker for LLM Token Usage (e.g. Claude Code). The licence is MIT.

Example prompts

  • “/clarify”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Task, Write, AskUserQuestion

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Record: Log original request + identify ambiguous parts
  2. Question: AskUserQuestion (specific options, 2-3 rounds)
  3. Escalation Check: Check escalation conditions (see below)
  4. Create DRAFT: Write .dev/specs/{name}/DRAFT.md (minimal version — What, Why, Scope, Success Criteria)
  5. Summary + Create PLAN: Before/After comparison → Write .dev/specs/{name}/PLAN.md
  6. Present PLAN: Present the PLAN inline in the conversation (do NOT enter plan mode), then immediately call /implement. The plan file must…

What it can do on your machine

Read from SKILL.md and the folder at commit 75a86fa. 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:

    • Read
    • Grep
    • Glob
    • Task
    • Write
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    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 1.3k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 50 tokens; SKILL.md has 516 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.2k

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 mag123c/toktrack at commit 75a86fa, republished under its MIT licence (© mag123c). 516 words, ~1,331 tokens.

Download SKILL.mdSave it as .claude/skills/clarify/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
clarify
description
Adaptive requirements clarification with auto-depth routing. Shallow (Q&A) for simple tasks, Deep (exploration + DRAFT + PLAN) for complex ones. Escalates automatically when ambiguity persists.
allowed-tools
Read, Grep, Glob, Task, Write, AskUserQuestion
required_context
.claude/ai-context/architecture.md, .claude/ai-context/conventions.md

/clarify — Adaptive Requirements Clarification

Chain (MUST)

PreviousCurrentNext
Session start/clarifyPresent PLAN inline → /implement

Core Model

/clarify → Measure complexity → Clear enough?
                                ├─ Yes → Present PLAN inline → /implement
                                └─ No  → Deeper clarify (explore, analyze, DRAFT...)
                                         → Re-measure → Repeat

Exit condition: "Is this enough info to implement?" — Critical Unknown=0 + remaining items are made visible (Provenance).


Reference Files (load as needed — chaining)

WhenFile
Tagging provenance on key decisions/assumptions / probe decisionsreferences/provenance.md
Pre-PLAN user confirmationreferences/checkpoint.md
When document authority/reading order is unclearreferences/doc-roles.md
Full Deep path proceduredeep/DEEP.md
PLAN/DRAFT structure (Lite/Full + Clarify Verdict)templates/

Inline essentials only: probe-don't-tag (if cheaply verifiable, measure instead of tagging), PLAN=intent · WRAP/DECISIONS=fact, do not hide inferences. Details in the references above.


Step 0: Route — Complexity Assessment

Measure complexity internally upon receiving request (do not expose to user).

Complexity Signals
SignalLOWHIGH
Request lengthShort and specificLong or ambiguous
Keywords"add", "fix", "change""design", "migration", "from scratch"
UncertaintyNone"not sure", "how should I"
Impact scopeSingle file/moduleCross-cutting, multiple services
RiskLow (UI, text)High (DB, auth, breaking API)
Existing patternsClearly existNone or unfamiliar stack
  • LOW → Shallow Path (completed within this file)
  • HIGH → Deep Path (see deep/DEEP.md)
  • Ambiguous → Start Shallow, monitor escalation conditions

Shallow Path (Low Complexity)

Remove ambiguity via quick Q&A, generate minimal specs, and present the PLAN inline.

Execution
  1. Record: Log original request + identify ambiguous parts
  2. Question: AskUserQuestion (specific options, 2-3 rounds)
  3. Escalation Check: Check escalation conditions (see below)
  4. Create DRAFT: Write .dev/specs/{name}/DRAFT.md (minimal version — What, Why, Scope, Success Criteria)
  5. Summary + Create PLAN: Before/After comparison → Write .dev/specs/{name}/PLAN.md
  6. Present PLAN: Present the PLAN inline in the conversation (do NOT enter plan mode), then immediately call /implement. The plan file must be written to .dev/specs/{name}/PLAN.md
Rules
  • No assumptions → Ask questions
  • Clarify to TDD-ready level
  • Target resolution within 3 rounds
Show full SKILL.md (234 more words)Show less
Escalation → Deep Path

Switch to Deep Path if any of these are detected:

  • Scope still undefined after 3 rounds of questions
  • New uncertainties keep emerging from user answers
  • Impact scope expanded beyond initial estimate (single → multi-module)
  • Risk indicators found (DB schema, auth, breaking changes)
  • User doesn't know the approach itself ("I don't know how to do this")

On switch: Inform "Scope is more complex than expected. Exploring the codebase first." then follow the process in deep/DEEP.md.


Deep Path

When complexity is HIGH or escalated from Shallow.

See deep/DEEP.md for the full process.

Summary:

  1. Classify intent (7 types) → Determine strategy
  2. 3 parallel exploration agents → Understand codebase
  3. Generate DRAFT → Interview → Continuously update
  4. On user explicit request → Analysis agents → Generate PLAN → Reviewer loop
  5. Present PLAN inline → immediately call /implement (no plan mode entry)

DECISIONS.md Recording (MUST)

Record decisions in .dev/DECISIONS.md before finalizing plan:

SituationRequired Record
New feature designDecision background, alternatives, reasoning
Architecture choiceConsidered options, selection rationale
Trade-offsWhat was sacrificed and what was gained
markdown
## YYYY-MM-DD: {feature-name}
- **Decision**: What was decided
- **Reason**: Why this choice was made
- **Alternatives**: Options considered but not chosen
- **Reference**: .dev/specs/{feature-name}/PLAN.md (if exists)

Plan File Requirements

Plan files must include:

  • Specify implementation via /implement skill
  • Verification method (test execution)
  • Confirmation that .dev/DECISIONS.md recording is complete

Plan File Location: The PLAN must be written to .dev/specs/{name}/PLAN.md.

Important: Plans that do not use /implement will not be approved.


NEXT STEP (Auto-execute)

After presenting the PLAN inline, call /implement immediately. Do NOT enter plan mode; do not ask "Should I implement?".

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

Files

SKILL.md and 6 other files (references) in .claude/skills/clarify of mag123c/toktrack.

  • SKILL.md
  • deep/DEEP.md
  • references/checkpoint.md
  • references/doc-roles.md
  • references/provenance.md
  • templates/DRAFT_TEMPLATE.md
  • templates/PLAN_TEMPLATE.md

Open the folder on GitHubat commit 75a86fa

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 skillmag123c/toktrack193—~1.3kAutomated safety check: PassMIT
Requirements Clarificationasgeirtj/system_prompts_leaks69k—~687Automated safety check: PassCC0-1.0
Requirementsrizsotto/Bear6.5k—~2kAutomated safety check: PassGPL-3.0
Agent Adaptive Coordinatorruvnet/ruflo74k2 repos~4kAutomated safety check: PassMIT
Go In Depthsickn33/agentic-awesome-skills47k1 repos~530Automated safety check: PassMIT
Create Agent Adapterpaperclipai/paperclip99k—~8kAutomated safety check: PassMIT

Similar skills

  • Requirements Clarification

    asgeirtj/system_prompts_leaks

    Clarify a material user-owned product decision before substantive implementation commitments.

    69k GitHub stars~687 tokensUpdated today
    Backend & APIsAuto-check passed
  • Requirements

    rizsotto/Bear

    Write, modify, or review a requirement file under docs/requirements -- pick the single owning file, keep the text contract-only, name IDs so they need no explanation, and verify cross-references and…

    6.5k GitHub stars~2k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Agent skill for adaptive-coordinator - invoke with $agent-adaptive-coordinator

    74k GitHub starsUsed in 2 repos~4k tokens
    Data & AnalyticsAuto-check passed
  • Go In Depth

    sickn33/agentic-awesome-skills

    Go in depth harness — fan-out web searches, fetch sources, adversarially verify claims, synthesize a cited report.

    47k GitHub starsUsed in 1 repo~530 tokens
    Research & ScienceAuto-check passed
  • Create Agent Adapter

    paperclipai/paperclip

    Create or modify Paperclip agent adapters across server, UI, and CLI surfaces.

    99k GitHub stars~8k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Aria Required Attr

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Include required ARIA attributes for roles.

    74k GitHub stars~459 tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed

More from mag123c/toktrack

  • Implement

    mag123c/toktrack

    TDD implementation (RED→GREEN→REFACTOR) → verify → review. An agent skill from mag123c/toktrack.

    193 GitHub stars~353 tokensUpdated 7 days ago
    Auto-check passed
  • Review

    mag123c/toktrack

    Multi-agent code review for Rust CLI/TUI. An agent skill from mag123c/toktrack.

    193 GitHub stars~1.2k tokensUpdated 7 days ago
    Auto-check passed
  • Verify

    mag123c/toktrack

    Self-healing verification loop (test → clippy → fmt). An agent skill from mag123c/toktrack.

    193 GitHub stars~676 tokensUpdated 7 days ago
    Auto-check passed
  • Next

    mag123c/toktrack

    Session start - check progress, suggest next task. An agent skill from mag123c/toktrack.

    193 GitHub stars~330 tokensUpdated 7 days ago
    Auto-check passed
  • Wrap

    mag123c/toktrack

    Session end - document updates, commit

    193 GitHub stars~407 tokensUpdated 7 days ago
    Auto-check passed

Questions about Clarify

What does Clarify do?

Adaptive requirements clarification with auto-depth routing. Clarify is an agent skill from mag123c/toktrack. Adaptive requirements clarification with auto-depth routing.

How do I install Clarify in Claude Code?

Run `npx skills add mag123c/toktrack --skill clarify -a claude-code`. Or copy the skill folder (.claude/skills/clarify in mag123c/toktrack) 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 mag123c/toktrack --skill clarify -a codex`. Or copy the skill folder (.claude/skills/clarify in mag123c/toktrack) 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 mag123c/toktrack --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: Read, Grep, Glob, Task, Write, 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 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 891 tokens, read only when the agent opens those files.

What are the alternatives to Clarify?

Skills that share tags, products or a category with Clarify: Requirements Clarification (asgeirtj/system_prompts_leaks, 69k stars), Requirements (rizsotto/Bear, 6.5k stars), Agent Adaptive Coordinator (ruvnet/ruflo, 74k stars) and Go In Depth (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clarify?

mag123c (a GitHub user) maintains it in mag123c/toktrack, which has 193 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 1, 2026.

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