Skip to main content
skill CX Codex

sk-facts — Claude Code skill: fact checking

The sk-facts Claude Code skill checks factual claims and records research in a fact ledger. It starts when a claim, number, source, or media licence needs checking.

MIT ★ 204 updated 2026-11-09

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add howznguyen/shorts-kit --skill sk-facts -a claude-code
Open on GitHub

What sk-facts does

The skill searches docs/facts/facts.json, checks claims against sources, and stores claim records in facts.json and source details in sources.json. Each claim gets a status and caveat. Images, clips, fonts, and music are recorded with their exact licence; factual narration lines link to record IDs.

Read the schema in docs/facts/README.md before adding records. Run bun run facts and bun run lint <id> to validate the ledger and a video's fact references; Bun is required. Lint blocks unverified claims, while contested ones need a caveat.

What it helps with

  • trace a numerical claim to a primary source
  • record a disputed claim with its caveat
  • check the licence for an image or audio asset
  • link a narration line to a fact record

Example prompts for the agent

  • Check this claim and find its primary source.
  • Add this number to the fact ledger with its caveat.
  • Find the licence for this photo and record its source.

How to install sk-facts

1Skills CLI (Vercel)

npx skills add howznguyen/shorts-kit --skill sk-facts -a claude-code

2Manually: put the files in place

~/.claude/skills/sk-facts/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/sk-facts/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about sk-facts

How do I install sk-facts in Claude Code?

Run npx skills add howznguyen/shorts-kit --skill sk-facts -a claude-code. The skill file is installed at ~/.claude/skills/sk-facts/SKILL.md.

What does sk-facts do?

It checks factual claims and stores their status and sources in ledger files. It also records media licences and connects facts to narration lines.

How does sk-facts validate the ledger?

bun run facts checks the schema and source references; bun run lint <id> checks facts referenced by a video. Contested claims need a caveat.

Source text

SKILL.md · MIT
---
name: sk-facts
description: Researches, verifies and records the factual claims of a short in the fact ledger (docs/facts/facts.json and sources.json), including the licence of every image, clip and dataset. Use when the user says "check this fact", "is this true", "find a source for", "research the topic", "add to the ledger", "where does this number come from", "can I use this photo", or when lint reports a missing or unverified fact. Step 2 of sk-pipeline, and the step to return to whenever a number changes.
---

# sk-facts: source, verify, record

**Announce:** "Using sk-facts for <topic>."

Rules: §9 (`docs/soul/07-facts.md`); schema in `docs/facts/README.md`. Read the
schema before writing the first record. The § wins over this file.

**Core principle: research that exists only in prose cannot be re-checked.** The
output of this skill is records in two files, not a paragraph in a brief:

- `docs/facts/facts.json`: one record per claim:
  `{ "id": "f-0001", "claim", "value", "status": "verified|contested|unverified", "sources": ["s-0001"], "caveat", "checkedAt": "YYYY-MM-DD" }`
- `docs/facts/sources.json`: one record per source:
  `{ "id": "s-0001", "title", "url", "publisher", "licence", "accessed": "YYYY-MM-DD" }`

## Steps

1. **Search the ledger before researching.** `grep -i "<keyword>" docs/facts/facts.json`.
   Re-researching a claim already recorded wastes a session; re-using a claim
   already found wrong is worse.
2. **Split the claim from the number.** Write it as subject, measure, where, when
   ("river X, width, at point Y, dry season"). A claim that cannot be pinned to a
   place and a time is not checkable: pin it or cut it.
3. **Source in tiers.**
   1. Primary or institutional: the original paper, agency, statistics office,
      official record, the document itself.
   2. Encyclopaedic: follow through to *its* citation and read that.
   3. Popular articles and listicles: use them only to find candidates. Two
      tier-3 sources agreeing is still tier 3.
   Follow laundered claims to the end. Ten blogs copying each other are one
   source; if the chain ends at nothing, drop the claim.
4. **Read the original wording yourself.** Summarisers and extraction tools keep
   the number and drop the hedge: "probably reduced" becomes "reduced". That turns
   a model estimate into a measurement, and nothing downstream catches it because
   the number is still right. `claim` and `caveat` are written from text you read.
5. **Flag hypotheses as hypotheses.** Superlatives ("largest", "only", "first")
   almost always have a competing definition: state it or drop the superlative.
   "Recently discovered" and anniversaries: check the year.
6. **Write the record, whatever the answer.**
   | status | meaning | on screen |
   |---|---|---|
   | `verified` | you read it in the original | yes |
   | `contested` | real but sources disagree, or common phrasing is wrong | only with a `caveat`, and say it in the caption (`sk-handoff`) |
   | `unverified` | not checked yet | no; lint blocks it |
   A claim you proved wrong is still worth a record with a `caveat` saying so: a
   popular belief that is false is often the best hook, and the record stops
   someone re-researching it later.
