interrogate SKILL.md skillA

interrogate from nightly-labs/openbot is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add nightly-labs/openbot/interrogate@git:20261013.9e6954c

Pins git:20261013.9e6954c in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

nightly-labs/openbot

Path

marketplace/production-catalog/bundles/pstack/skills/interrogate/SKILL.md

Versions recorded

1

Latest version

git:20261013.9e6954c, committed Oct 13, 2026

Size

4,317 bytes

Repository stars

5,267

License

a license file GitHub does not identify

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.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Interrogate

Spawn one reviewer per configured model to adversarially review code changes. The adversarial signal comes from model diversity, not assigned personas. The deliverable is a synthesized verdict. Do NOT auto-apply changes.

## Step 1, 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 with any surrounding context files the reviewers need to understand the code.

## Step 2, Intent

Before spawning reviewers, state the intent in one clear paragraph from the user's message, commit messages, the PR description if one exists, and the code. If you're unsure about the intent, ask the user before proceeding.

## Step 3, Spawn Reviewers

Launch all reviewers in a single message with the Task tool, one per entry on the `interrogate reviewers` line in `~/.cursor/rules/pstack-models.mdc`, labeled Reviewer A, B, and so on to match the entry count. If the rule or that line is missing, use the table defaults.
…

Read the whole file at its exact version.

How to install

mdr add nightly-labs/openbot/interrogate@sha256:25341c393f515c1e

[![mdr](https://markdownregistry.com/badge/art_4hdik24wxjcf2lrv.svg)](https://markdownregistry.com/a/art_4hdik24wxjcf2lrv)

Versions

The registry has recorded 1 version of this file, committed on Oct 13, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_4hdik24wxjcf2lrv
GET https://markdownregistry.com/api/v1/resolve?ref=nightly-labs/openbot/interrogate
GET https://markdownregistry.com/api/v1/blob/25341c393f515c1e1fa9bce668b7551e9f98c195113a460ff524d3c1f7f50cd9

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from nightly-labs/openbot

Every file in nightly-labs/openbot

Other files named interrogate

Browse by kind, by grade A, or by owner.