Run any Skill in Manus with one click

fact-check

Stars2

Forks0

UpdatedJune 29, 2026 at 20:44

Extracts factual claims from selected text or a page and checks each against the visible context and available sources, flagging what is supported, weakened, contradicted, or still unverified. Use when the user says "fact check this", "verify", "is this true", "check the sources", or asks about a page's accuracy, credibility, or possible misinformation.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

surfmind-space

surfmind-space/awesome-surfmind

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

SKILL.md

readonly

name	fact-check
description	Extracts factual claims from selected text or a page and checks each against the visible context and available sources, flagging what is supported, weakened, contradicted, or still unverified. Use when the user says "fact check this", "verify", "is this true", "check the sources", or asks about a page's accuracy, credibility, or possible misinformation.
author	surfmind
metadata	{"icon":"CheckCheck","tags":["research"]}

Fact Check

Pull the factual claims out of the page and check each against the visible context and available sources. Never invent facts, quotes, numbers, or sources, present a guess as established, or overclaim what the evidence actually supports.

Extract concrete, checkable claims from the selected or visible content. Skip pure opinions unless they imply facts, and watch for cited sources, links, dates, and numbers that a claim should trace to.
Check each claim against the visible context, its cited sources, and any web search or MCP/tool results available. Prefer primary and official sources when a claim affects money, health, legal, safety, or reputation decisions.
Classify each claim: supported, weakly supported, unsupported, contradicted, or needs more evidence. If a claim is ambiguous (a date that conflates two events, a word like "all" or "always" that may overstate), split it or mark it weakly supported rather than forcing a clean verdict.
When support is incomplete, say what is missing and what evidence would change the verdict.

Report each claim with its Status, Evidence used, Reasoning, and what to verify next. Preserve exact names, numbers, links, dates, and currencies, and don't let a single low-quality source settle a claim on its own.

Example

Page text: "The EU AI Act took effect in 2024 and bans all facial recognition."

Claim: The EU AI Act took effect in 2024. Status: Weakly supported Evidence used: The page shows a 2024 date but blurs the entry into force date with the later phased application dates. Reasoning: The Act entered into force in 2024, yet most obligations apply later, so "took effect" is only partly accurate. Verify next: The official EU legislation timeline for when each obligation starts to apply.

Claim: The EU AI Act bans all facial recognition. Status: Contradicted Evidence used: No source on the page supports a blanket ban; the linked summary lists narrow exceptions. Reasoning: The Act restricts specific real-time biometric uses rather than banning all facial recognition, so "all" overstates it. Verify next: The exact prohibited and high-risk categories in the primary text.

More from this repository

same repository

answer

surfmind-space/awesome-surfmind

Answers a question grounded in the selected text or visible page, researching further when the page falls short, always evidence-backed and never invented. Use when the user highlights a passage or is on a page and asks "what does this mean", "answer this", "where does it say", or any who/what/why/how question about that content.

2026-06-292

api-to-example

surfmind-space/awesome-surfmind

Turns REST API documentation into a runnable curl, fetch, or code example with required headers, request body, and placeholders for secrets. Use when the user wants to generate a request from API docs, an endpoint, or a Swagger/OpenAPI spec — "give me a curl for this", "show a fetch example", "how do I call this API".

2026-06-292

bilingual-reader

surfmind-space/awesome-surfmind

Translates selected text and explains the idioms, cultural nuance, key terms, and phrasing that should not be read literally. Use when the user says "translate this", "in Spanish/French/Japanese/etc.", "what does this mean", "explain this phrase", or wants foreign-language text rendered with the context behind it.

2026-06-292

calendar-prep

surfmind-space/awesome-surfmind

Turns an event page, calendar invite, email, or notes into key details, an agenda, a preparation checklist, and follow-up reminders. Use when the user wants to prepare for a meeting, event, or appointment, or asks for meeting prep, an agenda, or a prep checklist before an upcoming event.

2026-06-292

caption-assistant

surfmind-space/awesome-surfmind

Writes captions, accessibility alt text, and short image or page descriptions tailored to the visible content and audience. Use when the user asks to "describe this image", "write alt text", "caption this", or needs screen reader text, a11y descriptions, image descriptions, or social captions.

2026-06-292

chart-explainer

surfmind-space/awesome-surfmind

Explains a visible chart by identifying axes, trends, outliers, and the practical takeaway while flagging missing context. Use when the user shares a chart, graph, plot, or data visualization — bar, line, pie, scatter — and asks what it shows, means, or whether the data supports a decision.

2026-06-292

name	fact-check
description	Extracts factual claims from selected text or a page and checks each against the visible context and available sources, flagging what is supported, weakened, contradicted, or still unverified. Use when the user says "fact check this", "verify", "is this true", "check the sources", or asks about a page's accuracy, credibility, or possible misinformation.
author	surfmind
metadata	{"icon":"CheckCheck","tags":["research"]}

Fact Check

Extract concrete, checkable claims from the selected or visible content. Skip pure opinions unless they imply facts, and watch for cited sources, links, dates, and numbers that a claim should trace to.
Check each claim against the visible context, its cited sources, and any web search or MCP/tool results available. Prefer primary and official sources when a claim affects money, health, legal, safety, or reputation decisions.
Classify each claim: supported, weakly supported, unsupported, contradicted, or needs more evidence. If a claim is ambiguous (a date that conflates two events, a word like "all" or "always" that may overstate), split it or mark it weakly supported rather than forcing a clean verdict.
When support is incomplete, say what is missing and what evidence would change the verdict.

Example

Page text: "The EU AI Act took effect in 2024 and bans all facial recognition."

Claim: The EU AI Act took effect in 2024. Status: Weakly supported Evidence used: The page shows a 2024 date but blurs the entry into force date with the later phased application dates. Reasoning: The Act entered into force in 2024, yet most obligations apply later, so "took effect" is only partly accurate. Verify next: The official EU legislation timeline for when each obligation starts to apply.

Claim: The EU AI Act bans all facial recognition. Status: Contradicted Evidence used: No source on the page supports a blanket ban; the linked summary lists narrow exceptions. Reasoning: The Act restricts specific real-time biometric uses rather than banning all facial recognition, so "all" overstates it. Verify next: The exact prohibited and high-risk categories in the primary text.