pretty-but-wrong

Enumerate unsourced claims, stale data, and calculation errors in AI-generated documents.

4|1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/m2ai-portfolio/m2ai-skills-pack --skill pretty-but-wrong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pretty-but-wrong
Source: https://github.com/m2ai-portfolio/m2ai-skills-pack/tree/main/skills/pretty-but-wrong
Command: npx skills add https://github.com/m2ai-portfolio/m2ai-skills-pack --skill pretty-but-wrong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-generated documents often look polished but can contain unsourced claims, outdated data, or obvious reasoning gaps. This skill provides a structured hostile-review pass to surface those issues before sharing with decision-makers.

Core Features & Use Cases

  • Enumerates unsourced claims, stale data, and calculation errors without rewriting or fixing content.
  • Produces a prioritized issue list with categories and severity, suitable for review cycles, governance, and risk assessment.
  • Use Case: before distributing a board deck or external proposal, run this review to surface must-fix issues and get a clear remediation plan.

Quick Start

Use the hostile-review workflow to generate a ranked issue list for a document before distribution.

Frequently Asked Questions about pretty-but-wrong

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

FAQPage Schema
How do I fact-check AI-generated documents for unsourced claims before sharing?

To fact-check AI-generated documents, run a structured hostile-review process that identifies and enumerates unsourced claims, stale data, and calculation errors. This produces a prioritized issue list with categories and severity for risk assessment.

What is the best way to review an AI-generated board deck for calculation errors?

The best way to review an AI-generated board deck is to apply a hostile-review workflow with category-specific checks. This surfaces must-fix calculation errors and reasoning gaps, yielding a clear ranked issue list without rewriting content.

How do I surface data integrity issues in AI proposals without altering the original content?

To surface data integrity issues without altering content, use a review workflow that enumerates problems and produces a remediation plan. It explicitly avoids making fixes, leaving the original AI deliverables intact while highlighting risks.

Can I use a structured review workflow to assess document quality for external audiences?

Yes, you can use a structured review workflow to assess document quality for external audiences. It applies category-specific checks to proposals and reports, weighting issues like unsourced claims to ensure deliverables are safe for distribution.

What happens to my document during a hostile-review pass for AI deliverables?

During a hostile-review pass for AI deliverables, your document is analyzed for errors but not modified. The process identifies issues across internal and external audiences and outputs a ranked issue list suitable for governance and review cycles.