claim-accuracy
Skill2 starsChanged 5 months agoMITView on GitHub
Make content factually accurate and internally consistent so answer engines trust and cite it — verify claims, source them, keep facts consistent across pages and the web, cut overclaims, and correct what AI gets wrong about a brand. Works for any business, B2B or B2C, product or service. Use when the request is to fact-check content for AI, fix inaccuracies or overclaims, ensure factual consistency for AEO, improve trustworthiness, or correct AI misrepresentations of a brand. Pairs with evidence-and-citations and entity-optimization.
In this repository26 other files it gives its agents.
- aeo-foundationSkill
- ai-capability-signalingSkill
- ai-crawler-accessSkill
- ai-referral-analyticsSkill
- ai-retrievabilitySkill
- ai-visibility-auditSkill
- ai-visibility-trackingSkill
- answer-engineeringSkill
- author-authoritySkill
- chatgpt-optimizationSkill
- claude-optimizationSkill
- community-and-reviewsSkill
- comparison-contentSkill
- competitor-ai-analysisSkill
- content-freshnessSkill
- crawler-log-analysisSkill
- digital-prSkill
- entity-optimizationSkill
- evidence-and-citationsSkill
- gemini-optimizationSkill
- google-ai-overviews-optimizationSkill
- llms-txtSkill
- multimodal-aeoSkill
- perplexity-optimizationSkill
- prompt-researchSkill
- structured-dataSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Read aeo-foundation.md for the canonical facts, claims, and any compliance constraints (especially YMYL — health, finance, legal).
- Distinctive: line 48
Correct, transparently: When something changes or was wrong, fix it and date it.
- Distinctive: line 56
Check internal consistency: Ensure the same facts (pricing, dates, capabilities, results) match across all of the brand's own pages.
- Distinctive: line 63
Detect and fix AI misrepresentations: Test what the major engines currently say about the brand (see ai-visibility-audit).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claim Accuracy
Answer engines behave like accuracy and consensus machines: they favor claims they can verify and corroborate, and they deprioritize unsupported or overstated assertions. Accuracy is therefore not just ethics — it is an AEO signal. This skill makes a brand's content verifiable, internally consistent, and free of overclaims, and fixes the cases where engines repeat something false about the brand. It works for any business, B2B or B2C, and pairs tightly with evidence-and-citations (adding proof) and entity-optimization (consistent facts).
When to use this skill
- Fact-checking content meant to be cited by AI.
- Removing overclaims and unsupported assertions that engines discount.
- Reconciling facts that differ across a brand's pages or profiles.
- Correcting inaccurate or outdated things AI assistants say about the brand.
Before you start
Read aeo-foundation.md for the canonical facts, claims, and any compliance constraints
(especially YMYL — health, finance, legal). If it is missing, point to the
aeo-foundation skill.
Principles
- Accuracy is a trust signal. Verifiable, correct content is favored; a detectable error or overclaim erodes how readily engines cite the source.
- Support every strong claim. Unsupported confidence backfires — pair claims with a source, a statistic, or a clear basis (see evidence-and-citations), or soften them.
- Be consistent everywhere. The same fact should read the same across your pages and your off-site profiles; contradictions inject doubt and weaken entity recognition.
- No hype inflation. "Best," "leading," "guaranteed," and invented numbers without backing are liabilities, not assets.
- Correct, transparently. When something changes or was wrong, fix it and date it.
Workflow
- Inventory claims. Pull every checkable assertion — numbers, superlatives, comparative statements, dates, capabilities, guarantees.
- Verify each. Confirm against a primary or authoritative source. Cite it, correct it, or soften it. Anything you cannot support gets reworded or removed.
- Check internal consistency. Ensure the same facts (pricing, dates, capabilities, results) match across all of the brand's own pages.
- Check external consistency. Reconcile against the brand's other profiles and listings — hand the cross-web check to entity-optimization (and its consistency tool).
- Strip overclaims. Replace unbacked superlatives and vague boasts with specific, supported statements — or cut them.
- Detect and fix AI misrepresentations. Test what the major engines currently say about the brand (see ai-visibility-audit); for each error, fix the upstream source the engine is likely drawing on (your page, a profile, a third-party listing) and, where possible, the authoritative record.
- Keep a source of truth. Maintain the canonical facts in
aeo-foundation.mdso future content stays consistent.
Output format
- A claims audit: each checkable claim marked verified / needs-source / overclaim, with the fix.
- Inconsistencies found across pages or profiles, and how to reconcile them.
- AI misrepresentations observed, with the upstream source to correct for each.
(assumption)tags where a fact could not be verified.
Common pitfalls
- Superlatives and invented numbers with no backing — discounted by engines.
- Stale statistics or dates that make a page demonstrably wrong.
- The same fact stated differently on different pages.
- Ignoring what AI already says incorrectly about the brand.
- "Fixing" content while leaving the third-party source of the error untouched.
Related Skills
- evidence-and-citations — the sources and data that turn a claim into a supported one.
- entity-optimization — consistent canonical facts across the web.
- ai-visibility-audit — surfaces what engines currently say (and get wrong).
- aeo-foundation — the source of truth for the brand's facts and claims.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

