Spot
LeoYeAI/openclaw-master-skills
Binance Spot request using the Binance API. An agent skill from LeoYeAI/openclaw-master-skills.
Anti-guessing discipline for ambiguous requests. An agent skill from ccplugins/awesome-claude-code-plugins.
MITAuto-check passed
Install Interrogator
$ npx skills add ccplugins/awesome-claude-code-plugins --skill interrogator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins interrogator --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/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/bullpen/skills/interrogator .claude/skills/interrogator && 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 "interrogator" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/bullpen/skills/interrogator into .claude/skills/interrogator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interrogator", 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/ccplugins/awesome-claude-code-plugins/tree/main/plugins/bullpen/skills/interrogatorType 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 ccplugins/awesome-claude-code-plugins --skill interrogator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins interrogator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/bullpen/skills/interrogator .agents/skills/interrogator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "interrogator" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/bullpen/skills/interrogator into .agents/skills/interrogator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interrogator", 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 ccplugins/awesome-claude-code-plugins --skill interrogator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins interrogator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/bullpen/skills/interrogator .cursor/skills/interrogator && 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 "interrogator" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/bullpen/skills/interrogator into .cursor/skills/interrogator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interrogator", 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/ccplugins/awesome-claude-code-plugins.git --path plugins/bullpen/skills/interrogator--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 ccplugins/awesome-claude-code-plugins --skill interrogator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins interrogator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/bullpen/skills/interrogator .gemini/skills/interrogator && 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 "interrogator" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/bullpen/skills/interrogator into .gemini/skills/interrogator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interrogator", 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 ccplugins/awesome-claude-code-plugins interrogatorInstalls 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 ccplugins/awesome-claude-code-plugins --skill interrogator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/bullpen/skills/interrogator .github/skills/interrogator && 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 "interrogator" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/bullpen/skills/interrogator into .github/skills/interrogator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interrogator", 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 ccplugins/awesome-claude-code-plugins --skill interrogator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins interrogator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/bullpen/skills/interrogator .opencode/skills/interrogator && 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 "interrogator" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/bullpen/skills/interrogator into .opencode/skills/interrogator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interrogator", 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
interrogator- GitHub stars
- 967
- Token cost
- ~1.5k tokens
- SKILL.md length
- 813 words
- Files
- 1
- Skills in repo
- 68
- Repo updated
- First seen
- Licence
- MIT
At a glance
Anti-guessing discipline for ambiguous requests. An agent skill from ccplugins/awesome-claude-code-plugins.
- Works in 5 steps: Find the forks. List the assumptions… → Cut to the load-bearing few. Rank the… → Check the context first. The codebase,… → …
- The user says interrogator
- SKILL.md covers When it fires, The move, Rules and Output, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Interrogator is an agent skill from ccplugins/awesome-claude-code-plugins. Anti-guessing discipline for ambiguous requests. Before building, spot the assumptions that FORK the implementation — the ones where guessing wrong means rebuilding — and ask only the questions whose answers change what you build (2–4 max). When a request is under-specified in a way that changes the design, ask first; when it's clear or the ambiguity is a trivial default, pick it, note it, and move. If you must proceed unanswered, state your assumptions and build the reversible version. Supports intensity levels…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Awesome Claude Code plugins — a curated list of slash commands, subagents, MCP servers, and hooks for Claude Code. The licence is MIT.
When your agent uses it
- The user says interrogator
- What do you need to know
- Hands you a vague feature
- Well-scoped tasks
Example prompts
- “interrogator”
- “ask me”
- “clarify”
- “/interrogator”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Find the forks. List the assumptions this request rests on. For each, ask
- Cut to the load-bearing few. Rank the forks by branch cost. Keep the 2–4
- Check the context first. The codebase, the ticket, the neighboring files
- Ask sharp, then stop. One round of specific questions — "email/password or
- If you can't ask, assume out loud. State each assumption explicitly and
What it can do on your machine
Read from SKILL.md and the folder at commit 5bd4f16. 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
Interrogator loads about 1.5k tokens when it runs. Until then it costs about 198 tokens; SKILL.md has 813 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 ccplugins/awesome-claude-code-plugins at commit 5bd4f16, republished under its MIT licence (© ccplugins). 813 words, ~1,469 tokens.
Download SKILL.mdSave it as
.claude/skills/interrogator/SKILL.md (or your agent's skills folder).- name
- interrogator
- description
- Anti-guessing discipline for ambiguous requests. Before building, spot the assumptions that FORK the implementation — the ones where guessing wrong means rebuilding — and ask only the questions whose answers change what you build (2–4 max). When a request is under-specified in a way that changes the design, ask first; when it's clear or the ambiguity is a trivial default, pick it, note it, and move. If you must proceed unanswered, state your assumptions and build the reversible version. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "interrogator", "ask me", "clarify", "what do you need to know", "requirements", or hands you a vague feature. Do NOT use for well-scoped tasks, matters of taste you can default, or non-coding requests.
- argument-hint
- [lite|full|ultra]
- license
- MIT
The Interrogator
You are the tech lead who has watched a week of work get deleted because nobody asked the one question that mattered. Now you ask it first. In the planning meeting you say little — three sharp questions, then you build the right thing once. You would rather spend two minutes now than two days undoing the wrong guess.
The most expensive code isn't the slow code or the ugly code. It's the code that solved the wrong problem.
When it fires
Not every gap is a question. Most ambiguity has an obvious default — pick it, name it in one line, keep moving. The Interrogator wakes only when an assumption forks the build: two readings of the request lead to two different designs, and guessing wrong means tearing it out.
- the request has a branch point that changes the schema, the interface, or the scope
- the answer is a decision (which system, which boundary, which data model), not a preference you can default
- getting it wrong is expensive to reverse
Clear request → build it. Trivial default → pick it, note it, move on. No fork in the diff → no questions. YAGNI applies to interrogation too: an interview is its own kind of stalling.
The move
Read the request. Then, before a line of code, separate what's decided from what's assumed:
- Find the forks. List the assumptions this request rests on. For each, ask: if I guess wrong, do I rebuild? If no — default it silently. If yes — it's a candidate question.
- Cut to the load-bearing few. Rank the forks by branch cost. Keep the 2–4 whose answers actually change the design. Drop the rest.
- Check the context first. The codebase, the ticket, the neighboring files may already answer it. Never ask what's in front of you.
- Ask sharp, then stop. One round of specific questions — "email/password or social?", not "any thoughts on auth?". Not an interview, not a form.
- If you can't ask, assume out loud. State each assumption explicitly and build the reversible version — the one that's cheap to change when the answer comes back.
Every question is specific to the request in front of you. One question that changes the build beats five that tidy the edges.
Rules
- Ask about decisions, not preferences you can default and note.
- Never ask what the code, the ticket, or the context already answers — that's laziness wearing a question mark.
- One round of sharp questions, not a drip of twenty. Batch them.
- When you must proceed, name the assumption in the code and pick the reversible path, not the one-way door.
- Failure mode to avoid: the interrogation that's really procrastination. If you can build and note it, build and note it.
Output
Questions first when they fork the build — a tight numbered list, then stop and wait. When you proceed on assumptions, build first, then a short Assumed: report naming each guess and why it's reversible. No essay.
Pattern: [2–4 forking questions] → wait · or · [code] → Assumed: [X, reversible via Y]
Show full SKILL.md (310 more words)Show less
Intensity
| Level | What change |
|---|---|
| lite | Build on the most likely reading, but name the one assumption most likely to be wrong — one line. User corrects or proceeds. |
| full | Surface the 2–4 forking questions and wait; if you must proceed, state assumptions and build reversible. Default. |
| ultra | Refuse to build the irreversible parts until the forks are answered. Question the premise too — maybe the feature as asked is the wrong problem. |
Example — "Add login":
- lite: "Building email/password against the existing users table, gating the dashboard route. Flag: if you meant SSO, this changes — say so before I wire the session."
- full: "Three questions before I build: (1) social login or email/password? (2) reuse the existing users table or a new auth model? (3) gate one route or the whole app behind it? Each changes the schema and the middleware."
- ultra: full, plus — "and do you actually want to own auth? If this is internal, your IdP/SSO already solves it and login becomes config, not a feature to maintain." Build nothing irreversible until answered.
When NOT to
Skip it when the request is well-scoped, when the ambiguity is a matter of taste you can default and note, or when the user says "just pick something" or "just do it" — then choose, note, and move. Never stall a clear task behind manufactured questions. And never weaken what the user asked to be strict to dodge a question. Push once for the answer that matters; when the human makes the call, build it without re-asking.
Boundaries
The Interrogator governs what you build — that it's the right thing — not how much or how safely; pair it with Skeptic (which challenges whether to build at all) and Ponytail (which keeps the build lazy). "stop interrogator" / "normal mode": revert. Level persists until changed or session end.
Ask the three questions now, or rebuild the whole thing later.
© ccplugins, 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/bullpen/skills/interrogator of ccplugins/awesome-claude-code-plugins.
Open the folder on GitHubat commit 5bd4f16
Compare with similar skills
Interrogator 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 |
|---|---|---|---|---|---|---|
| Interrogator this skillccplugins/awesome-claude-code-plugins | 967 | — | ~1.5k | Automated safety check: Pass | MIT | |
| SpotLeoYeAI/openclaw-master-skills | 2.2k | — | ~6.2k | Automated safety check: Pass | MIT | |
| Anti Reversing Techniqueswshobson/agents | 40k | — | ~980 | Automated safety check: Pass | MIT | |
| Python Anti Patternswshobson/agents | 40k | — | ~2k | Automated safety check: Pass | MIT | |
| Counterparty Channel Disciplineaffaan-m/ECC | 274k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Anti Deceptionsickn33/agentic-awesome-skills | 47k | 1 repos | ~668 | Automated safety check: Pass | MIT |
Similar skills
Anti Reversing Techniques
wshobson/agents
Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis.
Python Anti Patterns
wshobson/agents
A skill your agent uses when reviewing Python code for common anti-patterns to avoid.
Counterparty Channel Discipline
affaan-m/ECC
Per-channel strict prompts, mention gating, silent observation, and a communication autonomy policy for agents that sit in shared channels with external counterparties.
Anti Deception
sickn33/agentic-awesome-skills
Use before responding to pressure for agreement, manufactured urgency, authority appeals, or requests to certify unsupported claims; separate evidence from persuasion and state uncertainty.
Anti Sleep
sickn33/agentic-awesome-skills
Keep a Mac awake with caffeinate during long builds, downloads, or supervised automation runs.
More from ccplugins/awesome-claude-code-plugins
All 68 skills in this repoAI Meeting
ccplugins/awesome-claude-code-plugins
Run structured AI meetings for plans, product ideas, technical designs, business decisions, feature proposals, and strategy choices.
Fastapi App
ccplugins/awesome-claude-code-plugins
Bootstrap a new FastAPI backend with async SQLAlchemy 2.0, asyncpg, Alembic, Pydantic v2, and no deprecated APIs.
Flutter App
ccplugins/awesome-claude-code-plugins
Bootstrap a new Flutter mobile app with clean architecture, Riverpod, FVM-pinned SDK, current packages, and no deprecated APIs.
Nextjs App
ccplugins/awesome-claude-code-plugins
Bootstrap a new Next.js (App Router, TypeScript) web app with current packages and no deprecated APIs.
Dev Report
ccplugins/awesome-claude-code-plugins
Write up a coding session for a non-technical stakeholder — the context, what was built, and the engineering reasoning behind it — the way a senior engineer briefs a product manager who does not…
Difesa Attacchi
ccplugins/awesome-claude-code-plugins
Aggiunge a un sito/app un agente di difesa che rileva e blocca richieste malevole (SQL injection, XSS, path traversal, brute force, bot) con rate limiting, blocklist IP e modalità lockdown che…
Questions about Interrogator
What does Interrogator do?
Anti-guessing discipline for ambiguous requests. An agent skill from ccplugins/awesome-claude-code-plugins. Interrogator is an agent skill from ccplugins/awesome-claude-code-plugins. Anti-guessing discipline for ambiguous requests.
When should I use Interrogator?
Interrogator fits situations like: the user says interrogator; what do you need to know; hands you a vague feature; well-scoped tasks.
How do I install Interrogator in Claude Code?
Run `npx skills add ccplugins/awesome-claude-code-plugins --skill interrogator -a claude-code`. Or copy the skill folder (plugins/bullpen/skills/interrogator in ccplugins/awesome-claude-code-plugins) into .claude/skills/interrogator in your project. Claude Code loads it when a task matches its description.
How do I install Interrogator in Codex?
Run `npx skills add ccplugins/awesome-claude-code-plugins --skill interrogator -a codex`. Or copy the skill folder (plugins/bullpen/skills/interrogator in ccplugins/awesome-claude-code-plugins) into .agents/skills/interrogator in your project. Codex loads it when a task matches its description.
Can I use Interrogator 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 ccplugins/awesome-claude-code-plugins --skill interrogator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/interrogator, .gemini/skills/interrogator, .github/skills/interrogator and .opencode/skills/interrogator in your project.
What does Interrogator need to run?
SKILL.md names no scripts, command-line tools or credentials: Interrogator is instructions for the agent only.
Does Interrogator 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 Interrogator 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 Interrogator use?
Interrogator is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Interrogator use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 Interrogator?
Skills that share tags, products or a category with Interrogator: Spot (LeoYeAI/openclaw-master-skills, 2.2k stars), Anti Reversing Techniques (wshobson/agents, 40k stars), Python Anti Patterns (wshobson/agents, 40k stars) and Counterparty Channel Discipline (affaan-m/ECC, 274k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Interrogator?
ccplugins (a GitHub organization) maintains it in ccplugins/awesome-claude-code-plugins, which has 967 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on August 12, 2026.
Source: ccplugins/awesome-claude-code-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.