abstain-or-escalate

Decides how to handle claims that verification could not confirm.

4|1|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/radarist/structured-analytic-skills --skill abstain-or-escalate-radarist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: abstain-or-escalate
Source: https://github.com/radarist/structured-analytic-skills/tree/main/skills/abstain-or-escalate
Command: npx skills add https://github.com/radarist/structured-analytic-skills --skill abstain-or-escalate-radarist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a verification pass comes back empty, writers face a choice: ship a hedged guess or handle the gap honestly. This Skill replaces the hedged hallucination with an explicit disposition — drop the claim, refuse it in plain words, escalate it as a named open question, or report the disagreement between conflicting sources. ## Core Features & Use Cases - Load-bearing test: Distinguishes claims whose removal would change a decision from peripheral filler that can be silently dropped. - Four explicit dispositions: Abstain-and-ask, escalate, abstain outright, or report disagreement — each with plain-words wording templates and no "probably" or "I think". - Recoverable gap records: Leaves <!-- abstained: ... --> markers in documents and structured open-question notes so later passes can backfill rather than rediscover. - Use Case: A market brief contains an unsourced shipment figure that drives its conclusion. The Skill tests that the claim is load-bearing, records the search performed, writes a plain-words abstention naming what would close the gap, and leaves a marker in the document. ## Quick Start Use the abstain-or-escalate skill to decide what to do with the unsourced claims in my draft report.

Frequently Asked Questions about abstain-or-escalate

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

FAQPage Schema
What should I do when there is no source for a claim in my report?▼

First test whether the claim is load-bearing — whether removing it would change a decision or conclusion. If not, drop it silently; if yes, choose an explicit disposition: abstain outright, escalate as a named open question, or ask for the missing input, never soften it with "probably".

How do I handle two sources that contradict each other?▼

Report the disagreement rather than silently picking one source. Cite both sources, state which is weighted higher and why (primacy, recency, or grade), and widen the downstream conclusion into a range instead of a point estimate.

When should I abstain versus escalate an unverifiable claim?▼

Escalate when the answer needs research beyond current reach, such as a paid database or specialist, and name where the answer likely lives. Abstain outright when the claim is consequential and only a guess is available; abstain-and-ask when the requester can supply the missing context.

Should I run verification before using abstain-or-escalate?▼

Yes. This skill starts where verification fails — run a Chain-of-Verification pass (draft, verification questions, independent answers, revision) first. Only route claims here after that pass returns no usable source.

How are abstained claims recorded so they can be fixed later?▼

In documents, leave an HTML comment marker at the claim site, such as <!-- abstained: {claim} — no source as of {date} -->. For escalations, log the open question with the specific gap and the source type that would close it.