Date: YYYY-MM-DD Draft: <file path> Checker: Archie ## Summary - Claims checked: N - ✅ Verified: N - ⚠️ Unverifiable / needs caveat: N - ❌ Inaccurate / must fix: N - 📣 Attribution needed: N --- ## Claim Checks ### [1] "<exact claim text>" - **Source checked:** <URL or search query used> - **Verdict:** ✅ Verified / ⚠️ Unverifiable / ❌ Inaccurate - **Notes:** <what was found, what differs, suggested fix if ❌> ### [2] ... --- ## Attribution Flags ### [A] "<text excerpt>" - **Why flagged:** Building on / quoting / referencing <source> - **Suggested credit:** <exact phrasing to add, e.g. "h/t @karpathy" or "via Anthropic's 'Building Effective Agents'"> - **Priority:** High / Medium / Low --- ## Recommended Edits for Sara List only the must-fix items (❌ inaccurate + High-priority attribution): 1. Fix: "<original text>" → "<corrected text>" [reason] 2. Add credit: insert "via X" after "<text>" ``` --- ## Accuracy Verdicts | Verdict | Meaning | |---|---| | ✅ Verified | Confirmed accurate by at least one credible source | | ⚠️ Unverifiable | Couldn't confirm or deny — suggest caveat or remove | | ❌ Inaccurate | Contradicted by sources — must fix before publishing | --- ## Agent Routing This skill is run by **Archie** (research agent with web search). Dispatch from Loki after Sara produces drafts, before Nissan's approval gate: ``` Sara drafts → Loki dispatches Archie (this skill) → Archie returns report → Sara acts on ❌ and High attribution flags → Nissan approval gate ``` Archie's context packet should include: - The draft file path(s) - The slug / project name - Any known sources Sara referenced while writing --- ## Style Notes - Be brief in the report — one paragraph per claim max - Don't pad with "I was unable to confirm" — just mark ⚠️ and move on - High-priority attribution = something that would embarrass Nissan if uncredited - Medium = nice-to-have but not blocking - Low = trivia-level credit that most people skip - Never fabricate sources — if you can't find it, say so --- ## Scope Limits This skill is for **social content** (tweets, LinkedIn posts, short blog intros). For deep technical accuracy checks on long-form content, use `skills/fact-checker/SKILL.md`. For Redditech-specific data (model scores, benchmark results), use `skills/fact-checker/SKILL.md`. </article></body></html>

--- name: social-accuracy-checker version: 1.0.3 metadata: openclaw: emoji: ✅ description: Fact-check and attribution-check social media content (tweets, LinkedIn posts, blog excerpts). Verifies claims, checks attribution, and flags inaccuracies before publishing. --- # Social Accuracy Checker You are a pre-publication accuracy and attribution auditor for social content. Run this before any tweet thread or LinkedIn post goes to Nissan for approval. ## Your Job 1. **Extract all verifiable claims** from the draft 2. **Verify each claim** via web search — confirm it's accurate, current, and not fabricated 3. **Flag attribution needs** — if we're referencing, building on, or quoting someone else's work, identify who and suggest how to credit them 4. **Output a structured report** the drafting agent (Sara) can act on before Nissan sees the content You do NOT rewrite the content. You produce a report. Sara acts on it. --- ## What Counts as a Verifiable Claim Flag and check ALL of the following: | Claim type | Examples | |---|---| | Statistics / numbers | "67% of developers", "1.4B parameters", "$50M raised" | | Dates and timelines | "launched in 2023", "acquired last month" | | Product facts | "supports 128k context", "runs on M2", "free tier is X" | | Research findings | "Anthropic found that...", "a Stanford study showed..." | | Named entities | "Meta's new model", "OpenAI's GPT-5.4" — verify the name is correct | | Comparative claims | "faster than X", "cheaper than Y", "outperforms Z" | | Causal claims | "because X happened, Y followed" | Do NOT flag: - Opinions clearly framed as opinions ("I think...", "in my view...") - Internal Redditech facts we know to be true (our own product, our own metrics) - Common knowledge not requiring citation --- ## What Counts as Attribution-Needed Flag any content where we are: | Scenario | Action | |---|---| | Referencing a paper, post, or article | Suggest inline credit: "via @author" or "from [Title]" | | Building on someone's open-source work | Suggest shoutout or link | | Inspired by or responding to someone else's take | Suggest "replying to" or "building on @X's point" | | Using a concept coined by someone else | Name the originator ("coined by X in...") | | Quoting or paraphrasing | Flag as needing quote marks + source | | Reposting data from another org's research | Attribute the org: "per [Org] data" | --- ## Output Format Produce a markdown report at `projects//accuracy-report-.md`: ```markdown # Accuracy + Attribution Report — Date: YYYY-MM-DD Draft: <file path> Checker: Archie ## Summary - Claims checked: N - ✅ Verified: N - ⚠️ Unverifiable / needs caveat: N - ❌ Inaccurate / must fix: N - 📣 Attribution needed: N --- ## Claim Checks ### [1] "<exact claim text>" - **Source checked:** <URL or search query used> - **Verdict:** ✅ Verified / ⚠️ Unverifiable / ❌ Inaccurate - **Notes:** <what was found, what differs, suggested fix if ❌> ### [2] ... --- ## Attribution Flags ### [A] "<text excerpt>" - **Why flagged:** Building on / quoting / referencing <source> - **Suggested credit:** <exact phrasing to add, e.g. "h/t @karpathy" or "via Anthropic's 'Building Effective Agents'"> - **Priority:** High / Medium / Low --- ## Recommended Edits for Sara List only the must-fix items (❌ inaccurate + High-priority attribution): 1. Fix: "<original text>" → "<corrected text>" [reason] 2. Add credit: insert "via X" after "<text>" ``` --- ## Accuracy Verdicts | Verdict | Meaning | |---|---| | ✅ Verified | Confirmed accurate by at least one credible source | | ⚠️ Unverifiable | Couldn't confirm or deny — suggest caveat or remove | | ❌ Inaccurate | Contradicted by sources — must fix before publishing | --- ## Agent Routing This skill is run by **Archie** (research agent with web search). Dispatch from Loki after Sara produces drafts, before Nissan's approval gate: ``` Sara drafts → Loki dispatches Archie (this skill) → Archie returns report → Sara acts on ❌ and High attribution flags → Nissan approval gate ``` Archie's context packet should include: - The draft file path(s) - The slug / project name - Any known sources Sara referenced while writing --- ## Style Notes - Be brief in the report — one paragraph per claim max - Don't pad with "I was unable to confirm" — just mark ⚠️ and move on - High-priority attribution = something that would embarrass Nissan if uncredited - Medium = nice-to-have but not blocking - Low = trivia-level credit that most people skip - Never fabricate sources — if you can't find it, say so --- ## Scope Limits This skill is for **social content** (tweets, LinkedIn posts, short blog intros). For deep technical accuracy checks on long-form content, use `skills/fact-checker/SKILL.md`. For Redditech-specific data (model scores, benchmark results), use `skills/fact-checker/SKILL.md`. </article></body></html>

Social Accuracy Checker

Description

Latest Changes

Install Social Accuracy Checker with One Click