Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
逐段逐句鉴定一篇文章内容的真伪，拆解论证结构，对每个事实/推断节点做六维核查（逻辑正确性、结论可量化性、证据链完整性、证据是否捏造、证据可考证性、来源可信度），最后输出带原文定位的问题清单和置信度打分表。触发条件：用户提到"鉴别真伪"、"这篇文章可信吗"、"内容审查"、"事实核查"、"fact…
Install Article Fact Checker
$ npx skills add digoal/blog --skill article-fact-checker -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install digoal/blog article-fact-checker --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skills_for_claude_web/article-fact-checker .claude/skills/article-fact-checker && rm -rf skills-srcUse ~/.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/
Install the "article-fact-checker" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/article-fact-checker into .claude/skills/article-fact-checker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "article-fact-checker", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/article-fact-checkerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add digoal/blog --skill article-fact-checker -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install digoal/blog article-fact-checker --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skills_for_claude_web/article-fact-checker .agents/skills/article-fact-checker && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "article-fact-checker" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/article-fact-checker into .agents/skills/article-fact-checker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "article-fact-checker", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add digoal/blog --skill article-fact-checker -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install digoal/blog article-fact-checker --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skills_for_claude_web/article-fact-checker .cursor/skills/article-fact-checker && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "article-fact-checker" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/article-fact-checker into .cursor/skills/article-fact-checker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "article-fact-checker", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/digoal/blog.git --path skills/skills_for_claude_web/article-fact-checker--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add digoal/blog --skill article-fact-checker -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install digoal/blog article-fact-checker --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skills_for_claude_web/article-fact-checker .gemini/skills/article-fact-checker && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "article-fact-checker" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/article-fact-checker into .gemini/skills/article-fact-checker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "article-fact-checker", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install digoal/blog article-fact-checkerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add digoal/blog --skill article-fact-checker -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skills_for_claude_web/article-fact-checker .github/skills/article-fact-checker && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "article-fact-checker" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/article-fact-checker into .github/skills/article-fact-checker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "article-fact-checker", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add digoal/blog --skill article-fact-checker -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install digoal/blog article-fact-checker --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skills_for_claude_web/article-fact-checker .opencode/skills/article-fact-checker && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "article-fact-checker" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/article-fact-checker into .opencode/skills/article-fact-checker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "article-fact-checker", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
article-fact-checker- GitHub stars
- 8.6k
- Token cost
- ~956 tokens
- SKILL.md length
- 138 words
- Files
- 1
- Skills in repo
- 98
- Repo updated
- First seen
- Licence
- GPL-2.0
At a glance
逐段逐句鉴定一篇文章内容的真伪，拆解论证结构，对每个事实/推断节点做六维核查（逻辑正确性、结论可量化性、证据链完整性、证据是否捏造、证据可考证性、来源可信度），最后输出带原文定位的问题清单和置信度打分表。触发条件：用户提到"鉴别真伪"、"这篇文章可信吗"、"内容审查"、"事实核查"、"fact…
- Works in 2 steps: 先拆结构，不先核查：把文章还原成"结论 ← 分论点 ← 证据"的论证树，只标出 → 对每个核查节点跑六维检验，而不是笼统给一个"可信/不可信"。六维分别对应
- Tasks that involve Fact-checking and source verification
- SKILL.md covers 这个 skill 在做什么，为什么这么设计, 第一步：拿到原文, 第二步：拆解论证结构 and 第三步：对事实陈述句和因果/推断句做六维核查, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Article Fact Checker is an agent skill from digoal/blog. 逐段逐句鉴定一篇文章内容的真伪，拆解论证结构，对每个事实/推断节点做六维核查（逻辑正确性、结论可量化性、证据链完整性、证据是否捏造、证据可考证性、来源可信度），最后输出带原文定位的问题清单和置信度打分表。触发条件：用户提到"鉴别真伪"、"这篇文章可信吗"、"内容审查"、"事实核查"、"fact check"、"这段话是真的假的"、"帮我查一下这篇文章的漏洞"、"证据链完不完整"、"这个结论站得住脚吗"、"逐句检查"、"这篇报道靠谱吗"，或者给出一篇文章/一段内容并希望知道"能不能信"、"哪里有问题"、"论证严不严密"。即使用户只说"帮我看看这篇文章有没有问题"或"这篇文章说的是真的吗"，也应使用本 skill。输出为 Markdown 报告，保存到当前项目 markdown/ 目录。
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office, covering Fact-checking and source verification and Markdown. The repository describes itself as: AI,Opensource,Database,Business,Finance,Minds. git clone --depth 1 https://github.com/digoal/blog. The licence is GPL-2.0.
When your agent uses it
- Tasks that involve Fact-checking and source verification
- Tasks that involve Markdown
Example prompts
- “这篇文章可信吗”
- “fact check”
- “这段话是真的假的”
- “/article-fact-checker”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- 先拆结构，不先核查：把文章还原成"结论 ← 分论点 ← 证据"的论证树，只标出
- 对每个核查节点跑六维检验，而不是笼统给一个"可信/不可信"。六维分别对应
What it can do on your machine
Read from SKILL.md and the folder at commit ad6fcb7. 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 (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Article Fact Checker loads about 956 tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 138 words of instructions outside code blocks.
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 digoal/blog at commit ad6fcb7, republished under its GPL-2.0 licence (© digoal). 138 words, ~956 tokens.
Download SKILL.mdSave it as
.claude/skills/article-fact-checker/SKILL.md (or your agent's skills folder).- name
- article-fact-checker
- description
- 逐段逐句鉴定一篇文章内容的真伪，拆解论证结构，对每个事实/推断节点做六维核查（逻辑正确性、结论可量化性、证据链完整性、证据是否捏造、证据可考证性、来源可信度），最后输出带原文定位的问题清单和置信度打分表。触发条件：用户提到"鉴别真伪"、"这篇文章可信吗"、"内容审查"、"事实核查"、"fact check"、"这段话是真的假的"、"帮我查一下这篇文章的漏洞"、"证据链完不完整"、"这个结论站得住脚吗"、"逐句检查"、"这篇报道靠谱吗"，或者给出一篇文章/一段内容并希望知道"能不能信"、"哪里有问题"、"论证严不严密"。即使用户只说"帮我看看这篇文章有没有问题"或"这篇文章说的是真的吗"，也应使用本 skill。输出为 Markdown 报告，保存到当前项目 markdown/ 目录。
文章真伪鉴定
这个 skill 在做什么，为什么这么设计
逐字逐句核查是最耗时也最容易做偏的方式——如果不先搭结构，很容易把力气花在 "这句话写得挺有文采"这种无信息量的修辞句上，反而漏掉真正承载事实主张的关键句。 所以这个 skill 分两步走：
- 先拆结构，不先核查：把文章还原成"结论 ← 分论点 ← 证据"的论证树，只标出 承载事实陈述或因果/推断主张的句子作为核查对象，纯描述、过渡、情绪煽动句只 标记类型，不逐条查真伪。这样能把工作量集中在真正需要核查的 20%~30% 的句子上。
- 对每个核查节点跑六维检验，而不是笼统给一个"可信/不可信"。六维分别对应 六种不同的造假/失实模式——逻辑断裂、结论空心化、证据链缺环、数据捏造、 孤证无法溯源、来源本身不可靠——混在一起打一个总分，用户没法知道问题到底出 在哪一环，也没法针对性地去核实。
打分用取短板而不是取平均：六维里任何一维出现严重问题（比如证据被证实是 捏造的），这个论证节点的综合置信度就应该被拉到很低，不能被其他维度的高分拉平—— 一篇文章"看起来逻辑严密、来源权威，但关键数据是编的"，本质上比"逻辑略松散但 证据都真实"更危险，取平均会掩盖这一点。
第一步：拿到原文
- 用户直接粘贴文本：直接用。
- 用户给的是文件路径：纯文本/Markdown 直接读；docx/pdf/pptx 先用对应技能 （docx / pdf-reading / pptx）提取正文再继续，不要对着带格式标记的原始内容分析。
- 用户给的是 URL：用 web_fetch 抓取正文。
第二步：拆解论证结构
通读全文一遍，产出一张论证树，明确以下三类元素：
- 主结论：文章最终想让读者相信/接受的核心主张。
- 分论点：支撑主结论的中间层论点。
- 句子分类：把文章里每一句/每一段拆成下面几类，并标注原文定位（第几段/
引用原句片段）：
- 事实陈述句（可核查对象）：有具体的人、事、时间、数字、机构。
- 因果/推断句（可核查对象）：从A推出B，包含"导致""因为""说明""证明" 这类连接词。
- 定性/评价句：不含可验证事实，但构成文章的核心论点（比如"这项技术具有 革命性意义"）——这类要单独处理，见第四步。
- 修辞/过渡/情绪句：无实质信息量，不需要核查真伪，但如果煽动性明显， 在报告里提一句即可，不用展开。
只对前三类（事实陈述句、因果/推断句、定性/评价句）逐一进入第三、四步的核查。
第三步：对事实陈述句和因果/推断句做六维核查
对每一个核查节点，逐维打分（0-100）并写出依据：
| 维度 | 检查什么 | 常见问题信号 |
|---|---|---|
| ① 逻辑正确性 | 形式层：有没有滑坡、稻草人、诉诸权威、幸存者偏差、相关当因果、以偏概全；结构层：论据支撑的到底是这句结论，还是一个"看起来差不多但范围不同"的结论 | 用"样本涨了30%"支撑"行业普遍上涨"这类偷换范围的手法最隐蔽，要重点看 |
| ② 证据链完整性 | 先判断论证类型（演绎/归纳/类比/因果），再对照该类型该有的环节找缺口：因果论证缺"排除混淆变量、时间先后顺序、反例检验"；归纳论证缺"样本量、样本代表性、选择性引用"；类比论证缺"类比双方的关键相似点是否真的成立" | 明确写出"缺了什么"，不要只说"证据链不完整" |
| ③ 证据是否捏造 | 反向搜索原始数据源（用 web_search）；核对时间线是否自洽（事件时间/报道时间/引用时间有无矛盾）；数字是否经得起量级估算（费米估算法，很多编造数据一算就露馅） | 找不到原始出处、时间线矛盾、数量级明显不合理 |
| ④ 证据可考证性 | 分三级标注：一手可核实（有链接/可查原始出处）、二手转引（只能查到"某人说"）、无法溯源（孤证、匿名消息源、"业内人士透露"） | 级别越低，这一维分数越低 |
| ⑤ 来源可信度 | 来源历史准确率、作者/来源与该结论是否有利益关联（利益相关方陈述天然降权）、该来源是否有过因类似内容被打脸的记录 | 用 web_search 查该来源过往报道的可信记录 |
| ⑥ 综合置信度 | 不是六维平均，而是取短板（木桶原理）：任一维严重偏低，综合分跟着拉低 | 证据链断了一环，逻辑再漂亮也不该给高分 |
需要外部核实的地方（原始数据源、时间线、来源历史记录）主动用 web_search / web_fetch 去查，不要凭训练知识臆断，也不要因为"这个说法很常见"就默认为真。
第四步：定性/评价句的替代检验（不可量化结论怎么判断真伪）
定性结论没法用数字验证，但可以用三条替代路径：
- 可证伪性测试：这个结论如果是假的，世界应该长什么样？如果作者举不出 "什么情况下这个结论会被推翻"，标记为"不可证伪，存疑"。
- 内部一致性测试：这个定性结论和文章里其他可量化的事实是否矛盾？矛盾就是 造假或逻辑断裂的信号。
- 同行共识锚定法：用 web_search 把这个定性结论放到该领域公开的专家共识/ 综述文章里比对，标注它是"共识观点""少数派观点"还是"孤例主张"三者之一， 在打分里体现——共识观点即使无法精确量化，可信度权重也应高于孤例主张。
第五步：汇总打分与问题清单
产出一张表，每行对应一个核查节点：
| 序号 | 原文定位（段落/引用片段） | 类型 | ①逻辑 | ②证据链 | ③是否捏造 | ④可考证性 | ⑤来源可信度 | 综合置信度(取短板) | 问题说明 |
|---|
问题说明要具体到"缺了什么/矛盾在哪/查不到出处"，不能只写"存疑"。
第六步：输出 Markdown 报告
保存到当前项目的 markdown/ 目录（没有就创建），文件名格式：
markdown/真伪鉴定-<文章标题或简短标识>.md
报告结构：
# 文章真伪鉴定报告：<标题>
## 结论摘要
一句话总结：这篇文章整体可信度如何，最大的问题出在哪一环。
## 论证结构
- 主结论：...
- 分论点：
1. ...
2. ...
## 核查节点明细表
（第五步的表格，全部核查节点）
## 定性结论核查
（第四步涉及的定性/评价句，逐条给出可证伪性/一致性/共识锚定的判断）
## 未核查内容说明
（修辞/过渡/情绪句的简要说明，不用逐条展开）
## 总体置信度
| 项目 | 结果 |
|---|---|
| 核查节点总数 | N |
| 高置信度（≥80） | N |
| 中等置信度（40-79） | N |
| 低置信度（<40，需重点关注） | N |
| **文章整体可信度判断** | 高 / 中 / 低，附一句话理由 |存完文件后用 present_files 呈现报告，简短说一句结论（整体可信度+最大问题点）， 不用把报告内容在对话里重复一遍。
边界情况
- 文章很长（超过几千字）：可以按小节分批处理论证树和核查表，但最终汇总成 一张完整的核查节点表，不要拆成多个文件。
- 纯观点性文章（几乎没有事实陈述）：核查重点转向第四步的定性检验和第一步 的逻辑检验，提前跟用户说明"这篇文章事实性内容较少，核查会以逻辑严密性和 论点一致性为主"。
- 用户只想查某一段/某几句，不是全文：可以只对用户指定的部分走完整流程， 但仍要先看一眼上下文，确认这段话在全文论证结构里的位置，避免断章取义式核查。
- 核查过程中发现证据造假的确凿证据：直接在问题说明里明确指出，不要因为 "不确定意图是不是恶意"而弱化措辞，但也不要过度延伸推测作者动机——只说 "证据与可查证的原始来源不符"这类事实层面的判断，不做诛心之论。
© digoal, GPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/skills_for_claude_web/article-fact-checker of digoal/blog.
Open the folder on GitHubat commit ad6fcb7
Compare with similar skills
Article Fact Checker 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Article Fact Checker this skilldigoal/blog | 8.6k | — | ~956 | Automated safety check: Pass | GPL-2.0 | |
| Markdown Article FormatterJimLiu/baoyu-skills | 27k | 6 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Crosspostingwasp-lang/wasp | 19k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Gzh Designisjiamu/gzh-design-skill | 4k | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Obsidian Markdown
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
Crossposting
wasp-lang/wasp
Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.
Gzh Design
isjiamu/gzh-design-skill
微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…
- Official
Review The Docs
supabase/supabase
Review Supabase docs changes locally in your supabase/supabase checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review).
More from digoal/blog
All 98 skills in this repoArticle Fact Checker
digoal/blog
三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。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 —…
Find Postgres Bug
digoal/blog
Find latent bugs in a local PostgreSQL source tree (RELxxSTABLE branch or HEAD) the way a core hacker does: build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core…
Digoal
digoal/blog
Portable digital employee distilled from digoal's personal blog for PostgreSQL, PolarDB, DuckDB, AI+database, vector/RAG, database operations, source-code reading, technical content creation…
Paper Interpretation
digoal/blog
从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读，并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…
Product Multi Role Analysis
digoal/blog
Analyze a product from documentation, websites, PDFs, articles, release notes, pricing pages, app listings, reviews, filings, or related links; save separate intermediate analyses from seven roles…
Blog Cover Poster
digoal/blog
Turn a blog post, article, notes, or any source material into a set of vertical poster images — one cover plus several coherent content slides that explain the core points.
Related
Categories
Questions about Article Fact Checker
What does Article Fact Checker do?
逐段逐句鉴定一篇文章内容的真伪，拆解论证结构，对每个事实/推断节点做六维核查（逻辑正确性、结论可量化性、证据链完整性、证据是否捏造、证据可考证性、来源可信度），最后输出带原文定位的问题清单和置信度打分表。触发条件：用户提到"鉴别真伪"、"这篇文章可信吗"、"内容审查"、"事实核查"、"fact…. Article Fact Checker is an agent skill from digoal/blog.
When should I use Article Fact Checker?
Article Fact Checker fits situations like: tasks that involve Fact-checking and source verification; tasks that involve Markdown.
How do I install Article Fact Checker in Claude Code?
Run `npx skills add digoal/blog --skill article-fact-checker -a claude-code`. Or copy the skill folder (skills/skills_for_claude_web/article-fact-checker in digoal/blog) into .claude/skills/article-fact-checker in your project. Claude Code loads it when a task matches its description.
How do I install Article Fact Checker in Codex?
Run `npx skills add digoal/blog --skill article-fact-checker -a codex`. Or copy the skill folder (skills/skills_for_claude_web/article-fact-checker in digoal/blog) into .agents/skills/article-fact-checker in your project. Codex loads it when a task matches its description.
Can I use Article Fact Checker 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 digoal/blog --skill article-fact-checker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/article-fact-checker, .gemini/skills/article-fact-checker, .github/skills/article-fact-checker and .opencode/skills/article-fact-checker in your project.
What does Article Fact Checker need to run?
SKILL.md names no scripts, command-line tools or credentials: Article Fact Checker is instructions for the agent only.
Does Article Fact Checker access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Article Fact Checker 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 Article Fact Checker use?
Article Fact Checker is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Article Fact Checker use?
About 956 tokens (SKILL.md is roughly 3.8k 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 Article Fact Checker?
Skills that share tags, products or a category with Article Fact Checker: Markdown Article Formatter (JimLiu/baoyu-skills, 27k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and Crossposting (wasp-lang/wasp, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Article Fact Checker?
digoal (a GitHub user) maintains it in digoal/blog, which has 8,588 GitHub stars. The repository holds 98 skills in this directory. The repository was last updated on October 9, 2026.
Source: digoal/blog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.