Azsdk Common Generate SDK Locally
Azure/azure-sdk-for-android
Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization.
Clarify a material user-owned product decision before substantive implementation commitments.
Install Requirements Clarification
$ npx skills add asgeirtj/system_prompts_leaks --skill requirements-clarification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install asgeirtj/system_prompts_leaks requirements-clarification --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Meta/muse-code/skills/requirements-clarification .claude/skills/requirements-clarification && rm -rf skills-srcUse ~/.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/
Install the "requirements-clarification" agent skill from https://github.com/asgeirtj/system_prompts_leaks/tree/main/Meta/muse-code/skills/requirements-clarification into .claude/skills/requirements-clarification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-clarification", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/asgeirtj/system_prompts_leaks/tree/main/Meta/muse-code/skills/requirements-clarificationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add asgeirtj/system_prompts_leaks --skill requirements-clarification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install asgeirtj/system_prompts_leaks requirements-clarification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Meta/muse-code/skills/requirements-clarification .agents/skills/requirements-clarification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "requirements-clarification" agent skill from https://github.com/asgeirtj/system_prompts_leaks/tree/main/Meta/muse-code/skills/requirements-clarification into .agents/skills/requirements-clarification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-clarification", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add asgeirtj/system_prompts_leaks --skill requirements-clarification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install asgeirtj/system_prompts_leaks requirements-clarification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Meta/muse-code/skills/requirements-clarification .cursor/skills/requirements-clarification && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "requirements-clarification" agent skill from https://github.com/asgeirtj/system_prompts_leaks/tree/main/Meta/muse-code/skills/requirements-clarification into .cursor/skills/requirements-clarification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-clarification", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/asgeirtj/system_prompts_leaks.git --path Meta/muse-code/skills/requirements-clarification--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add asgeirtj/system_prompts_leaks --skill requirements-clarification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install asgeirtj/system_prompts_leaks requirements-clarification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Meta/muse-code/skills/requirements-clarification .gemini/skills/requirements-clarification && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "requirements-clarification" agent skill from https://github.com/asgeirtj/system_prompts_leaks/tree/main/Meta/muse-code/skills/requirements-clarification into .gemini/skills/requirements-clarification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-clarification", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install asgeirtj/system_prompts_leaks requirements-clarificationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add asgeirtj/system_prompts_leaks --skill requirements-clarification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks.git skills-src && mkdir -p .github/skills && cp -r skills-src/Meta/muse-code/skills/requirements-clarification .github/skills/requirements-clarification && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "requirements-clarification" agent skill from https://github.com/asgeirtj/system_prompts_leaks/tree/main/Meta/muse-code/skills/requirements-clarification into .github/skills/requirements-clarification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-clarification", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add asgeirtj/system_prompts_leaks --skill requirements-clarification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install asgeirtj/system_prompts_leaks requirements-clarification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Meta/muse-code/skills/requirements-clarification .opencode/skills/requirements-clarification && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "requirements-clarification" agent skill from https://github.com/asgeirtj/system_prompts_leaks/tree/main/Meta/muse-code/skills/requirements-clarification into .opencode/skills/requirements-clarification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-clarification", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
requirements-clarification- GitHub stars
- 69k
- Token cost
- ~687 tokens
- SKILL.md length
- 226 words
- Files
- 1
- Skills in repo
- 128
- Repo updated
- First seen
- Licence
- CC0-1.0
At a glance
Clarify a material user-owned product decision before substantive implementation commitments.
- Works in 6 steps: Read the request and any explicitly… → Separate user-owned outcomes and… → If a narrow reversible default safely… → …
- A truncated request omits such a choice
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Implement/build/fix/debug/refactor work when expected behavior is settled
What it does
Requirements Clarification is an agent skill from asgeirtj/system_prompts_leaks. Clarify a material user-owned product decision before substantive implementation commitments. Use only when request and named/governing evidence still leave a choice that would materially change scope, platform support, user-facing surface, data/API contract, domain values, project placement, or cross-system architecture; also use when a truncated request omits such a choice. On the initial turn, inspect only named or governing requirements evidence, then ask directly without loading: prefer structured input; ask…
Its SKILL.md is about 690 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 Backend & APIs, covering API design. The repository describes itself as: Documented system prompts from Anthropic - Claude Fable 5.1, Opus 5.5, Claude Design, Claude Code. OpenAI - ChatGPT GPT-6-Astra, Codex. Google - Gemini 3.8 Flash, 3.1 Pro… The licence is CC0-1.0.
When your agent uses it
- A truncated request omits such a choice
- Implement/build/fix/debug/refactor work when expected behavior is settled
- Plan/design deliverables owned by Plan
- Complexity/greenfield/integration alone
Example prompts
- “/requirements-clarification”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Read the request and any explicitly named or governing requirements source.
- Separate user-owned outcomes and authoritative inputs from agent-owned
- If a narrow reversible default safely satisfies the request, state it and
- Otherwise ask before substantive commitment. Reads, notes, or one small
- Prefer request_user_input when available. Ask one blocking outcome question;
- After the answer, do not ask again unless later evidence reveals a distinct
What it can do on your machine
Read from SKILL.md and the folder at commit 60d44cc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
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
Requirements Clarification loads about 687 tokens when it runs. Until then it costs about 259 tokens; SKILL.md has 226 words of instructions outside code blocks.
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 asgeirtj/system_prompts_leaks at commit 60d44cc, republished under its CC0-1.0 licence (© asgeirtj). 226 words, ~687 tokens.
Download SKILL.mdSave it as
.claude/skills/requirements-clarification/SKILL.md (or your agent's skills folder).- name
- requirements-clarification
- description
- Clarify a material user-owned product decision before substantive implementation commitments. Use only when request and named/governing evidence still leave a choice that would materially change scope, platform support, user-facing surface, data/API contract, domain values, project placement, or cross-system architecture; also use when a truncated request omits such a choice. On the initial turn, inspect only named or governing requirements evidence, then ask directly without loading: prefer structured input; ask one blocking outcome question or at most three coupled questions; wait. After the answer, load the body before write or delegation. Do not use for implement/build/fix/debug/refactor work when expected behavior is settled, plan/design deliverables owned by Plan, complexity/greenfield/integration alone, agent-owned technical choices, locally discoverable facts, reversible defaults, permission to begin, or stop/no-tool turns. Never re-ask supplied facts or turn clarification into refusal.
- user-invocable
- false
Requirements Clarification
Resolve only a remaining user-owned product decision. Do not turn normal implementation uncertainty into a question.
- Read the request and any explicitly named or governing requirements source. Do not scan broadly for hypothetical ambiguity. If this evidence settles the outcome, proceed without asking.
- Separate user-owned outcomes and authoritative inputs from agent-owned implementation choices. Research discoverable facts yourself. Never ask the user to choose a library, framework, or method the agent can determine.
- If a narrow reversible default safely satisfies the request, state it and proceed. Complexity, greenfield status, file count, or integration work alone never requires clarification.
- Otherwise ask before substantive commitment. Reads, notes, or one small branch-neutral probe are allowed; a scaffold, public contract, embedded domain values, or cross-system architecture is a commitment.
- Prefer
request_user_inputwhen available. Ask one blocking outcome question; group at most three tightly coupled questions. Offer concrete outcome options and a recommendation. Never ask merely for permission to begin. - After the answer, do not ask again unless later evidence reveals a distinct material fork. Apply the answer and continue.
plan owns standalone plan and design deliverables. This skill does not create
an approval gate or stop a specified implementation merely because planning
would be useful. Never re-ask facts already supplied by the request or governing
evidence, and never turn clarification into a refusal.
© asgeirtj, CC0-1.0. 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 Meta/muse-code/skills/requirements-clarification of asgeirtj/system_prompts_leaks.
Open the folder on GitHubat commit 60d44cc
Compare with similar skills
Requirements Clarification 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Requirements Clarification this skillasgeirtj/system_prompts_leaks | 69k | — | ~687 | Automated safety check: Pass | CC0-1.0 | |
| Azsdk Common Generate SDK LocallyAzure/azure-sdk-for-android | 121 | — | ~1.5k | Automated safety check: Pass | MIT | |
| REST API Contract Reviewdecebals/claude-code-java | 751 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Architecture Designshawnpang/startup-founder-skills | 343 | — | ~2.1k | Automated safety check: Pass | MIT | |
| OpenAPI Spec Generationwshobson/agents | 40k | 9 repos | ~511 | Automated safety check: Pass | MIT | |
| .NET API Compatibility DesignAaronontheweb/dotnet-skills | 1.2k | 1 repos | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
- Official
REST API Contract Review
decebals/claude-code-java
Reviews REST API design for correct HTTP verbs, versioning, DTO use, consistent responses and backward compatibility before an API change ships.
Architecture Design
shawnpang/startup-founder-skills
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure topology, database selection, or dependency analysis.
OpenAPI Spec Generation
wshobson/agents
Create, validate and maintain OpenAPI 3.1 specs for REST APIs, whether designed first or generated from existing code, and use them for docs and client SDKs.
.NET API Compatibility Design
Aaronontheweb/dotnet-skills
Applies extend-only design rules to NuGet packages and distributed systems, covering source, binary and wire compatibility and how to deprecate members safely.
API Error Design Patterns
revfactory/harness-100
Reference for designing how an API reports failures: structured error codes, response shapes, client-friendly messages, an error catalog and retry or fallback advice.
More from asgeirtj/system_prompts_leaks
All 125 skills in this repoFleet Manager for Agent Sessions
asgeirtj/system_prompts_leaks
Shows one digest of coding-agent sessions across your connected machines and lets you open, read, steer, approve, stop and close them, over Herdr, tmux or MSP.
Muse Code Product Doctor
asgeirtj/system_prompts_leaks
Diagnoses a Muse Code installation's own failures from binary and session evidence, instead of treating the report as an ordinary repository bug.
DOCX
asgeirtj/system_prompts_leaks
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx).
Agents Project Coordinator
asgeirtj/system_prompts_leaks
Runs a goal as a project in which the agent coordinates separate agent threads, judging when to split the work, and interviews you first when nothing can be verified.
Muse Plugin Creator
asgeirtj/system_prompts_leaks
Creates and validates a new native Muse plugin package in the current workspace, limited to five capability families, and leaves installation to you.
Deep Research
asgeirtj/system_prompts_leaks
A skill your agent uses when the user's prompt requires (1) researching a topic across multiple sources, comparing options or alternatives, analyzing trends or history, understanding markets or…
Related
Categories
Questions about Requirements Clarification
What does Requirements Clarification do?
Clarify a material user-owned product decision before substantive implementation commitments. Requirements Clarification is an agent skill from asgeirtj/system_prompts_leaks. Clarify a material user-owned product decision before substantive implementation commitments.
When should I use Requirements Clarification?
Requirements Clarification fits situations like: A truncated request omits such a choice; implement/build/fix/debug/refactor work when expected behavior is settled; plan/design deliverables owned by Plan; complexity/greenfield/integration alone.
How do I install Requirements Clarification in Claude Code?
Run `npx skills add asgeirtj/system_prompts_leaks --skill requirements-clarification -a claude-code`. Or copy the skill folder (Meta/muse-code/skills/requirements-clarification in asgeirtj/system_prompts_leaks) into .claude/skills/requirements-clarification in your project. Claude Code loads it when a task matches its description.
How do I install Requirements Clarification in Codex?
Run `npx skills add asgeirtj/system_prompts_leaks --skill requirements-clarification -a codex`. Or copy the skill folder (Meta/muse-code/skills/requirements-clarification in asgeirtj/system_prompts_leaks) into .agents/skills/requirements-clarification in your project. Codex loads it when a task matches its description.
Can I use Requirements Clarification 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 asgeirtj/system_prompts_leaks --skill requirements-clarification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/requirements-clarification, .gemini/skills/requirements-clarification, .github/skills/requirements-clarification and .opencode/skills/requirements-clarification in your project.
What does Requirements Clarification need to run?
SKILL.md names no scripts, command-line tools or credentials: Requirements Clarification is instructions for the agent only.
Does Requirements Clarification 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 Requirements Clarification 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 Requirements Clarification use?
Requirements Clarification is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Requirements Clarification use?
About 687 tokens (SKILL.md is roughly 2.7k 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 Requirements Clarification?
Skills that share tags, products or a category with Requirements Clarification: Azsdk Common Generate SDK Locally (Azure/azure-sdk-for-android, 121 stars), REST API Contract Review (decebals/claude-code-java, 751 stars), Architecture Design (shawnpang/startup-founder-skills, 343 stars) and OpenAPI Spec Generation (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Requirements Clarification?
asgeirtj (a GitHub user) maintains it in asgeirtj/system_prompts_leaks, which has 69,280 GitHub stars. The repository holds 128 skills in this directory. The repository was last updated on October 10, 2026.
Source: asgeirtj/system_prompts_leaks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.