Agent skill

Verify Claims

by LeoYeAI in LeoYeAI/openclaw-master-skills

Verify claims and information using professional fact-checking services.

MITAuto-check passedResearch & Science

Install Verify Claims

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill verify-claims -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills verify-claims --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/verify-claims .claude/skills/verify-claims && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
verify-claims
GitHub stars
2.2k
Token cost
~4.9k tokens
SKILL.md length
2,139 words
Files
2
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Verify claims and information using professional fact-checking services.

  • Works in 5 steps: Understand the Content → Select Fact-Checking Services → Search Each Fact-Checking Service → …
  • Users want to verify facts
  • SKILL.md covers Core Principles, When to Use This Skill, Workflow and Common Scenarios, plus 4 more sections
  • Reaches en.wikipedia.org

What it does

Verify Claims is an agent skill from LeoYeAI/openclaw-master-skills. Verify claims and information using professional fact-checking services. Use this skill when users want to verify facts, check claims in articles/videos/transcripts, validate news authenticity, cross-reference information with trusted fact-checkers, or investigate potentially false or misleading content. Triggers include requests to "fact check", "verify this", "is this true", "check if this is accurate", or when users share content they want validated against misinformation.

Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).

It sits in Research & Science, covering Fact-checking and source verification. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Users want to verify facts
  • Check claims in articles/videos/transcripts
  • Validate news authenticity
  • Cross-reference information with trusted fact-checkers

Example prompts

  • “fact check”
  • “verify this”
  • “is this true”
  • “/verify-claims”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Understand the Content
  2. Select Fact-Checking Services
  3. Search Each Fact-Checking Service
  4. Analyze Search Results
  5. Synthesize and Present Results

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • en.wikipedia.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verify Claims loads about 4.9k tokens when it runs. Until then it costs about 124 tokens; SKILL.md has 2,139 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~124
When it runs · the whole SKILL.md, loaded when a task matches
~4.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 2,139 words, ~4,935 tokens.

Download SKILL.mdSave it as .claude/skills/verify-claims/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
verify-claims
description
Verify claims and information using professional fact-checking services. Use this skill when users want to verify facts, check claims in articles/videos/transcripts, validate news authenticity, cross-reference information with trusted fact-checkers, or investigate potentially false or misleading content. Triggers include requests to "fact check", "verify this", "is this true", "check if this is accurate", or when users share content they want validated against misinformation.

Fact-Checking Skill

Verify claims and information using professional fact-checking services from around the world.

Core Principles

  1. Multiple sources - Cross-reference findings from several fact-checking organizations
  2. Regional relevance - Prioritize fact-checkers appropriate to the content's context
  3. Language matching - Use fact-checkers in the native language of the content when possible
  4. Credible sources only - Never use fraudulent or unreliable fact-checking services
  5. Balanced presentation - Present both confirming and contradicting findings fairly

When to Use This Skill

Trigger this skill when the user:

  • Explicitly asks to fact-check, verify, or validate information
  • Shares an article, video transcript, or claim and asks "is this true?"
  • Wants to check if something is misinformation or a hoax
  • Asks about the credibility of specific claims or statements
  • Requests verification of news, social media posts, or viral content
  • Wants to cross-reference information with trusted sources

Do NOT trigger for:

  • General research or information gathering (use web search instead)
  • Checking grammar, spelling, or writing quality
  • Verifying code functionality or technical documentation
  • Questions about opinions rather than factual claims

Workflow

Step 1: Understand the Content

Before beginning verification, analyze what needs to be checked:

  1. Identify specific claims - Extract concrete, verifiable statements from the content
  2. Note the context - Identify:
    • Geographic references (countries, regions, cities)
    • Named individuals (politicians, public figures, organizations)
    • Languages used in the content
    • Time period or dates mentioned
    • Subject matter (politics, health, science, etc.)
  3. Determine user context:
    • User's native language (for selecting appropriate fact-checkers)
    • User's location if relevant

Example Analysis:

  • Content: "Video claiming vaccines cause autism, mentions Andrew Wakefield, references UK study"
  • Claims to verify: Vaccine-autism link, Wakefield's research
  • Context: Medical/health topic, UK origin, English language
  • Key entities: Andrew Wakefield, MMR vaccine, UK medical establishment
Step 2: Select Fact-Checking Services

CRITICAL: Begin by fetching the current list of fact-checking services:

Fetch: https://en.wikipedia.org/wiki/List_of_fact-checking_websites

From this list, select 3-7 relevant fact-checking services based on:

