Bible Fact Check

Input Sources (pick one)

1. bible-buddy reference file — e.g.,

   /review-bible-buddy fun-facts.md

   → reads from

   bible-buddy/references/

2. Any file path — e.g.,

   /review-bible-buddy /path/to/my-notes.md

   → reads the specified file
3. URL — e.g.,

   /review-bible-buddy https://example.com/article

   → Do NOT use WebFetch — many news sites block it with 403. Run

   uv run --directory {BIBLE_BUDDY} scripts/fetch_url.py "<URL>"

   to extract article text. The script auto-falls back to patchright (headless Chromium) when urllib gets 403.
4. Pasted text — user pastes content directly in the conversation → review the pasted text
5. No argument — use AskUserQuestion to ask the user whether they want to paste a URL or input text. Do NOT default to any file.

Path Resolution

{BIBLE_BUDDY}

1. Project-level:

   .claude/skills/bible-buddy/

   (relative to repo root)
2. User-level:

   ~/.claude/skills/bible-buddy/

references/

• 專案層級：

  npx skills add lancetw/skills/bible-buddy --project

• 使用者層級：

  npx skills add lancetw/skills/bible-buddy

  」

{BIBLE_BUDDY}

Prerequisites

1. Run dependency setup (one-time):
   bash

   uv sync --directory {BIBLE_BUDDY} && uv run --directory {BIBLE_BUDDY} patchright install chromium

How to Run

1. Determine the input source
2. Resolve

   {BIBLE_BUDDY}

   path (see Path Resolution above)
3. Read / receive the content
   • For

     fun-facts.md

     : Do NOT use Read (exceeds 10K token limit). Use Grep:

     Grep("^- ", path="{BIBLE_BUDDY}/references/fun-facts.md", output_mode="content", head_limit=0)

     → returns all ~134 facts with line numbers in one call
4. Load reference files as checking criteria (read on demand, not all at once):

   • {BIBLE_BUDDY}/references/anachronism-timeline.md

     → Read entire file (small, 43 lines) → for checks 3, 4

   • {BIBLE_BUDDY}/references/commonly-misread-passages.md

     → Do NOT Read entire file (44KB wide table). Two-step lookup:
     1. Load index:

        bash: grep '|' {BIBLE_BUDDY}/references/commonly-misread-passages.md | awk -F'|' '{print $2}' | sed 's/^ *//;s/ *$//' | grep -v '^-' | grep -v '^Scripture'

        → gives all 79 scripture references (~2KB)
     2. For each relevant passage, Grep the full row:

        Grep("Isaiah 7:14", path="{BIBLE_BUDDY}/references/commonly-misread-passages.md")

        → for checks 2, 4, 7, 8

   • {BIBLE_BUDDY}/references/yeshua-hermeneutics.md

     → Read entire file (small, 122 lines) → for check 8
5. Run checks sequentially:
   • URL or pasted text: run checks 1-5 only
   • fun-facts reference file: run all 10 checks
6. For each check, report findings with line numbers, or "✅ 通過" if clean
7. End with a summary table

The 10 Checks

1. 事實錯誤檢查 (Factual Errors)

• Historical dates (cross-reference

  anachronism-timeline.md

  for known dates, AND verify precision — if timeline says "1820s-1830s" but content says only "1820 年代", flag the imprecision)
• Person attributions (who did what in which Bible chapter)
• Word meanings: if a Hebrew/Greek term appears in

  commonly-misread-passages.md

  's "Key Hebrew/Greek Term" column, verify the content uses it correctly. Also check semantic range — flag claims that reduce a word to a single meaning when it has a broader range (e.g., pistis ≠ only "faithfulness")
• Scholarly claims (hapax legomenon, manuscript evidence, etc.)
• If the content's interpretation of a passage contradicts the "Actual First-Century Jewish Context" column in

  commonly-misread-passages.md

  , flag it
• Causal claims: verify the direction is correct (e.g., if a Chinese translation was published in 1919, it cannot have "caused" an 1844 doctrine)
• Theological teachings without any scripture citation: if the content makes a theological claim (about God, the Spirit, salvation, church practice) without citing scripture, flag as "ungrounded teaching" (無經文根據的教導)

