Business Report
Rumor / Claim Verification
AI Tool:
GrokWorks with Grok
Category: Reports
Trace a claim to its origin, verdict it, and check how hard it is spreading on X and the web right now.
Prompt Quality - 95/100 · Strong
The Prompt
grok-rumor-claim-verification.md
Fact-check this claim properly - trace it back to where it actually started if you can, not just whether it "sounds true." Use live web and X search. THE CLAIM: {{claim}} WHERE I SAW IT: {{where_seen}} INSTRUCTIONS: 1. Search for the origin of this claim - where it first appeared, and whether it changed or got exaggerated as it spread (a common pattern: a hedge like "reportedly" or "sources suggest" gets dropped as it's repeated). 2. Find the strongest primary source for or against it - not a chain of articles all citing each other. The actual original evidence if it exists. 3. Give a clear verdict: True, False, Partially True (specify what part), Unverifiable (and why), or Outdated (was true, no longer is). 4. If the claim is technically true but misleading in how it's being presented, say that explicitly - this is different from "false." 5. Note how widely it's actually spreading right now versus how big a deal it's being treated as, if that's relevant. OUTPUT FORMAT: - Origin trace (where it started, how it's changed) - Strongest evidence for and against - Verdict (with the exact category from above) - "Technically true but misleading" flag if applicable - Current spread / scale note if relevant CONSTRAINTS: - Don't default to "there's truth on both sides" just to hedge - most claims resolve to a real verdict once you actually trace them. - If you can't find the original source, say that plainly instead of treating a repeated claim as its own evidence.
Negative prompt
Included when you copy the prompt
Do not treat a repeated claim as its own evidence. Do not both-sides a claim that has a real verdict. Do not invent an origin story. Do not skip the technically-true-but-misleading case when it applies.
The PromptUTF-8
Fill in your details below - this prompt updates as you type, then copy it.
Fill in your details
0 of 2 filled. Preview updates as you type - then copy the finished prompt (negative prompt included when present).
grok-rumor-claim-verification.md
Prompt preview
Fact-check this claim properly - trace it back to where it actually started if you can, not just whether it "sounds true." Use live web and X search. THE CLAIM: {{claim}} WHERE I SAW IT: {{where_seen}} INSTRUCTIONS: 1. Search for the origin of this claim - where it first appeared, and whether it changed or got exaggerated as it spread (a common pattern: a hedge like "reportedly" or "sources suggest" gets dropped as it's repeated). 2. Find the strongest primary source for or against it - not a chain of articles all citing each other. The actual original evidence if it exists. 3. Give a clear verdict: True, False, Partially True (specify what part), Unverifiable (and why), or Outdated (was true, no longer is). 4. If the claim is technically true but misleading in how it's being presented, say that explicitly - this is different from "false." 5. Note how widely it's actually spreading right now versus how big a deal it's being treated as, if that's relevant. OUTPUT FORMAT: - Origin trace (where it started, how it's changed) - Strongest evidence for and against - Verdict (with the exact category from above) - "Technically true but misleading" flag if applicable - Current spread / scale note if relevant CONSTRAINTS: - Don't default to "there's truth on both sides" just to hedge - most claims resolve to a real verdict once you actually trace them. - If you can't find the original source, say that plainly instead of treating a repeated claim as its own evidence.
0 / 2 filledPreview
When to use this prompt
Use it when
- You need help with researchers.
- You need help with founders.
- You need help with operators.
- You need help with writers.
Skip it when
- You only need a one-line ask with no constraints, format, or context.
- You cannot supply the fill-in details the template asks for.
- A different category or tool-specific workflow fits the job better.
How to get a good result
Done when
The output clearly completes “Rumor / Claim Verification”: it matches the requested format, uses your filled-in details, and is ready to use without another prompting round.
Common mistakes
- Leaving claim, where_seen vague - the model then invents placeholders.
- Asking Grok for a shorter answer after a long structured prompt - that throws away the format rules.
- Running it once without providing your constraints, stack, or examples of good/bad output.
FAQ
- What do I fill in before I copy this prompt?
- Replace these placeholders with your details: claim, where_seen. Required fields are marked on the page. The prompt text updates as you type.
- Which AI tools is this prompt written for?
- It works best with Grok. Copy the filled prompt and paste it into the tool you already use.
- What should a good result look like?
- The output clearly completes “Rumor / Claim Verification”: it matches the requested format, uses your filled-in details, and is ready to use without another prompting round.
- What are common mistakes with this prompt?
- Leaving claim, where_seen vague - the model then invents placeholders. Asking Grok for a shorter answer after a long structured prompt - that throws away the format rules. Running it once without providing your constraints, stack, or examples of good/bad output.
Best for
- Researchers
- Founders
- Operators
- Writers
Related Prompts
More prompts like this — same topic and style.