本文へ移動
cccskills
無料GitHub で公開

fact-checker

Verifies factual claims in documents using web search and official sources, then proposes corrections with user confirmation. Use when the user asks to fact-check, verify information, validate claims, check accuracy, or update outdated information in documents. Supports AI model specs, technical documentation, statistics, and general factual statements.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md8.4 KB
  • README.md5.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Fact Checker

Verify factual claims in documents and propose corrections backed by authoritative sources.

When to use

Trigger when users request:

  • "Fact-check this document"
  • "Verify these AI model specifications"
  • "Check if this information is still accurate"
  • "Update outdated data in this file"
  • "Validate the claims in this section"

Workflow

Copy this checklist to track progress:

Fact-checking Progress:
- [ ] Step 1: Identify factual claims
- [ ] Step 2: Search authoritative sources
- [ ] Step 3: Compare claims against sources
- [ ] Step 4: Generate correction report
- [ ] Step 5: Apply corrections with user approval

Step 1: Identify factual claims

Scan the document for verifiable statements:

Target claim types:

  • Technical specifications (context windows, pricing, features)
  • Version numbers and release dates
  • Statistical data and metrics
  • API capabilities and limitations
  • Benchmark scores and performance data

Skip subjective content:

  • Opinions and recommendations
  • Explanatory prose
  • Tutorial instructions
  • Architectural discussions

Step 2: Search authoritative sources

For each claim, search official sources:

AI models:

  • Official announcement pages (anthropic.com/news, openai.com/index, blog.google)
  • API documentation (platform.claude.com/docs, platform.openai.com/docs)
  • Developer guides and release notes

Technical libraries:

  • Official documentation sites
  • GitHub repositories (releases, README)
  • Package registries (npm, PyPI, crates.io)

General claims:

  • Academic papers and research
  • Government statistics
  • Industry standards bodies

Search strategy:

  • Use model names + specification (e.g., "Claude Opus 4.5 context window")
  • Include current year for recent information
  • Verify from multiple sources when possible

Step 3: Compare claims against sources

Create a comparison table:

Claim in DocumentSource InformationStatusAuthoritative Source
Claude 3.5 Sonnet: 200K tokensClaude Sonnet 4.5: 200K tokens❌ Outdated model nameplatform.claude.com/docs
GPT-4o: 128K tokensGPT-5.2: 400K tokens❌ Incorrect version & specopenai.com/index/gpt-5-2

Status codes:

  • ✅ Accurate - claim matches sources
  • ❌ Incorrect - claim contradicts sources
  • ⚠️ Outdated - claim was true but superseded
  • ❓ Unverifiable - no authoritative source found

Step 4: Generate correction report

Present findings in structured format:

## Fact-Check Report

### Summary
- Total claims checked: X
- Accurate: Y
- Issues found: Z

### Issues Requiring Correction

#### Issue 1: Outdated AI Model Reference
**Location:** Line 77-80 in docs/file.md
**Current claim:** "Claude 3.5 Sonnet: 200K tokens"
**Correction:** "Claude Sonnet 4.5: 200K tokens"
**Source:** https://platform.claude.com/docs/en/build-with-claude/context-windows
**Rationale:** Claude 3.5 Sonnet has been superseded by Claude Sonnet 4.5 (released Sept 2025)

#### Issue 2: Incorrect Context Window
**Location:** Line 79 in docs/file.md
**Current claim:** "GPT-4o: 128K tokens"
**Correction:** "GPT-5.2: 400K tokens"
**Source:** https://openai.com/index/introducing-gpt-5-2/
**Rationale:** 128K was output limit; context window is 400K. Model also updated to GPT-5.2

Step 5: Apply corrections with user approval

Before making changes:

  1. Show the correction report to the user
  2. Wait for explicit approval: "Should I apply these corrections?"
  3. Only proceed after confirmation

When applying corrections:

# Use Edit tool to update document
# Example:
Edit(
    file_path="docs/03-写作规范/AI辅助写书方法论.md",
    old_string="- Claude 3.5 Sonnet: 200K tokens(约 15 万汉字)",
    new_string="- Claude Sonnet 4.5: 200K tokens(约 15 万汉字)"
)

After corrections:

  1. Verify all edits were applied successfully
  2. Note the correction summary (e.g., "Updated 4 claims in section 2.1")
  3. Remind user to commit changes

Search best practices

Query construction

Good queries (specific, current):

  • "Claude Opus 4.5 context window 2026"
  • "GPT-5.2 official release announcement"
  • "Gemini 3 Pro token limit specifications"

Poor queries (vague, generic):

  • "Claude context"
  • "AI models"
  • "Latest version"

Source evaluation

Prefer official sources:

  1. Product official pages (highest authority)
  2. API documentation
  3. Official blog announcements
  4. GitHub releases (for open source)

Use with caution:

  • Third-party aggregators (llm-stats.com, etc.) - verify against official sources
  • Blog posts and articles - cross-reference claims
  • Social media - only for announcements, verify elsewhere

Avoid:

  • Outdated documentation
  • Unofficial wikis without citations
  • Speculation and rumors

Handling ambiguity

When sources conflict:

  1. Prioritize most recent official documentation
  2. Note the discrepancy in the report
  3. Present both sources to the user
  4. Recommend contacting vendor if critical

When no source found:

  1. Mark as ❓ Unverifiable
  2. Suggest alternative phrasing: "According to [Source] as of [Date]..."
  3. Recommend adding qualification: "approximately", "reported as"

Special considerations

Time-sensitive information

Always include temporal context:

Good corrections:

  • "截至 2026 年 1 月" (As of January 2026)
  • "Claude Sonnet 4.5 (released September 2025)"

Poor corrections:

  • "Latest version" (becomes outdated)
  • "Current model" (ambiguous timeframe)

Numerical precision

Match precision to source:

Source says: "approximately 1 million tokens" Write: "1M tokens (approximately)"

Source says: "200,000 token context window" Write: "200K tokens" (exact)

Citation format

Include citations in corrections:

> **注**:具体上下文窗口以模型官方文档为准,本书写作时使用 Claude Sonnet 4.5 为主要工具。

Link to sources when possible.

Examples

Example 1: Technical specification update

User request: "Fact-check the AI model context windows in section 2.1"

Process:

  1. Identify claims: Claude 3.5 Sonnet (200K), GPT-4o (128K), Gemini 1.5 Pro (2M)
  2. Search official docs for current models
  3. Find: Claude Sonnet 4.5, GPT-5.2, Gemini 3 Pro
  4. Generate report showing discrepancies
  5. Apply corrections after approval

Example 2: Statistical data verification

User request: "Verify the benchmark scores in chapter 5"

Process:

  1. Extract numerical claims
  2. Search for official benchmark publications
  3. Compare reported vs. source values
  4. Flag any discrepancies with source links
  5. Update with verified figures

Example 3: Version number validation

User request: "Check if these library versions are still current"

Process:

  1. List all version numbers mentioned
  2. Check package registries (npm, PyPI, etc.)
  3. Identify outdated versions
  4. Suggest updates with changelog references
  5. Update after user confirms

Quality checklist

Before completing fact-check:

  • All factual claims identified and categorized
  • Each claim verified against official sources
  • Sources are authoritative and current
  • Correction report is clear and actionable
  • Temporal context included where relevant
  • User approval obtained before changes
  • All edits verified successful
  • Summary provided to user

Limitations

This skill cannot:

  • Verify subjective opinions or judgments
  • Access paywalled or restricted sources
  • Determine "truth" in disputed claims
  • Predict future specifications or features

For such cases:

  • Note the limitation in the report
  • Suggest qualification language
  • Recommend user research or expert consultation

Next Step: Export Verified Content

After fact-checking, suggest exporting the verified document:

Fact-check complete: [N] claims verified, [M] corrections proposed.

Options:
A) Export as PDF — run /daymade-docs:pdf-creator (Recommended for formal documents)
B) Create slides — run /daymade-docs:ppt-creator from verified content
C) No thanks — I'll use the corrected document directly

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Fixes web search on an agent whose model backend can't run it: a relay/reseller proxying Claude or Codex returns empty instead of failing. Use when web search returns nothing, a model insists a shipped product doesn't exist, someone wants to give an agent internet access, or the user is on a third-party base URL, relay, or 中转站. Diagnoses which built-in tools are dead, removes them, and installs a working replacement.

日本語の概要は準備中です。原文の説明を表示しています。

daymade/claude-code-skills1,4522026年10月11日 更新

抓取 A 股消息面情报:从财联社、华尔街见闻、金十、新浪 7x24、东财快讯、 证监会/央行/上交所/财政部政策公告、东方财富股吧等公开来源抓取与股票相关的 新闻、政策、情绪,输出结构化 JSON 或 Markdown。 当用户提到“A 股消息面”、“抓新闻”、“个股消息”、“政策监管”、“股吧情绪”、 “财联社”、“东财快讯”、“市场情绪”或需要把某只股票相关的公开情报聚合出来时 触发。也适用于“帮我看看 000001 最近有什么消息”这类口语化请求。

日本語の概要は準備中です。原文の説明を表示しています。

daymade/claude-code-skills1,4522026年10月11日 更新

Transcribes audio or video to speaker-labeled, timestamped text, locally with MLX on Apple Silicon or remotely. Use for 转录 / 录音转文字 / 说话人分离 / 字幕, and also for preparing audio for ASR without transcribing: 转格式, 降采样到 16kHz, merging recorder segments, or compressing and speeding up audio before 飞书妙记 — even when it looks like a one-line ffmpeg job.

日本語の概要は準備中です。原文の説明を表示しています。

daymade/claude-code-skills1,4522026年10月11日 更新

Routes audio: StepFun ASR/语音识别, StepFun TTS/配音, transcript/妙记→会议纪要, merge/review minutes. Reads one bundled specialist; generic ASR and correction stay direct.

日本語の概要は準備中です。原文の説明を表示しています。

daymade/claude-code-skills1,4522026年10月11日 更新

Diagnoses and repairs repository setup and guarded Git workflows for Claude Code or Codex — environment repair, startup sync, hook auditing, collaborator handoff. Use when a repo won't run, a teammate onboards, hook output duplicates, or commit/push/conflict needs guarding. Not for lost-commit recovery (use git-safety-net), GitHub ops (use github-ops), or history scrubbing (use github-sensitive-data-cleanup).

日本語の概要は準備中です。原文の説明を表示しています。

daymade/claude-code-skills1,4522026年10月11日 更新

Runs adversarial due-diligence on a benchmark the user envies — a founder, KOL, company, or product whose success looks inflated — splitting marketing bubble from real signal, then mapping the validated playbook onto the user's own resources. Use for 尽调/对标/拆解 a competitor, 抄/偷师 their playbook, or suspecting 水分/泡沫 in claims. Prefer over deep-research when debunking inflated claims, not a neutral briefing.

日本語の概要は準備中です。原文の説明を表示しています。

daymade/claude-code-skills1,4522026年10月11日 更新

daymade のスキルをすべて見る

このスキルの問題を報告する