<!-- xid: 0AA2CEC66CB2 --> <a id="xid-0AA2CEC66CB2"></a>
Scanned 9/12/2026
Install to Claude Code
npx -y skills add synthaicode/XRefKit --skill fact_review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Fact Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/synthaicode-fact-review)More formats (shields.io, HTML) on the badges page.
<!-- xid: 0AA2CEC66CB2 -->
<a id="xid-0AA2CEC66CB2"></a>
# Skill: fact_review
## Purpose
Review article claims against the visible evidence set so factual gaps,
unsupported wording, and release blockers stay explicit.
## Required Knowledge (XID)
- [Editorial operations framework](../../../../knowledge/packs/editorial-ops/110_editorial_operations_framework.md#xid-F9E58E2BAD21)
- [Context direction guard rules](../../../../knowledge/organization/160_context_direction_guard_rules.md#xid-7A2F4C8D1601)
## Inputs
- article draft
- source links or evidence set
- optional claim list
- target channels
## Outputs
- fact-review result path
- release blockers
- unresolved unknowns
## Startup
- Confirm the draft and source set exist.
- Identify the highest-risk claim classes such as numbers, names, dates, URLs, and quoted assertions.
- Confirm whether the goal is draft feedback or release gating.
## Execution
1. Extract the concrete claims that need checking.
2. Compare each claim to the visible source basis.
3. Classify each result as supported, unsupported, ambiguous, or channel-risky.
4. Mark missing support as `unknown`.
5. Write the review result to the output path and return it.
## Monitoring and Control
- Do not rewrite the article and call it review.
- Do not treat likely truth as verified support.
- Keep opinion and fact findings separate.
## Closure
- Return the fact-review result path.
- Return the release blockers.
- Return the author revision handoff.
## Reporting Contract (共通報告)
- reporting_profile: summary_first
Use the shared [Skill Reporting Contract](../../../../docs/core/contracts/081_skill_reporting_contract.md#xid-6B2D9F4A1C73) in the final report. Start with these headings in this order:
1. Status — done, partial, blocked, or escalated
2. Result — what was produced or decided
3. Evidence — output, evidence, checks, or XIDs
4. Open Items — unresolved unknowns, risks, judgments, or なし
5. Handoff — next owner and next action, or なし
Keep this summary-first section visible before Skill-specific detail; do not omit empty sections.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!