CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interrogate

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.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An excellent orchestration skill: concrete, executable, and well-sequenced, with clean progressive disclosure into four real and well-matched reference files. The only flaw is minor intra-document redundancy between the intro paragraph and the synthesis step.

DimensionReasoningScore

Conciseness

The body is efficient, operational, and free of concept explanations Claude already knows, but contains minor trimmable redundancy — e.g., the intro's "Agreement across models is high-confidence signal; lone-model findings are worth reading but lower confidence" repeats Step 4's consensus/lone-model weighting.

4 / 5

Actionability

Fully executable guidance throughout: a concrete command (`git diff main...HEAD`), exact spawn parameters (`subagent_type: pstack:readonly-agent`, model list handling), a model-slug fallback procedure, a numbered template-fill list, and an exact output structure — all four referenced files exist and match their described purposes.

5 / 5

Workflow Clarity

Five unambiguously sequenced steps with explicit checkpoints (ask the user before proceeding if intent is unclear; substitute the closest valid model slug on spawn failure) and clearly defined synthesis and categorization procedures. The workflow is read-only with "Do NOT auto-apply changes", so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

The SKILL.md is a concise process overview with well-signaled, one-level-deep references (reviewer-prompt.md, rubric.md, code-quality-review.md, lead-judgment.md) that all exist, are appropriately split out, and are navigated to with clear "Read X and fill in the template" / "Read X for the full framework" instructions.

5 / 5

Total

19

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed invocation-oriented description with an explicit trigger list and a clear capability statement. Its main weaknesses are a thin "what" (one composite action rather than several concrete capabilities) and a small amount of trigger-synonym coverage left on the table.

Suggestions

Expand the "what" statement to name 2-3 concrete capabilities, e.g., "Multiple LLM reviewers challenge changes from independent angles, then a lead-judgment pass filters findings into act-on/consider/noted/dismissed categories."

Add one or two more natural trigger variants such as "critique this code" or "red-team this change" to broaden trigger coverage.

Consider qualifying "stress test this code" (e.g., "stress test this change") to reduce overlap risk with performance/load-testing skills.

DimensionReasoningScore

Specificity

"Multiple LLM reviewers challenge changes from independent angles" names the domain and one concrete action, but the description does not list several specific capabilities (e.g., synthesizing findings, lead-judgment filtering) the way a 4 or 5 would.

3 / 5

Completeness

Both "what" ("Multiple LLM reviewers challenge changes from independent angles") and "when" (an explicit "Use for ..." clause with concrete quoted trigger phrases) are clearly and explicitly answered, matching the top anchor.

5 / 5

Trigger Term Quality

Seven natural trigger phrases spanning registers ("interrogate", "adversarial review", "challenge this", "stress test this code", "find blind spots", "tear this apart") give good keyword coverage, but a few plausible variants like "critique this code" or "red-team this" are missing.

4 / 5

Distinctiveness Conflict Risk

The multi-model adversarial-review niche is well differentiated with distinct triggers, but "stress test this code" could plausibly trigger a performance/load-testing skill, creating minor overlap risk.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

adamsardo/pstack-claude

Path

plugins/pstack/skills/interrogate/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.