self-critique

Generate counter-arguments to challenge analysis before finalizing conclusions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cris-m/flopsy --skill self-critique-cris-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-critique
Source: https://github.com/cris-m/flopsy/tree/main/src/team/templates/skills/self-critique
Command: npx skills add https://github.com/cris-m/flopsy --skill self-critique-cris-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify and challenge your own reasoning before presenting conclusions, reducing overconfidence and blind spots.

Core Features & Use Cases

  • Provides a structured self-critique workflow to draft, pause for evaluation, and generate counter-arguments.
  • Encourages bias checks and confidence calibration across high-stakes decisions.
  • Useful during analysis-heavy tasks, research reporting, and policy discussions.

Quick Start

Provide your current conclusion and prompt for a self-critique to uncover at least two substantial counter-arguments.

Frequently Asked Questions about self-critique

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

FAQPage Schema
How do I use self-critique to challenge my own analysis before finalizing a conclusion?

Self-critique challenges your analysis by generating counter-arguments before finalizing a stance. You provide a drafted interpretation or recommendation, and the workflow pauses to surface underlying assumptions, counter-evidence, and potential biases.

What is confidence calibration and when do I need it for high-stakes decisions?

Confidence calibration adjusts your certainty level by actively checking for biases and counter-evidence. It is needed during high-stakes decisions, research reporting, and policy discussions to reduce overconfidence and blind spots in your conclusions.

How do I generate counter-arguments to check for bias in my decision-support workflow?

To generate counter-arguments, input your current conclusion into the self-critique workflow. The process forces an evaluation pause to uncover at least two substantial counter-arguments, surfacing hidden assumptions and checking biases before you commit.

Can I apply self-critique during research reporting and policy discussions?

Yes, self-critique is designed for analysis-heavy tasks including research reporting and policy discussions. It provides a structured workflow to draft interpretations, pause for evaluation, and generate counter-arguments to strengthen your final recommendations.

What's the best way to surface hidden assumptions in a substantive analysis?

The best way to surface hidden assumptions is applying a structured self-critique workflow after drafting an interpretation. By forcing counter-argument generation before finalizing a stance, you expose underlying biases and counter-evidence.

Does this self-critique workflow require any external scripts or dependencies to run?

No external dependencies are required. The self-critique workflow operates through a frontmatter-defined entry point, though it can optionally reference scripts, references, and assets to support the structured evaluation process.