SkillAgentSearch skills...

interrogate

Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Adversaries try to break a change or design, and only findings proven by a run survive.

Install / Use

npx skills add michael-denyer/pstack-claude --skill interrogate

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

GitHub Copilot
OpenAI Codex

Our assessment of interrogate

interrogate scores 83/100 on our quality scale, 3029th of 4,706 Development & Engineering skills we index.

Its SKILL.md is 6.0 KB long, well organised into 15 sections and no code examples: a thorough specification that gives an agent plenty to work with.

It has 557 GitHub stars, a meaningful sign that others use it.

Substance
29/30
Structure
13/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so interrogate is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

interrogate compared with similar skills

All 4 of these similar skills score higher than interrogate; compare them before choosing.

SkillScoreStarsUpdatedFormat
interrogate (this skill)by michael-denyer8355755d agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
Agent-Reachby Panniantong100112.7k10d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md

Frequently asked questions

How do I install interrogate?
Run npx skills add michael-denyer/pstack-claude --skill interrogate. The install tabs above show the steps for each supported agent.
Which AI agents does interrogate work with?
It is written for GitHub Copilot and OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
Is interrogate safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is interrogate still maintained?
The repository was last updated about 2 months ago, so interrogate is actively maintained.

name: interrogate description: "Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles."

Interrogate

On Codex, read the platform mapping, including its per-skill notes, before following this skill.

Spawn one reviewer per configured model to adversarially review code changes. Each model gets the same prompt and rubric. The adversarial signal comes from model diversity, not assigned personas.

The deliverable is a synthesized verdict. Do NOT auto-apply changes.

Step 1, Determine Scope

Identify what to review from context:

  • If the user points at specific files or a diff, use that
  • If on a feature branch, run git diff main...HEAD (or the appropriate base branch) for the full changeset
  • If the user's message references recent work, gather the relevant files

Package the diff (or file contents) plus any surrounding context files the reviewers need to understand the code.

Step 2, State the Intent

Before spawning reviewers, state the intent explicitly. Derive this from:

  • The user's message
  • Commit messages
  • PR description if one exists
  • The code itself

Write one clear paragraph. If you're unsure about the intent, ask the user before proceeding.

Step 3, Spawn Reviewers

Launch all reviewers in a single message using the Agent tool. Use the interrogate reviewers line in the pstack-models.md override sheet (/setup-pstack lists its path per runtime), one reviewer per entry, extending or shrinking the Reviewer A/B/C labels below to the configured entry count. If the sheet or that line is missing, use the table defaults.

| Subagent | Default model | |----------|---------------| | Reviewer A | opus | | Reviewer B | fable | | Reviewer C | sonnet |

For each reviewer:

  • subagent_type: general-purpose
  • model: the configured interrogate reviewers entry, or the table default with no configured line. For an auto or inherit-parent entry, omit model so that reviewer runs on the parent model.
  • readonly: true

If the Agent tool rejects a configured entry, run that reviewer on the table default of its family and say so. Families go by model name, such as Opus, Fable, or Sonnet. With no family match, use Reviewer A's default. If it rejects a table default, check the valid slugs in the Agent tool's error message, pick the closest equivalent (prefer the highest-reasoning tier of the same family), spawn with it, and open a separate PR to update the default table. Do not block the review on the slug issue. Never treat an alias entry as a rejected slug or apply either fallback to it.

Read references/reviewer-prompt.md and fill in the template with:

  1. The stated intent
  2. The diff or file contents
  3. The review rubric from references/rubric.md
  4. The code-quality lens from references/code-quality-review.md

The same filled template goes to all reviewers, so every model applies the code-quality lens.

Step 4, Synthesize

As results come back, build a unified picture:

  1. Parse all findings from the reviewers
  2. Identify consensus. Findings raised by 2+ models independently are highest signal.
  3. Identify lone-model findings. Still worth reading, but weight accordingly.
  4. Deduplicate. Different models may describe the same issue differently. Merge these and note which models raised it.
  5. Note disagreements. If one model flags something and another explicitly says the opposite, that's useful context for the verdict.

Step 5, Lead Judgment

You are the lead reviewer, a pragmatic senior engineer, not a neutral aggregator.

Read references/lead-judgment.md for the full framework.

Categorize every finding using these buckets:

  • Act on. Real issues affecting correctness, security, or maintainability given the actual goals. These would block a real PR.
  • Consider. Legitimate points, but you're not sure they outweigh the cost of addressing them right now. Worth the user's attention.
  • Noted. Technically valid but not actionable. Context-dependent, premature optimization, or low-impact given the current stage.
  • Dismissed. Wrong, nitpicky, or missing context. Brief explanation why.

For each finding, include:

  • Which model(s) raised it
  • The category (act on / consider / noted / dismissed)
  • A one-line rationale for the categorization

Output Format

Present the verdict in this structure:

Intent

[The stated intent paragraph from Step 2]

Reviewers

  • Reviewer [label]: [model name], [N findings] (one bullet per reviewer)

Act On

[Findings that should be addressed. For each: description, which models raised it, why it matters.]

Consider

[Findings worth thinking about. For each: description, which models raised it, tradeoff involved.]

Noted

[Valid but low-priority. Brief list.]

Dismissed

[Rejected findings with brief rationale.]

Agreement Map

[Where did models agree, where did they diverge, and what does the pattern of agreement/disagreement tell us?]

Reasoning effort

A role value in the override sheet may name a reasoning effort after its model, as in opus @xhigh. Levels on Claude Code: low, medium, high, xhigh, max. Which ones apply depends on the model. A value without @ takes the sheet's default effort line, a level or session, and session when the sheet has no such line. session sets no effort, so the dispatch is the usual one. Strip the suffix before reading the model: inherit-parent or auto still omits model at every level, and a model name is passed as model. On Claude Code, a level picks the effort agent from the subagent_type you would otherwise use. pstack:poteto-agent becomes subagent_type: "pstack:poteto-agent-<level>". general-purpose, or no subagent_type, becomes subagent_type: "pstack:effort-<level>". The effort agents set only effort, so the model you pass still decides the model. On Codex, pass the level as spawn_agent's reasoning_effort and keep the usual instructions.

Related Skills

View on GitHub
GitHub Stars557
CategoryDevelopment
Updated1mo ago
Forks66

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
interrogate — GitHub Copilot Skill: Install & Safety Check | SkillAgent