← Samaya Finance SkillsCONTENT HISTORY
WHAT CHANGED
Update to Samaya Finance Skills
Snapshot Nov 16, 2026 · 18:17 UTC · version 1.2.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Samaya Finance Skills and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "\"fact-check this deck\", \"audit this 10-K summary\", \"can you verify the numbers in this doc\", \"double-check this workbook against the filings\", \"does this presentation still hold up\" — verifies every figure, date and named claim in an existing Word, PDF, PowerPoint or Excel file against Samaya and writes an Excel audit log. Verification only; it does not write new content.",
"included_files": [
{
"relative_path": "references/audit-schema.md",
"size_in_bytes": 3582
},
{
"relative_path": "references/docx.md",
"size_in_bytes": 3929
},
{
"relative_path": "references/pdf.md",
"size_in_bytes": 2022
},
{
"relative_path": "references/pptx.md",
"size_in_bytes": 1973
},
{
"relative_path": "references/samaya-house-language.md",
"size_in_bytes": 8409
},
{
"relative_path": "references/xlsx.md",
"size_in_bytes": 1596
},
{
"relative_path": "scripts/annotate_pdf.py",
"size_in_bytes": 4723
},
{
"relative_path": "scripts/annotate_pptx_notes.py",
"size_in_bytes": 3204
},
{
"relative_path": "scripts/annotate_xlsx.py",
"size_in_bytes": 2942
},
{
"relative_path": "scripts/build_audit_log.py",
"size_in_bytes": 5726
},
{
"relative_path": "scripts/comment_with_link.py",
"size_in_bytes": 7157
}
],
"name": "samaya-fact-checker",
"skill_md_contents": "---\nname: samaya-fact-checker\ndescription: >-\n \"fact-check this deck\", \"audit this 10-K summary\", \"can you verify the numbers in this doc\",\n \"double-check this workbook against the filings\", \"does this presentation still hold up\" —\n verifies every figure, date and named claim in an existing Word, PDF, PowerPoint or Excel file\n against Samaya and writes an Excel audit log. Verification only; it does not write new\n content.\n---\n\n# Fact-Checker\n\nExtract every checkable quantitative fact, date/period, and named claim from an uploaded\ndocument, verify each against Samaya-sourced data, and produce an audit log Excel workbook.\nOptionally annotate the original file in place with citation comments.\n\nThis is a **verification** skill: it never edits the substance of the source document (numbers,\nclaims, structure) and never adds new content beyond citations. It only checks and annotates.\n\n## HOUSE LANGUAGE — shared, and it governs every line of output\n\nRead `references/samaya-house-language.md` before writing any output: no sayings, no \"X, not Y\",\nno metaphors, the ordinary word rather than the academic one, answers scored against the question\nasked without grading the answerer, signs not words, and the materiality pass before handing back.\nThe worked examples in that file are the operative version of these rules.\n\n## Preflight (confirm before extracting)\n\n1. **Identify the file and format.** If more than one file is attached, confirm which one to\n check. Route to the matching reference file for extraction/annotation mechanics:\n `references/docx.md`, `references/pptx.md`, `references/xlsx.md`, `references/pdf.md`.\n2. **Confirm Samaya is connected.** Every verification routes through the Samaya MCP. If the\n connector is not available, say so and stop — do not verify from web search or memory alone.\n3. **Ask once, upfront, whether to also annotate the original file** with inline citations, in\n addition to the audit log (which is always produced). Word, Excel, and PDF support genuine\n inline comments; PowerPoint gets citations written into each flagged slide's speaker notes\n instead (no native PPTX comment API is reachable from any tool in this environment — see\n `references/pptx.md`). Make this an upfront yes/no, not a per-item prompt.\n\n## Build order\n\n1. **Extract.** Read the document per its format (see the matching reference file) and pull out\n every quantitative fact, date/period, and named/qualitative claim, each with a `description`,\n `original_value`, and precise `location` (page/paragraph for Word, slide # for PowerPoint,\n sheet+cell for Excel, page # + a short verbatim snippet for PDF). Assemble this list in a\n working JSON payload as you go — this is the same payload every downstream script consumes\n (see `references/audit-schema.md` for the exact shape).\n2. **Cluster and verify via Samaya.** Group items by (company, source document) — related facts\n from the same filing go in **one** Samaya query as a compound question; unrelated clusters\n (different companies, different documents, unrelated topics) go as separate calls. Do not\n combine unrelated clusters into one query, and do not fire one query per literal fact when\n several facts trace to the same document. See \"Sourcing\" below for routing by data type.\n3. **Flag each item** — exactly one of `Match`, `Stale`, `Mismatch`, `Unable to verify` (see\n `references/audit-schema.md` for what each means; fold immaterial rounding differences into\n `Match` rather than treating them as their own category).\n4. **Build the audit log:**\n ```bash\n python scripts/build_audit_log.py data.json audit_log.xlsx\n ```\n5. **If the user opted into inline annotation**, run the script matching the source format:\n ```bash\n # Excel source\n python scripts/annotate_xlsx.py original.xlsx data.json annotated.xlsx\n # PDF source\n python scripts/annotate_pdf.py original.pdf data.json annotated.pdf\n # PowerPoint source (writes to speaker notes, not visible slide content)\n python scripts/annotate_pptx_notes.py original.pptx data.json annotated.pptx\n # Word source — unzip once, then run this per item, then rezip (see references/docx.md):\n python scripts/comment_with_link.py unpacked/ \"<one-line comment> {{LINK}}\" --url \"<source URL>\"\n # Needs the `docx` helper skill; without it, write the OOXML comment parts directly or\n # deliver the audit log alone and say why. A missing helper skill never stops the run.\n ```\n Each annotation script silently skips items whose `location.type` doesn't match that format,\n so it's safe to run against the full payload.\n\n Annotations are short by design — one verdict line (flag, then values only where they\n differ), then the source document and date. They don't restate the anchored text and never\n say \"via Samaya.\" In Word the URL hides behind the word `link`; in Excel and PDF, whose\n comments are plain text, it goes on its own line. The full reconciliation lives in the audit\n log, not in the margin. See `references/docx.md` for the exact shapes.\n6. **Deliver** the audit log (always) plus the annotated file (if opted in). Summarize counts by\n flag in chat (e.g., \"14 Match, 2 Stale, 3 Mismatch, 1 Unable to verify\").\n\n## Sourcing — route by data type, not by habit\n\n| Claim type | Route |\n|---|---|\n| Reported actuals, segment/financial figures, guidance language, management facts | Company filings & transcripts via Samaya (10-K/10-Q/8-K/20-F/6-K/proxy/annual report/earnings call) |\n| Forward estimates / street consensus | The consensus provider the document names, or what Samaya can reach for the name, with its as-of date — never a single broker's estimate presented as consensus |\n| Price or any single point-in-time market figure | Market data via Samaya, stated as-of a date |\n| Named officers/executives | Latest proxy statement, 10-K, or 8-K via Samaya |\n| Ownership | Latest 13F/13D filings via Samaya |\n| Market-position / competitive claims (\"market leader\", \"largest provider\") | Check against the most recent disclosed market-share or ranking data via Samaya if it exists; otherwise flag `Unable to verify` — do not treat an un-sourceable qualitative claim as a `Mismatch` |\n| Recent events / news | Most recent filings and press releases via Samaya, not a newswire aggregator |\n\nNever invent a route not on this list, and never cite a newswire summary of a number when a\nfiling is the source. If every Samaya route returns nothing for a claim, flag `Unable to\nverify` — don't force a verdict.\n\n## Querying Samaya\n\nSend the query as a **single `financial_qa` call per (company, source document) cluster** —\nSamaya handles multi-fact, compound questions about one company/document well on its own, so\ndon't split a cluster into one call per fact. Only split into separate calls when clusters are\ngenuinely independent (different companies, different unrelated documents) — run those as\nseparate calls with a fresh `session_id` each, not combined into one mega-query that would blur\nwhich returned figure supports which original claim.\n\nUse the exact document title and URL Samaya's `references` return for the audit log's Source\nDocument / Source URL columns — never assemble a URL from a pattern or invent one. If Samaya\nreturns no URL for an otherwise-confirmed source, write `\"no link returned\"`, not a guess.\n\n## Guardrails (non-negotiable)\n\n1. Use only disclosed or Samaya-retrieved information to verify claims — no memory-based\n figures, dates, or officeholders standing in for a real check.\n2. Never render a verdict as an investment recommendation or valuation opinion — a flag reports\n whether a stated fact ties to a disclosed source, nothing more.\n3. Never fabricate a source document, date, or URL. `Unable to verify` is always the correct\n flag when no real source was found — never a guessed `Match`.\n4. Never alter the substance of the original document — no correcting the number in place, no\n rewriting claims. Verification and citation only; the person decides what to fix.\n5. Don't force a flag: an immaterial rounding difference is `Match` with a note, not a fabricated\n fifth category; a genuinely unverifiable qualitative claim is `Unable to verify`, not a\n `Mismatch` by default.\n\n## Before delivery\n\n- Every item in the audit log has exactly one of the four valid flags.\n- Every `Match`/`Stale`/`Mismatch` item has a populated Source Document, Source URL, and\n As-Of Date; `Unable to verify` items clearly state why (no route / undisclosed / subjective).\n- No source URL was invented — every one traces to an actual Samaya `references` return.\n- If inline annotation was requested, every flagged location that exists in the original file\n received an annotation, and the annotated file opens cleanly (spot-check by reopening it).\n- Every annotation is one verdict line plus a source line — no restated body text, no raw URL\n in a Word comment where a hyperlinked `link` was possible.\n- No investment-recommendation or valuation language anywhere in the audit log or annotations.\n"
}SHA-256 of public snapshot: 09287897a14dad91e8bc8aeac4f695c34fb3d4d5e868b95b5666ac54eb075f25