Selection Criteria
  1. User's language/location - Always include fact-checkers in the user's native language

  2. Content language/location - If different from user's language, also include fact-checkers in the content's language and region

  3. Geographic relevance - If content mentions specific countries/regions:

    • Include fact-checkers from those countries
    • Example: Content about French politics → include French fact-checkers
  4. Subject matter specialists - Some fact-checkers specialize:

    • Health/medical claims → Health Feedback, Science Feedback
    • Politics → country-specific political fact-checkers
    • General → Snopes, FactCheck.org, Full Fact
  5. Person-specific - If content focuses on specific public figures:

    • Include fact-checkers from their home countries
    • Example: Claims about a US politician → include US fact-checkers
Exclusion Rule

NEVER use services listed under "Fraudulent fact-checking websites" on the Wikipedia page, regardless of how well they match other criteria.

Prioritization

When you must limit selections:

  • Prioritize: User's language > Content's language > Geographic relevance
  • Prefer well-established services (FactCheck.org, Snopes, Full Fact, AFP Fact Check, etc.)
  • Include at least one international/general service

Example Selection:

  • User: Polish speaker
  • Content: English article about US vaccines
  • Selected services:
    1. Demagog.pl (Polish, for user)
    2. FactCheck.org (US, for content geography)
    3. Snopes (US, general/medical)
    4. Health Feedback (health specialist)
    5. Full Fact (UK, English-speaking, general)
Step 3: Search Each Fact-Checking Service

For each selected service, conduct targeted searches:

Search Strategy
  1. Extract 2-4 search terms from the content:

    • Key person names
    • Main topics/subjects
    • Specific claims or events
    • Important keywords
  2. Translate terms to the fact-checker's native language if needed

  3. Construct search queries using DuckDuckGo with site operator:

    Format: site:domain.com [search terms in appropriate language]
    
    Examples:
    - site:fullfact.org vaccines autism
    - site:demagog.org.pl szczepionki autyzm
    - site:factcheck.org Andrew Wakefield MMR
    - site:healthfeedback.org vaccine safety
  4. Execute 1-3 searches per fact-checker (depending on content complexity)

Search Best Practices
  • Keep queries concise (2-4 words typically)
  • Start broad, then narrow if needed
  • Don't repeat very similar queries
  • If first search yields good results, proceed to analysis
  • If first search yields poor results, try alternative terms
Step 4: Analyze Search Results

For each fact-checking service:

  1. Review search results - Examine the first 5-10 results from each search

  2. Select relevant articles - Choose articles where:

    • Headline directly addresses the claim being verified
    • Content appears substantial (not just brief mentions)
    • Publication date is relevant (recent for ongoing issues, any date for historical debunks)
  3. Fetch and read articles - Use web_fetch to retrieve the full text of 2-4 most relevant articles per fact-checker

  4. Extract key findings for each article:

    • Verdict - What did the fact-checker conclude? (True, False, Misleading, Mixed, Unproven, etc.)
    • Evidence - What evidence did they cite?
    • Context - Any important nuance or context
    • Relevance - How directly does this address the user's claim?
Step 5: Synthesize and Present Results

Organize findings into a clear, user-friendly format:

Handle Fresh Content First

Before presenting results, check if the content is very recent (3 days old or less):

  1. If fact-checks found: Proceed normally with presentation

  2. If no fact-checks found AND content is ≤3 days old:

    • Note that the content is too fresh for fact-checkers to have covered it yet
    • If task scheduling is available:
      • Schedule a follow-up fact-check for 3 days from now
      • Inform user: "I've scheduled a follow-up check for [date]. I'll notify you if fact-checkers have published verification by then."
    • If task scheduling is NOT available:
      • Suggest: "This content is very recent (published [date]). Fact-checkers typically need a few days to verify claims. I recommend checking back in 3 days for updated verification."
    • Offer preliminary analysis using general web search
    • Proceed with any available information from general sources
  3. If no fact-checks found AND content is older:

    • Note that fact-checkers haven't specifically covered this
    • Offer general web research instead
Structure Your Response
  1. Opening summary (2-3 sentences)

    • Overall consensus from fact-checkers
    • Brief answer to the user's question
  2. Key findings by claim (if multiple claims)

    • Group related findings together
    • Present contradicting evidence if it exists
  3. Detailed evidence (organized by fact-checker or by claim)

    • Include specific verdicts
    • Cite evidence fact-checkers used
    • Note any disagreements between fact-checkers
  4. Important context (if relevant)

    • Historical background
    • Why the claim persists
    • Common misconceptions
  5. Source citations

    • Provide direct links to all fact-checking articles referenced
    • Format: [Fact-Checker Name]: Article Title (Date if available) - [URL]
