criticism-self-criticism

Review completed work for errors, omissions, and quality gaps.

Updated May 17, 2026
One-click install
npx skills add https://github.com/tiankong0101-byte/skills-registry --skill criticism-self-criticism-tiankong0101-byte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: criticism-self-criticism
Source: https://github.com/tiankong0101-byte/skills-registry/tree/main/skills/criticism-self-criticism
Command: npx skills add https://github.com/tiankong0101-byte/skills-registry --skill criticism-self-criticism-tiankong0101-byte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review completed work honestly, process criticism without defensiveness, and turn mistakes into concrete corrective actions. It is useful when a task has finished, a review checkpoint arrives, recurring errors need diagnosis, or you need a structured retrospective.

Core Features & Use Cases

  • Structured self-review: Examine whether goals were met, what was skipped, and where validation or investigation was insufficient.
  • Feedback processing: Handle criticism based on facts, distinguish valid points from misunderstandings, and respond constructively.
  • Root-cause correction: Identify specific errors, explain their impact, and propose actionable improvements instead of vague judgments.
  • Use case: After a deliverable is reviewed, use this Skill to produce a clear audit report listing completed items, issues found, strengths, and next-step focus areas.

Quick Start

Use the criticism-self-criticism skill to evaluate this completed work and produce a structured review report with specific issues, root causes, strengths, and next-step focus areas.

Frequently Asked Questions about criticism-self-criticism

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

FAQPage Schema
How do I conduct a structured self-review of completed work?

Conduct a structured self-review by factually examining whether goals were met, identifying what was skipped, and validating where investigation was insufficient. This process requires specific issue identification, root-cause analysis, and actionable correction planning to turn findings into concrete improvements.

What is the best way to process feedback and criticism without getting defensive?

Processing feedback requires handling criticism based strictly on facts, distinguishing valid points from misunderstandings, and responding constructively. You must identify specific errors, explain their impact, and propose actionable improvements instead of offering vague judgments or defensive reactions.

How do I diagnose recurring mistakes in my deliverables?

Diagnose recurring mistakes by performing a root-cause correction analysis on completed work. Identify specific errors, explain their impact on the deliverable, and propose actionable improvements to replace vague judgments and prevent the same mistakes from happening again.

Can I use this approach to generate a retrospective audit report for a project?

Yes, you can use this approach to generate a clear audit report after a deliverable is reviewed. The report will list completed items, issues found, strengths, and next-step focus areas, providing a structured retrospective for post-delivery review checkpoints.

What should a quality check include when reviewing a finished task?

A quality check should include a structured self-critique that examines whether goals were met, what was skipped, and where validation was insufficient. It must feature fact-based evaluation, specific issue identification, root-cause analysis, and actionable correction planning.

When do I need a formal root-cause analysis for my work?

You need a formal root-cause analysis when a task has finished, a review checkpoint arrives, or recurring errors need diagnosis. It helps identify specific errors, explain their impact, and propose actionable improvements during structured retrospectives and post-delivery reviews.