clarify
Skill1 starsChanged 3 days agoMITView on GitHub
Before doing a request, find everything in it that is unclear, ambiguous, missing, contradictory or open to several readings (scope, target, names, behavior, language, format, risky or irreversible actions, "etc."), and ask the user what is really wanted through the built-in questions popup (interactive-questions), in several rounds when it does not fit in one, before changing anything. Use whenever the user summons it (/clarify, "clarifie", "pose-moi des questions avant", "si ce n'est pas clair demande-moi", "vérifie que tu as bien compris") or when a request has real doubts that change what must be done.
82 other projects use a version of this.
Adopted by
Most recently taken up by
- arxdsilva/ai-loopstheir own version, first seen Nov 16, 2026
- RichardDow/skillstheir own version, first seen Nov 15, 2026
- ZaxbyHub/opencode-swarmtheir own version, first seen Nov 15, 2026
- Integralist/agent-skillstheir own version, first seen Nov 14, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 13, 2026
- venhdev/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use quieter, arrange and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
HK-hubSkillquieter
Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.
Also in 29 projects that use this
HK-hubSkillarrange
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 14 projects that use this
zwy123zwySkillnormalize
将用户随意输入的提示词规范化为结构清晰、便于大模型执行的标准化提示词。适用于需要整理、统一提示词格式时调用。
Also in 19 projects that use this
owshq-mecSkilllayout
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 8 projects that use this
- +8 more from HK-hub
Other versions82 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 82
- spool-lab/spool★ 592same name
- paperboytm/spool★ 590same name
- talesofai/cohub★ 585same name
- ZaxbyHub/opencode-swarm★ 531same name
- zaxbysauce/opencode-swarm★ 519same name
- educlopez/ui-craft★ 441same name
- nexmoe/DayBee★ 424same name
- nexmoe/eve★ 424same name
- ryanthedev/code-foundations★ 381same name
- Southclaws/storyden★ 348same name
72 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-at-endSkill
- continue-workSkill
- exportSkill
- full-permissionSkill
- ideationSkill
- interactive-questionsSkill
- onboardSkill
- pauseSkill
- presentationSkill
- rtkSkill
- setup-contextSkill
- write-like-meSkill
- audit-bugsSkill
- audit-depsSkill
- audit-qualitySkill
- audit-securitySkill
- benchmarkSkill
- cmake-styleSkill
- cpp-classSkill
- cpp-commentsSkill
- cpp-projectSkill
- cpp-styleSkill
- better-explain-docSkill
- better-html-docSkill
- better-html-styleSkill
- better-protocol-docSkill
- docs-updateSkill
- explain-docSkill
- html-docSkill
- html-styleSkill
- protocol-docSkill
- readme-styleSkill
- reportSkill
- wiki-styleSkill
- ci-cdSkill
- git-commitSkill
- git-conventionsSkill
- pre-commitSkill
- legal-checkSkill
- legal-setupSkill
- licenseSkill
- libutils-exceptionSkill
- libutils-installSkill
- libutils-setupSkill
- libutilsSkill
- python-classSkill
- python-commentsSkill
- python-projectSkill
- python-styleSkill
- auditSkill
- cppSkill
- devSkill
- docSkill
- gitSkill
- legalSkill
- pythonSkill
- setup-projectSkill
- styleSkill
- setup-studioSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 79 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Read the request as written, then the context that can answer by itself (the code, git status, the README, the conversation, memory): never …
- Distinctive: line 34
No real doubt left: say so in one line ("Rien d'ambigu : je fais ...") and do the task, without a popup.
- Distinctive: line 42
Write each question so it can be answered without reading anything else: say what the doubt is and what each option changes.
- Distinctive: line 47
Read the answers exactly (the *Other* text and notes often change the option).
“Common” is measured: kept by at least 6 in 10 of the 79 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Clarify the request before acting
The request is not done yet: first make sure it is understood. Everything unclear is asked to the user with
interactive-questions (AskUserQuestion popup, never a list in the text), then the work starts on the answers.
Request given with the skill: the text after /clarify if any, otherwise the latest request of the user.
1. Read the request and look
- Read the request as written, then the context that can answer by itself (the code,
git status, the README, the conversation, memory): never ask what can be found or decided from them; a harmless default is taken and said in one line. - Quick read-only look only (files, grep,
git): no change, no build, no commit during this step.
2. List the doubts
Go through the request and keep only the points whose answer changes what will be done:
- Target / scope: which files, modules, projects, repositories, branches; how far (only this or everything similar); what must not be touched.
- Ambiguous words: "this", "it", "the repo", "etc.", "clean", "update", "like before", two possible meanings.
- Missing details: name, version, format, language, output (file / text / PDF), limits, deadline, defaults.
- Several valid approaches with different cost, risk or result (the choice is the user's).
- Contradictions between parts of the request, or with the code / earlier instructions / conventions.
- Risky or irreversible actions (delete, overwrite, force-push, publish, release, send, system change): what is allowed exactly.
- Order and dependencies between several tasks, what to do first, what to skip.
- Assumptions you would otherwise make silently and that could be wrong.
No real doubt left: say so in one line ("Rien d'ambigu : je fais ...") and do the task, without a popup.
3. Ask (skill interactive-questions, load it)
- Group the doubts by theme (scope, approach, details, risks) and ask them with AskUserQuestion: 1 to 4 questions per call, 2 to 4 options each, French labels, the recommended option first, multi choice when the options add up, previews to compare concrete things.
- More than 4 doubts, or a doubt that depends on an earlier answer: several rounds, the blocking / structuring questions first (scope, approach), the details after, each round using what was answered before.
- Write each question so it can be answered without reading anything else: say what the doubt is and what each option changes. Never ask the same thing twice, never ask what the user already stated.
- "Explique plus" / a free text that opens a new doubt: answer it and ask again (see
interactive-questions).
4. Confirm and act
- Read the answers exactly (the Other text and notes often change the option).
- Say in a few lines what will be done now (scope, approach, details chosen). Ask once more only when an answer
left a real contradiction or the plan became risky; otherwise do the task at once, with the skills that fit
(
/devrouting, the style and git skills of the user...). - A choice that must last (a preference, a convention, a name) goes to memory / CLAUDE.md / the project config only when the user wants it.
- Git rules stay the ones of the user's CLAUDE.md and
git-conventions(nothing committed or pushed unless asked in the current request or allowed by the repository).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

