critic

Review agent plans and test code for logical errors and untested assumptions.

3|4|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/nicsuzor/academicOps --skill critic-nicsuzor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critic
Source: https://github.com/nicsuzor/academicOps/tree/main/.agent/skills/critic
Command: npx skills add https://github.com/nicsuzor/academicOps --skill critic-nicsuzor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a skeptical, independent review of agent-generated plans and conclusions, catching logical errors, untested assumptions, and scope drift before they impact outcomes.

Core Features & Use Cases

  • Logical Error Detection: Identifies flawed reasoning and non-sequiturs.
  • Assumption Validation: Flags claims taken for granted without evidence.
  • Scope Adherence: Ensures plans directly address the original request.
  • Edge Case Identification: Highlights potential failure points.
  • Test Code Review: Specifically checks for common anti-patterns in test code.
  • Use Case: Before an agent presents a complex research plan, the Critic agent reviews it to ensure the methodology is sound and all necessary steps are accounted for, preventing wasted effort on flawed strategies.

Quick Start

Activate the critic skill to review the provided plan for logical errors and untested assumptions.

Frequently Asked Questions about critic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review agent plans for logical errors and untested assumptions?

You can catch untested assumptions by applying a skeptical second-opinion review to agent conclusions. This critique identifies untested assumptions and scope drift, returning a structured verdict of PROCEED, REVISE, or HALT.

What is a Volkswagen pattern in test code review?

A Volkswagen pattern in test code review is a common anti-pattern where tests falsely pass under inspection. A critical review identifies this pattern by checking for semantic verification, real fixtures, and demo test existence.

How do I validate edge cases before presenting a complex research plan?

You validate edge cases by applying an independent critical lens to the research plan, highlighting potential failure points and untested assumptions. This ensures methodology is sound and prevents wasted effort on flawed strategies.

Does automated plan review check for scope drift?

Yes, an independent skeptical review checks for scope drift by ensuring plans directly address the original request. It identifies non-sequiturs and validates that the methodology remains within the defined boundaries.

When should I use a second-opinion review on agent conclusions?

You should use a second-opinion review before agent conclusions impact outcomes, specifically to catch overconfident claims and missing edge cases. This structured critique prevents executing on flawed strategies.