2. 經節編號檢查 (Verse Reference Errors)

3. 年代錯置檢查 (Anachronism)

anachronism-timeline.md

anachronism-timeline.md

4. 過度簡化檢查 (Oversimplification)

• Minority academic views stated as fact
• Complex debates reduced to one-sided conclusions
• Words like "其實是" or "就是" on debated topics

commonly-misread-passages.md

yeshua-hermeneutics.md

5. 數量計算檢查 (Counting Errors)

6. 重複檢查 (Duplicates) ⟨fun-facts only⟩

7. 稻草人檢查 (Strawman Arguments) ⟨fun-facts only⟩

commonly-misread-passages.md

8. 意味不明檢查 (Unclear Meaning) ⟨fun-facts only⟩

• What misconception it corrects, OR
• What surprising insight it reveals, OR
• Why a Taiwan reader should care

commonly-misread-passages.md

9. 字數控制檢查 (Verbosity) ⟨fun-facts only⟩

10. 趣味門檻檢查 (Interest Threshold) ⟨fun-facts only⟩

• Would a Taiwan Sunday school teacher find this interesting?
• Does it require specialized knowledge to appreciate?
• Is it relevant to what Taiwan churches actually teach or encounter?

commonly-misread-passages.md

General Sweep (after completing all 10 checks)

• Pre-existing antecedents that the content ignores (e.g., "Augustine invented original sin" ignores 4 Ezra, 2 Baruch)
• Conflation of related but distinct concepts (e.g., Colwell's rule vs Harner's qualitative argument)
• Translation history gaps (e.g., claiming CUV 1919 originated a connection when Morrison 1823 already used it)
• Counter-examples the content doesn't address (e.g., Joel 1:8 for betulah)

### 補充：通則檢查

Output Format

• Claude Code →

  uv run --directory {BIBLE_BUDDY} scripts/detect_desktop.py bible-fact-check

  → save to returned path
• Cowork / Claude.ai web → Do NOT save. Tell user: "你可以複製回應內容存檔，或在 Claude.ai 中使用 Artifact 功能下載。"

YYYYMMDD_HHmm_<slug>.md

pasted_text

_

1. Detect Desktop path using the script above
2. Write the full report to

   <detected-path>/YYYYMMDD_HHmm_<slug>.md

3. Show only the summary table in the conversation, with the file path

Report structure

# 審查：[filename or URL or "使用者提供的內容"]
來源：[URL if applicable]
日期：[YYYY-MM-DD HH:mm:ss]

### N. 檢查名稱

| # | 原文摘錄 | 問題說明 |
|---|---------|---------|
| 1 | 「...」 | 簡短說明 |
| 2 | 「...」 | 簡短說明 |

### N. 檢查名稱 — ✅ 通過

## 總結

| 檢查 | 結果 |
|------|------|
| 1. 事實錯誤 | 2 項 |
| 2. 經節編號 | ✅ |
| ... | ... |

### 主要問題說明

1. **[問題類型]** — 2-3 句白話解釋，這些問題為什麼重要、讀者該注意什麼。
2. ...

Readability Rules

• 全中文為主 — 希臘文/希伯來文只在必要時附註，不要大段英文引用
• 短段落 — 每個發現 2-3 句話就好，不要寫論文
• 白話 — 用台灣教會能理解的語言，避免學術腔
• 補充背景 ≠ 批評 — 年代錯置檢查的語氣是「補充資訊」，不是指責作者
• Reference file 引用只需標示來源名稱和關鍵事實，不要貼原文

Important Notes

• Use 上主 (not 耶和華 or YHWH) when referring to the divine name in reports
• Do NOT auto-fix anything. Report only.
• Be specific: include line numbers and quote the problematic text
• When a finding is based on a reference file, cite it: 「根據 anachronism-timeline.md：altar call 起源為 1830s，非 1820s」
• When in doubt, flag it — the user will decide whether to act
• Some checks may not apply to all content types (e.g., key-terms lists won't have strawman arguments). Skip with "N/A — 此檢查不適用於本內容"
• Reference files: read ONLY the 3 files listed in Step 4 under

  {BIBLE_BUDDY}/references/

  (resolved path).