Presentation Guidelines
  • Be objective - Present findings without inserting personal judgment
  • Be nuanced - Avoid oversimplifying complex issues
  • Be clear about uncertainty - If fact-checkers disagree or evidence is inconclusive, say so
  • Be balanced - If some evidence supports and some contradicts, present both
  • Use accessible language - Avoid jargon, explain technical terms
  • Highlight consensus - When multiple fact-checkers agree, emphasize this
Formatting
  • Use clear headers to organize different claims or themes
  • Use natural prose, not bullet points, for the main findings
  • Only use lists for: multiple similar items, source citations, or when explicitly helpful
  • Include clickable citations throughout (not just at the end)
Example Response Structure
Based on verification from five established fact-checking organizations, the claim that vaccines cause autism has been thoroughly debunked. Multiple independent reviews of the evidence have found no causal link between vaccination and autism spectrum disorder.

The origins of this claim trace back to a fraudulent 1998 study by Andrew Wakefield, which was later retracted by The Lancet. Fact-checkers consistently note that Wakefield lost his medical license, and subsequent large-scale studies involving millions of children have found no connection.

[Full Fact reviewed the evidence in 2023](link), concluding "There is no link between the MMR vaccine and autism." Their analysis examined 12 major studies and found consistent results across different populations and methodologies.

