rhea-morgan

Cross-check edition factual claims against canonical rosters and desk packets.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/pnils08/GodWorld --skill rhea-morgan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rhea-morgan
Source: https://github.com/pnils08/GodWorld/tree/main/.claude/agents/rhea-morgan
Command: npx skills add https://github.com/pnils08/GodWorld --skill rhea-morgan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that the editions produced by desks align with canonical data sources, catching discrepancies in citizen names, vote positions, rosters, and associated metadata before publication. This allows editors to prevent misstatements and maintains continuity with the established canon.

Core Features & Use Cases

  • Cross-checks compiled editions against primary canon sources such as citizen rosters, vote trackers, and sports rosters.
  • Memory-aware verification to surface recurrent errors, known phantom entries, and canonical corrections from past editions.
  • Generates a structured error list and a detailed CLAIM DECOMPOSITION to guide corrections and ensure auditability.

Quick Start

Run the verification workflow after edition compilation to generate a pre-publication report and a detailed discrepancy log.

Frequently Asked Questions about rhea-morgan

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

FAQPage Schema
How do I verify edition accuracy against canonical data sources before publication?

To verify edition accuracy, cross-check every factual claim in the edition against canonical data sources like civic rosters, sports rosters, and desk packets to catch discrepancies in names, vote positions, and metadata before publication.

How do I cross-check vote tallies and citizen identities for canon consistency?

Cross-check vote tallies and citizen identities by validating them directly against canonical references. This process identifies inconsistencies in roster positions and associated metadata, ensuring all entries match the established canon.

What is the best way to generate a structured fact-checking report for published editions?

The best way to generate a fact-checking report is to run a verification workflow that produces a structured discrepancy log detailing errors, warnings, and claim decompositions to guide corrections and ensure auditability.

Can I detect recurrent errors and phantom entries from past editions during canon verification?

Yes, memory-aware canon verification can surface recurrent errors, known phantom entries, and canonical corrections from past editions, preventing repeated misstatements and maintaining continuity with the established canon.

Does fact-checking compiled editions require external dependencies or components?

Fact-checking compiled editions requires no external dependencies or components. The verification workflow operates independently to validate compiled editions against primary canon sources like citizen rosters and vote trackers.

When should I run a canon consistency check in the edition compilation workflow?

You should run a canon consistency check immediately after edition compilation to generate a pre-publication report, catching any metadata discrepancies before the edition is released.