Data fidelity
Skill Tibsfox/gsd-skill-creator/examples/skills/research/data-fidelity
Fact-checking and source verification workflow for research documents. Launches parallel fact-checkers, aggregates findings, applies corrections systematically.From its SKILL.md
npx -y skills add Tibsfox/gsd-skill-creator --skill data-fidelityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
SKILL.md
2.0 KB, 389 tokens by cl100k_base, as published. Nobody here has run it
Data Fidelity
Activates when research documents need verification, fact-checking, or data updates.
When to Use
- After initial research documents are written (quality gate before publish)
- When refreshing documents with current data (market prices, company stats)
- When a user says "check for errors", "verify claims", "fact check", "add fidelity"
Workflow
Phase 1: Fact-Check Fleet
Launch 2-3 parallel fact-checker agents, each covering a different document range:
- Agent A: docs 01-12
- Agent B: docs 13-24
- Agent C: forward-looking/speculative docs (if any)
Phase 2: Aggregate Findings
Collect reports. Categorize by severity:
- ERROR — factually wrong, must fix
- QUESTIONABLE — might be wrong, needs verification
- INCONSISTENCY — contradicts another document
Phase 3: Data Refresh
Launch market-researcher agents for current pricing, company data, and industry stats.
Phase 4: Apply Corrections
Systematic edit pass:
- Fix all ERRORs first
- Resolve INCONSISTENCYs (pick the correct value, update all occurrences)
- Update data with fresh market research
- Flag QUESTIONABLE items that couldn't be resolved
Phase 5: Rebuild
If documents have HTML/PDF output, rebuild after corrections:
bash build.sh
Quality Standards
- Every numerical claim should have a source or explicit reasoning
- Cross-document consistency: same number must be the same everywhere
- Dates should be specific (not "recently" — say "March 2026")
- Company names should be current (post-merger names, current HQ)
- Legal citations should include statute number (USC, CFR, RCW)
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.