7. **Record every image, clip, font and music track as a source** with its exact
   `licence` string (e.g. "CC BY 4.0", "public domain", "CC0", "licensed: <terms>").
   Take attribution text verbatim from the provider; it often carries a year or
   author that is part of the requirement. Prefer public domain and CC0; CC BY
   needs a credit line (on screen or in the pinned comment). Never use imagery
   whose terms you have not read, including map tiles and stock sites' previews.
8. **Link narration lines to facts.** Each line that states a fact carries
   `"fact": "f-xxxx"` in `src/videos/<id>/narration.json`.
9. **Validate.**
   ```bash
   bun run facts        # ledger schema, ids, source references
   bun run lint <id>    # every referenced fact exists and is verified (contested needs caveat)
   ```

## Verify

- [ ] ledger searched before researching
- [ ] every on-screen or spoken number has a `verified` record (or `contested` + caveat)
- [ ] no claim rests only on a tier-3 source
- [ ] every `url` in sources.json was actually opened this session
- [ ] every image and audio asset has a source record with a licence
- [ ] `bun run facts` exits clean, with no new warnings
- [ ] anything that could not be verified was cut, not softened into vagueness

Next: back to `sk-brief` (or `sk-narration` if the brief exists).

© howznguyen · MIT · howznguyen/shorts-kit

Similar skills

SKILL.md skills catalog →
facts backnotprop facts is a Claude Code skill that distills key points about planned or completed work. It runs only after an explicit $facts invocation. CX Codex +1 587installs ERP Facts Jaikin-SASU ERP Facts MCP server connects an agent to sourced ERP details, support dates and e-invoicing status for system comparisons and Odoo 20 upgrade assessments. CX Codex +1 Leonida Lab: GTA 6 facts, official or not LeonidaLab Leonida Lab: GTA 6 facts, official or not is an MCP server for Claude Code that answers questions about GTA 6 with facts labeled official, reported or unannounced. CX Codex +1 find-skills vercel-labs find-skills is a Claude Code skill that locates agent skills for a task and helps assess the results. It activates when someone asks for a capability that may already be installable. CX Codex +1 4,400,000installs frontend-design official anthropics The frontend-design skill guides intentional visual design for new interfaces and redesigns. Use it when a generic generated UI is not enough. CX Codex +1 1,025,790installs agent-browser vercel-labs This Claude Code skill automates browser interaction for tasks like navigating sites, filling forms, and testing web apps. It also supports exploratory QA and Electron app automation. CX Codex +1 1,600,000installs design-taste-frontend Leonxlnx The design-taste-frontend Claude Code skill sets design rules and checks for websites. It activates for new pages, redesigns, and requests to fix a generic-looking site. CX Codex +1 802,600installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. CX Codex +1 1,424,476installs

From the same set10

The whole set →
sk-brief sk-brief — a Claude Code skill that shapes a short-video idea into a brief, choosing a story flow and visual types. It checks image licences before any script is written. CX Codex +1 ★ 204repo stars sk-style The sk-style Claude Code skill polishes spoken scripts for short videos while keeping their meaning intact. It activates on requests to tighten wording, improve flow, or remove AI-sounding phrases. CX Codex +1 ★ 204repo stars sk-render The sk-render Claude Code skill renders short videos to MP4, normalizes audio, and prepares the file for upload. It activates for render and export requests, loudness fixes, or reports of broken output. CX Codex +1 ★ 204repo stars sk-narration sk-narration — a Claude Code skill that writes or edits short-video scripts, generates voice tracks, and runs narration checks. It activates for script, pronunciation, pacing, or voice changes and narration lint errors. CX Codex +1 ★ 204repo stars sk-handoff sk-handoff — a Claude Code skill that prepares a finished short for upload with a cover, encoded video, caption, and pinned comment. It runs on requests to make a thumbnail, write copy, add credits, or prepare the post. CX Codex +1 ★ 204repo stars sk-scene The sk-scene Claude Code skill builds and fixes short-form video scenes in Remotion. It activates for requests to create shots, adjust captions or motion, and check layouts. CX Codex +1 ★ 204repo stars sk-promo The sk-promo Claude Code skill builds ads, launch films, and feature teasers in vertical or landscape formats. It takes a video from the initial brief through storyboard checks and delivery. CX Codex +1 ★ 204repo stars sk-pipeline The sk-pipeline Claude Code skill guides a narrated vertical short from the initial idea to upload-ready files. It activates for new videos, editing supplied footage, or resuming a project. CX Codex +1 ★ 204repo stars

Project sponsors

Companies that keep this analytics open