[FactCheck.org's comprehensive analysis](link) explains that "The myth persists despite overwhelming scientific consensus against it" and details how the original study was not only retracted but shown to involve falsified data.

However, [Demagog.pl](link) notes that while the vaccine-autism link is false, concerns about vaccine safety in general are legitimate and should be addressed through proper scientific channels rather than dismissed.

**Important context**: The persistence of this myth has real public health consequences, as fact-checkers note declining vaccination rates in some communities. Understanding why the claim was debunked helps address ongoing concerns.

**Sources consulted:**
- Full Fact: "MMR vaccine does not cause autism" - [link]
- FactCheck.org: "Wakefield's Fraudulent Research" - [link]  
- Snopes: "Vaccines and Autism" - [link]
- Demagog.pl: "Szczepionki i autyzm - mit czy prawda?" - [link]
- Health Feedback: "Scientific consensus on vaccine safety" - [link]

Common Scenarios

Scenario 1: Single Specific Claim

User request: "Is it true that 5G causes COVID-19?"

Approach:

  • Identify claim: 5G technology causes or spreads COVID-19
  • Select 4-5 general fact-checkers (international scope, tech/health focus)
  • Search for "5G COVID" or "5G coronavirus"
  • Expected result: Multiple fact-checkers will have debunked this
  • Present: Clear consensus with explanation of why the claim is false
Scenario 2: Article with Multiple Claims

User request: "Can you fact-check this article about climate change?"

Approach:

  • Extract 3-5 specific verifiable claims from the article
  • Select fact-checkers: user's language + climate-focused services
  • Search each claim separately
  • Present: Findings organized by claim, with overall assessment
Scenario 3: Complex Political Claim

User request: "Did [politician] really say/do [thing]?"

Approach:

  • Identify the specific claim and context
  • Select fact-checkers from politician's country + user's language
  • Search politician's name + key terms
  • Present: Direct answer with context, including if statement was taken out of context
Scenario 4: Viral Social Media Content

User request: "I saw this video on TikTok claiming [X], is it real?"

Approach:

  • Identify what's being claimed in the video
  • Select broad, well-known fact-checkers (viral content often fact-checked widely)
  • Search for key terms from the claim
  • Present: Whether it's been debunked, original context if misrepresented
Show full SKILL.md (876 more words)Show less
Scenario 5: Historical Claim

User request: "Did [historical event] really happen this way?"

Approach:

  • Note that this is historical verification, may need broader research
  • Select fact-checkers + consider using general web search for historical records
  • Present: What fact-checkers say if available, acknowledge if claim is outside typical fact-checking scope
Scenario 6: Very Fresh Content (Breaking News)

User request: "I just saw this article published today claiming [X]. Is it true?"

Approach:

  • Check publication date: is it 3 days old or less?
  • Search fact-checkers anyway (sometimes they work very quickly on major stories)
  • If no fact-checks found:
    • With task scheduling: Schedule follow-up check for 3 days later, notify user of the scheduled check
    • Without task scheduling: Inform user that content is too fresh, suggest returning in 3 days
  • Offer preliminary analysis using general web search
  • Present: "This is very recent content. Fact-checkers haven't had time to verify yet. Here's what I found from general sources, but I recommend waiting for professional fact-checking."

Example response:

This article was published just [X hours/days] ago, which is too recent for professional 
fact-checkers to have verified the claims yet. They typically need a few days to conduct 
thorough research.

I've scheduled a follow-up fact-check for [date in 3 days]. I'll notify you automatically 
if fact-checkers publish verification by then.

In the meantime, here's what I found through general web research:
[preliminary findings with appropriate caveats]

Note: These are preliminary findings only. Professional fact-checkers may provide more 
thorough verification in the coming days.

Edge Cases and Limitations

When Fact-Checkers Haven't Covered the Topic

If searches return no relevant results:

  1. Try broader search terms
  2. Try related claims that fact-checkers may have covered
  3. If still no results, check if the content is recent (3 days or less)
  4. For fresh content (≤3 days old):
    • Acknowledge: "This is very recent content. Professional fact-checkers typically need a few days to verify claims."
    • If scheduling tools are available: Schedule a follow-up fact-check for 3 days later
    • If scheduling is not available: Suggest the user returns in 3 days for updated verification
    • Offer to do preliminary general web research in the meantime
  5. For older content: Acknowledge "Professional fact-checkers haven't specifically addressed this claim"
  6. Offer to do general web research instead
  7. Consider if the claim is too obscure or too local for major fact-checkers
Contradicting Fact-Checkers

If fact-checkers disagree:

  1. Present all perspectives fairly
  2. Note the disagreement explicitly
  3. Consider if they're addressing slightly different aspects
  4. Look for consensus on specific sub-points
  5. Don't force a conclusion if the evidence is genuinely mixed
Outdated Information

If fact-checks are old but the claim is current:

  1. Note the publication dates
  2. Search for more recent fact-checks
  3. Consider if circumstances have changed
  4. Acknowledge if using older sources due to lack of recent coverage
Language Barriers

If key fact-checkers are in languages you don't fully understand:

  1. Use web_fetch to retrieve the content
  2. Focus on verdicts, ratings, and conclusion sections which are often clear
  3. Use any English summaries or abstracts
  4. Acknowledge limitations if language creates uncertainty
Bias Concerns

Users may question fact-checker reliability:

  1. Stick to well-established, internationally recognized services
  2. Present findings from multiple fact-checkers to show consensus
  3. Note if you're using fact-checkers from multiple countries/perspectives
  4. Acknowledge that no source is perfect, but these are professional verification services

Quality Checklist

Before presenting results, verify:

  • Checked at least 3 different fact-checking services
  • Included fact-checkers relevant to the user's language/location
  • Included fact-checkers relevant to the content's context
  • Excluded any fraudulent fact-checking services
  • Read full articles, not just headlines or snippets
  • Provided direct links to all sources cited
  • Presented findings objectively without adding personal judgment
  • Acknowledged any uncertainty or disagreement between sources
  • Organized response clearly with specific findings, not vague summaries
  • Used natural prose for main findings, lists only where truly helpful
  • If content is ≤3 days old with no fact-checks: Noted this and scheduled follow-up OR suggested user return in 3 days
  • If providing preliminary analysis: Clearly distinguished it from professional fact-checking

Examples of Good Fact-Checking Services

International/English:

  • FactCheck.org (US, general)
  • Snopes (US, general)
  • Full Fact (UK, general)
  • AFP Fact Check (International, multilingual)
  • PolitiFact (US, politics)

Regional/Language-Specific:

  • Demagog.pl (Poland, Polish)
  • Les Décodeurs (France, French)
  • Correctiv (Germany, German)
  • Maldita.es (Spain, Spanish)
  • Aos Fatos (Brazil, Portuguese)
  • Alt News (India, English/Hindi)
  • Africa Check (Africa, multilingual)

Specialized:

  • Health Feedback (health/medical claims)
  • Climate Feedback (climate science claims)
  • Science Feedback (general science claims)

Note: This is not exhaustive. Always fetch the current list from Wikipedia to see all available services.


Final Notes

Task Scheduling for Fresh Content

When content is very recent (≤3 days old) and hasn't been fact-checked yet:

If task scheduling tools are available:

  • Automatically schedule a follow-up fact-check for 3 days later
  • Store the original query, claims, and context
  • When the scheduled task runs:
    • Re-search the same fact-checking services
    • Compare new findings to preliminary analysis
    • Notify user only if new fact-checks were found
    • Provide updated verification with links

If task scheduling is NOT available:

  • Inform the user that the content is too fresh
  • Suggest they return in 3 days for updated verification
  • Provide preliminary analysis from general sources with appropriate caveats
  • Make it clear that preliminary findings are not from professional fact-checkers
Core Approach

This skill focuses on using professional fact-checking organizations rather than doing original research. These organizations employ journalists and researchers who specialize in verification. Your role is to:

  1. Find what they've already published
  2. Synthesize their findings
  3. Present them clearly to the user
  4. Schedule follow-ups for very recent content when possible

If a topic hasn't been covered by fact-checkers, acknowledge this and offer to do general research instead. Don't try to replace professional fact-checking with web searches alone, but do provide preliminary information when users need it for fresh content.

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/verify-claims of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Verify Claims next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verify Claims compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify Claims this skillLeoYeAI/openclaw-master-skills2.2k—~4.9kAutomated safety check: PassMIT
Perplexity Web Searchdavila7/claude-code-templates33k11 repos~3.5kAutomated safety check: NotesMIT
Citation Verification GuideGalaxy-Dawn/claude-scholar5.7k2 repos~1.9kAutomated safety check: PassMIT
Article Fact Checkerdigoal/blog8.6k—~939Automated safety check: PassGPL-2.0
Deep Research Agent TeamImbad0202/academic-research-skills51k—~13kAutomated safety check: PassCustom licence
Docs Grounding Verifiermicrosoft/apm4k—~1.9kAutomated safety check: PassMIT

Similar skills

  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    33k GitHub starsUsed in 11 repos~3.5k tokens
    Research & ScienceAuto-check: notes
  • Citation Verification Guide

    Galaxy-Dawn/claude-scholar

    Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.

    5.7k GitHub starsUsed in 2 repos~1.9k tokens
    Research & ScienceAuto-check passed
  • 三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…

    8.6k GitHub stars~939 tokensUpdated yesterday
    Research & ScienceAuto-check passed
  • Deep Research Agent Team

    Imbad0202/academic-research-skills

    Runs a 13-agent pipeline for rigorous academic research, from forming the question through systematic search, synthesis, bias checks and an APA 7.0 report.

    51k GitHub stars~13k tokensUpdated yesterday
    Research & ScienceAuto-check passed
  • Official

    A skill your agent uses to verify CLAIM-LEVEL grounding of a documentation page (or set of pages) against the source code.

    4k GitHub stars~1.9k tokensUpdated today
    Research & ScienceAuto-check passed
  • Fact Checking

    bradygaster/squad

    Review and validate claims using counter-hypothesis testing.

    3.3k GitHub stars~503 tokensUpdated today
    Research & ScienceAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Verify Claims

What does Verify Claims do?

Verify claims and information using professional fact-checking services. Verify Claims is an agent skill from LeoYeAI/openclaw-master-skills. Verify claims and information using professional fact-checking services.

When should I use Verify Claims?

Verify Claims fits situations like: users want to verify facts; check claims in articles/videos/transcripts; validate news authenticity; cross-reference information with trusted fact-checkers.

How do I install Verify Claims in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill verify-claims -a claude-code`. Or copy the skill folder (skills/verify-claims in LeoYeAI/openclaw-master-skills) into .claude/skills/verify-claims in your project. Claude Code loads it when a task matches its description.

How do I install Verify Claims in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill verify-claims -a codex`. Or copy the skill folder (skills/verify-claims in LeoYeAI/openclaw-master-skills) into .agents/skills/verify-claims in your project. Codex loads it when a task matches its description.

Can I use Verify Claims in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill verify-claims -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-claims, .gemini/skills/verify-claims, .github/skills/verify-claims and .opencode/skills/verify-claims in your project.

What does Verify Claims need to run?

SKILL.md names no scripts, command-line tools or credentials: Verify Claims is instructions for the agent only.

Does Verify Claims access the network?

SKILL.md names 1 domain. In commands or code: en.wikipedia.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Verify Claims safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Verify Claims use?

Verify Claims is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify Claims use?

About 4.9k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verify Claims?

Skills that share tags, products or a category with Verify Claims: Perplexity Web Search (davila7/claude-code-templates, 33k stars), Citation Verification Guide (Galaxy-Dawn/claude-scholar, 5.7k stars), Article Fact Checker (digoal/blog, 8.6k stars) and Deep Research Agent Team (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify Claims?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.