Verify public claims
Skill jqaisystems/jqai-ai-skills/skills/verify-public-claims
Check public-facing copy against supplied evidence and current public sources, classify every material claim, and produce defensible rewrites. Use when a user asks to fact-check website copy, release notes, case studies, marketing claims, public profiles, reports, articles, product descriptions, or other material before publication.From its SKILL.md
npx -y skills add jqaisystems/jqai-ai-skills --skill verify-public-claimsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.1 KB, 543 tokens by cl100k_base, as published. Nobody here has run it
Verify Public Claims
Turn public-facing statements into a traceable claim ledger, then revise the copy so every material assertion matches the available evidence.
1. Establish the review contract
- Confirm the copy, intended audience, publication surface, relevant date, and evidence supplied by the user.
- Identify whether the request covers factual accuracy, freshness, wording strength, source quality, or all four.
- Browse current public sources when a claim may have changed or the user asks for current verification.
- Use only public sources or evidence the user has approved for this review.
- Do not treat inaccessible, login-only, or missing material as verified.
2. Build the claim ledger
- Use assets/claim-ledger-template.md.
- Split compound sentences when their parts need different evidence.
- Record the exact claim, source, publication date, event date when different, verification date, evidence excerpt or paraphrase, and intended rewrite.
- Read references/evidence-statuses.md before assigning a status.
- Focus on claims that affect trust, decisions, eligibility, scope, performance, recency, identity, or attribution.
3. Classify each claim
Use exactly one primary status:
supported: direct, relevant, sufficiently current evidence supports the wordingqualified: the core is supported, but the wording needs a limit, date, scope, or attributioninference: the conclusion is reasonable but is not stated directly by the evidenceunsupported: no adequate evidence supports the material claimstale: the evidence may once have supported the claim but is too old for present-tense use
When sources conflict, preserve the conflict in the ledger and prefer the most direct authoritative current source. Do not resolve uncertainty by averaging, guessing, or silently choosing the most favorable version.
4. Rewrite to the evidence level
- Keep supported claims precise.
- Add the required scope, date, source, or attribution to qualified claims.
- Label inference as analysis, interpretation, estimate, or recommendation.
- Remove unsupported claims or replace them with narrower wording that the evidence supports.
- Update stale claims only when a current source is available; otherwise hold or date the wording.
- Never invent citations, metrics, testimonials, dates, credentials, customers, outcomes, or source access.
5. Report the result
Return the completed claim ledger, revised copy, sources checked, unresolved conflicts, held claims, and review date. For legal, medical, financial, safety-critical, or regulated claims, require a current authoritative source and appropriate human review before publication.
What ships with it: 3 files
2.9 KB alongside SKILL.md
agents/
- openai.yaml242 B
assets/
- claim-ledger-template.md1.1 KB
references/
- evidence-statuses.md1.6 KB