antinet-four-color-cards

Generates traceable fact, explanation, risk, and action cards from parsed documents.

6.0k|578|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/anbeime/skill --skill antinet-four-color-cards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: antinet-four-color-cards
Source: https://github.com/anbeime/skill/tree/main/skills/antinet-four-color-cards
Command: npx skills add https://github.com/anbeime/skill --skill antinet-four-color-cards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Financial analysts, legal assistants, and researchers often struggle to turn long parsed documents into rigorous, auditable analysis. This Skill converts structured Markdown documents into four color-coded card types—blue (facts), green (explanations), yellow (risks), and red (actions)—with every claim traceable to a source fragment.

Core Features & Use Cases

  • Four-Color Card Generation: Produces fact cards with source citations, explanation cards, risk cards flagging overstatements and uncertainty, and action cards with next-step recommendations.
  • Multi-Stage Pipeline: Runs three stages (extract, review, propose) mapped to dedicated worker agents, with citation chaining enforced so green cards cite blue cards and red cards cite green/blue cards.
  • Graceful Degradation: Falls back to a rule-based engine when the LLM is unavailable, marks low-confidence parses for manual review, and labels unreviewed risk cards as pending.
  • Use Case: A financial analyst feeds a parsed research report into the skill and receives a structured JSON set of sourced facts, mechanism explanations, flagged overstatements, and recommended actions for an audit-ready report.

Quick Start

Run the four-color-cards skill on my parsed Markdown document to generate traceable fact, explanation, risk, and action cards.

Frequently Asked Questions about antinet-four-color-cards

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

FAQPage Schema
How do I generate traceable fact and risk cards from a document?

Run the skill's staged pipeline: extract produces fact cards with source fragments, review produces explanation and risk cards, and propose produces action cards. Each card cites its upstream sources, and claims without sources are blocked from output.

What are the four card types in document analysis workflows?

Blue cards hold sourced facts, green cards explain mechanisms and gaps, yellow cards flag overstatements and uncertainty, and red cards recommend next actions. Together they form an auditable structure for research and compliance analysis.

Does the four-color card generation work without an LLM?

Yes, it degrades to a rule-based engine when the LLM is unavailable. In that mode the risk and action cards are explicitly labeled as generated without LLM support.

What happens when the risk review step times out?

The yellow risk card is delivered using the rule-engine result and marked with a pending_review flag. It can be finalized later once the review worker completes its overstatement check.

What are the limitations of card-based document analysis?

Facts without identifiable sources are labeled as unsourced rather than asserted, and low parse confidence triggers manual review flags. The approach depends on the quality of the upstream document parsing stage.