interrogate
Optional adversarial cross-model review to challenge a design or find blind spots, using per-call agent models or host delegation.
Skill by matthewyjiang
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/matthewyjiang-interrogate
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: documents, design, agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/interrogate
What's inside
- Skill name
interrogate- Description
- Optional adversarial cross-model review to challenge a design or find blind spots, using per-call agent models or host delegation. Report unavailable model selection honestly; thermos remains the portable combined PR review.
- License
- MIT
- Instructions
- 45 lines in SKILL.md · view on GitHub
Files (5)
- SKILL.md
- code-quality-review.md · references/
- lead-judgment.md · references/
- reviewer-prompt.md · references/
- rubric.md · references/
SKILL.md (first lines)
# Interrogate Read [the workflow contract](../../references/workflow-contract.md) and [review routing](../../references/review-routing.md). Model diversity—not personas on one model—is the independent signal here. It uses `reviewer`, not the thermos lens agents; no model pins in definitions, edits or automatic fixes. Models come from per-call `model` on Rho's `agent`, or from host model-selecting delegation. 1. **Scope and intent.** Resolve the requested files/diff/PR and actual base/head, not an assumed main. Pin requested working-tree evidence if applicable. State the intended outcome and repository constraints; ask only if missing intent materially changes correctness. Parent gathers all Git/PR evidence and pinned context. A moving snapshot invalidates affected conclusions. 2. **Check capability.** Prefer `reviewer` calls with per-call `model` (see review routing), using models the user named or configured aliases; ask once if none are known. Otherwise discover the host's model-selecting delegation API (in T3, `orchestrator_capabilities`, `delegate_task` and the live catalog). Choose at least two genuinely different model families; do not infer diversity from different IDs. Without either, state **cross-model interrogation unavailable**, and offer an ordinary same-model `reviewer` pass only if the user accepts. Do not install definitions or change global configuration. 3. **Launch.** Fill `references/reviewer-prompt.md` with the same intent, pinned scope/evidence, `references/rubric.md`, `references/code-quality-review.md` and workflow contract contents for every reviewer. Supply actual text, not unresolved paths. Require read-only operation, no builds/tests, no delegation, no external actions, and explicit missing-context/status reports. Use immutable evidence or supplied snapshots, never mutable-worktree substitutes. Launch independent child runs in one batch (host tasks follow host instructions). Record run IDs, actual models and any errors/substitutions; no top-level conversations or homemade shell model runner. Await every required completion, without polling loops or duplicate work. Failed/unavailable routes are not clean reviews. 4. **Synthesize.** Deduplicate by actual issue, keep model attribution and disagreements. Apply `references/lead-judgment.md`; verify real paths/counterevidence before accepting or dismissing. Consensus is signal, never proof; a lone security or correctness finding still warrants investigation. 5. **Judge.** Sort into Act on (concrete material issue), Consider (valid tradeoff), Noted (not actionable now), Dismissed (wrong/context/style, with rationale). Return Intent; Reviewers (actual provider/model, status, finding count); Act on / Consider / Noted / Dismissed with evidence/remedies; Agreement map; failures and unreviewed areas. Never describe a user-accepted same-model alternative as cross-model interrogation. For PR work, use `thermos` as the one combined review unless a distinct interrogation was requested; do not stack redundant review runs.
From matthewyjiang/rho-pstack, MIT.
More from matthewyjiang/rho-pstack
- 0.567score
how
matthewyjiang
Explain subsystem architecture, runtime flow, placement, ownership, or layering before changing code.
SkillAFreshness: AClaude Code +9 - 0.567score
architect
matthewyjiang
Sketch caller usage, types, signatures and module ownership before nontrivial implementation.
SkillAFreshness: AClaude Code +9 - 0.561score
blast-radius
matthewyjiang
Trace what a change could break beyond its diff and prove the load-bearing safety assumptions through real code.
SkillAFreshness: AClaude Code +9 - 0.561score
correct
matthewyjiang
Turn recurring agent mistakes into structural prevention: architecture, types, actionable lint, then behavior tests.
SkillAFreshness: AClaude Code +9 - 0.536score
principle-boundary-discipline
matthewyjiang
Apply when wiring validation, error handling, or framework adapters.
SkillAFreshness: AClaude Code +9 - 0.536score
principle-build-the-lever
matthewyjiang
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks.
SkillAFreshness: AClaude Code +9 - 0.531score
principle-experience-first
matthewyjiang
Apply when product, UX, or feature-scope tradeoffs come up.
SkillAFreshness: AClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Oct 17, 2026 (12 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/matthewyjiang/rho-pstack
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from matthewyjiang
- 0.567score
how
matthewyjiang
Explain subsystem architecture, runtime flow, placement, ownership, or layering before changing code.
SkillAFreshness: AClaude Code +9 - 0.567score
architect
matthewyjiang
Sketch caller usage, types, signatures and module ownership before nontrivial implementation.
SkillAFreshness: AClaude Code +9 - 0.561score
blast-radius
matthewyjiang
Trace what a change could break beyond its diff and prove the load-bearing safety assumptions through real code.
SkillAFreshness: AClaude Code +9 - 0.561score
correct
matthewyjiang
Turn recurring agent mistakes into structural prevention: architecture, types, actionable lint, then behavior tests.
SkillAFreshness: AClaude Code +9 - 0.536score
principle-boundary-discipline
matthewyjiang
Apply when wiring validation, error handling, or framework adapters.
SkillAFreshness: AClaude Code +9 - 0.536score
principle-build-the-lever
matthewyjiang
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks.
SkillAFreshness: AClaude Code +9
Cite this page
interrogate skill. Agent Mart. https://agentmart.dev/skills/matthewyjiang-interrogate (last updated 2026-10-24)