Guardrailed Writer Fact-Check

Verify claims against local artifacts and allowlisted sources with budgeted checks.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/JDL440/nfl-eval --skill guardrailed-writer-fact-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Guardrailed Writer Fact-Check
Source: https://github.com/JDL440/nfl-eval/tree/main/.squad/skills/guardrailed-writer-fact-check
Command: npx skills add https://github.com/JDL440/nfl-eval --skill guardrailed-writer-fact-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting often includes unchecked claims and revision churn; this Skill provides a bounded, deterministic fact-checking workflow that reuses existing artifacts and telemetry to support editors without inviting uncontrolled external research.

Core Features & Use Cases

  • Deterministic source ladder: prefer local artifacts first, official primary sources second, trusted references third, with escalation blocked or escalated as needed.
  • Narrow resolver helper: expose an allowlisted fetch helper rather than freeform browsing to maintain policy and speed.
  • Budgeted checks and time: cap external lookups and wall-clock time, with telemetry to track usage and cost.
  • Durable artifacts: persist which claims were verified, attributed, softened, or omitted, with sources and budget summaries.
  • Editor as final authority: the verification pass aids editors but does not replace decision-making.

Quick Start

Integrate the writer-factcheck step into your drafting workflow to automatically verify claims against local artifacts and approved sources.

Frequently Asked Questions about Guardrailed Writer Fact-Check

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

FAQPage Schema
How do I automate fact-checking for drafting against local artifacts and approved sources?

To automate fact-checking for drafting, this Skill uses a deterministic source ladder that verifies claims by checking local artifacts first, then official primary sources, and trusted references third. It persists verification results as durable artifacts.

What is a source ladder and how does it work for editorial claim verification?

A source ladder is a deterministic hierarchy for claim verification that prioritizes local artifacts first, official primary sources second, and trusted references third. It blocks or escalates verification as needed to maintain accuracy without uncontrolled external research.

Can I restrict external lookups and control costs during the fact-checking workflow?

Yes, you can restrict external lookups using an allowlisted resolver helper instead of freeform browsing. The workflow caps external checks and wall-clock time, tracking usage and cost through built-in telemetry to maintain budget constraints.

Does the fact-checking process replace the editor's final decision-making authority?

No, the fact-checking process aids editors but does not replace decision-making. The editor remains the final authority, ensuring the automated verification pass supports editorial drafting, reviews, and final gates without overriding human judgment.

How do I track which claims were verified, attributed, or omitted during drafting?

You track verified, attributed, softened, or omitted claims through durable artifacts. The workflow persists these records alongside their sources and budget summaries, ensuring a clear audit trail for editorial review and final gates.

When should I use a bounded fact-checking workflow instead of freeform browsing for revisions?

Use a bounded fact-checking workflow when drafting includes unchecked claims and revision churn. It reuses existing artifacts and telemetry to support editors with deterministic verification, preventing the uncontrolled external research that freeform browsing invites.