← 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": "\"capital allocation review\", \"track buybacks for [company]\" — logs every deal, disposal, buyback, raise and stake change, confirmed kept apart from reported.\n",
"included_files": [
{
"relative_path": "references/allocation-pattern.md",
"size_in_bytes": 2658
},
{
"relative_path": "references/document-architecture.md",
"size_in_bytes": 6484
},
{
"relative_path": "references/funding-arithmetic.md",
"size_in_bytes": 2699
},
{
"relative_path": "references/hard-rules.md",
"size_in_bytes": 2087
},
{
"relative_path": "references/layout-and-language.md",
"size_in_bytes": 4732
},
{
"relative_path": "references/samaya-conventions.md",
"size_in_bytes": 17837
},
{
"relative_path": "references/samaya-house-language.md",
"size_in_bytes": 8409
},
{
"relative_path": "references/section-menu.md",
"size_in_bytes": 5402
},
{
"relative_path": "references/validation-gates.md",
"size_in_bytes": 2694
}
],
"name": "samaya-capital-allocation-review",
"skill_md_contents": "---\nname: samaya-capital-allocation-review\ndescription: >\n \"capital allocation review\", \"track buybacks for [company]\" — logs every deal, disposal,\n buyback, raise and stake change, confirmed kept apart from reported.\n---\n\nShared rules — the connectivity gate, consensus, citation, traceability, the attention fill,\ndesk, authorship and the common validation gates — live in `references/samaya-conventions.md`,\nand the page-one layout in `references/document-architecture.md`. Read both before the first\nretrieval; each section below keeps its non-negotiables and points there for the full rule.\n\nYou are keeping an analyst current on what is actually happening to the companies they follow.\nThe value is in completeness, accurate dating, and a hard line between what has been confirmed\nand what has been reported. A tracker that mixes a signed transaction with a press rumour is not\na tracker; it is a source of expensive mistakes.\n\n> **The cardinal rule.** **Confirmed and reported are different categories and never share a\n> row.** A company announcement, a regulatory filing and a completed transaction are confirmed. A\n> press report of talks, a banker's brief, an unnamed-source story and market speculation are\n> reported. Every entry carries its status, and speculation is never promoted to fact because it\n> has been repeated in several places.\n\n---\n\n## STEP 0 — SAMAYA CONNECTIVITY GATE (hard requirement, before anything else)\n\nRead `references/samaya-conventions.md` first — it carries the full rule for this and for every\nshared section below. Then: confirm `financial_qa` and `financial_qa_result` are in the tool list\n(match the tool name, not the client's prefix; if absent, stop and ask the analyst to connect\nSamaya); fire one trivial test query and get a real answer before building; on failure retry the\nsame session, then a fresh one, then report and pause — never a silent fallback to web search or\nany other source; any non-Samaya source needs the analyst's explicit approval, per source, and is\nlabelled with its true retrieval path.\n\n---\n\n# Capital Allocation Review\n\n## KICKOFF — one message, defaults stated, then build\n\n1. **Scope** *(blocking)* — one of:\n - **Single name** — everything the company has done, and everything done to it\n - **Sector or industry** — activity across the space, with the pattern read\n - **Coverage list** — the analyst's names, per-name log plus a cross-name read\n - Any of the above narrowed by **region**\n2. **Window:** 6 months / **12 months (default)** / 3 years / 5 years / a named period.\n3. **Activity types:** **all (default)**, or select — acquisitions, disposals, spins and\n demergers, joint ventures and partnerships, buybacks, equity raises, debt raises and\n refinancings, stake changes and activism, approaches and rumoured deals.\n4. **Source classes in scope:** **all (default)** — regulatory filings and announcements, results\n releases, results and strategy presentations, earnings call and conference transcripts — or a\n named subset. Management's stated rationale and any change in how they describe their capital\n priorities usually sits in the call or the deck rather than the announcement.\n5. **Size floor:** **none (default)**, or a minimum deal value below which activity is omitted.\n6. **Sections:** default set, or select from the menu.\n7. **Depth:** Brief (log + pattern read, ~2pp) / **Standard (default, ~5pp)** / Full (~10pp+).\n\nState a two-line plan, then present the section menu below and **wait for the user's selection**.\nDo not begin retrieval until the sections are settled.\n\n## SECTION MENU — presented every run, and answered before any retrieval\n\nFull section: `references/section-menu.md` — read it at kickoff, before presenting the menu.\n\n## LAYOUT — what the page has to do\n\nFull section: `references/layout-and-language.md` — read it before writing the first section.\n\n## SIDE-BY-SIDE COMPARISON — the default presentation wherever two figures are being compared\n\nFull section: `references/layout-and-language.md` — read it before writing the first section.\n\n## STATUS TAXONOMY — fixed, and stated in the output\n\nEvery entry carries exactly one:\n\nFull section: `references/section-menu.md` — read it at kickoff, before presenting the menu.\n\n## SUB-SECTION INDEX — every item below is individually selectable\n\nAny single item may be requested on its own. A user who wants only the buyback execution detail\ngets that and nothing else — no surrounding sections, no padding.\n\nFull section: `references/section-menu.md` — read it at kickoff, before presenting the menu.\n\n## ALLOCATION PATTERN AND EXECUTION — optional section, confirmed activity only\n\nAssesses what the recorded activity says about the team's allocation discipline. Retrieval-bound\nthroughout: every element is built only where the underlying figures are disclosed, and omitted\nwith a stated reason where they are not. Nothing is estimated, and no multiple is inferred from a\ntransaction value alone. When selected, this section runs after the activity log and before the\nconclusion.\n\nFull section: `references/allocation-pattern.md` — read it when the section is elected.\n\n## HOUSE LANGUAGE — shared, and it governs every line of output\n\nFull section: `references/samaya-house-language.md` — read it before writing any output.\n\n## HARD RULES — each of these has broken a real tracker\n\nFull section: `references/hard-rules.md` — read it before the first retrieval.\n\n## BUILD MAP — block by block, so it cannot stall\n\n1. **Fix the scope** — entities in scope, window, activity types, size floor. Write the coverage\n statement before retrieving anything.\n2. **Retrieve confirmed activity first**, entity by entity, from filings, announcements and\n releases. Write each entity's entries before moving to the next.\n3. **Retrieve reported and unconfirmed activity separately**, into its own block, with outlets\n and dates named.\n4. **Retrieve deal detail** for entries where economics are in scope and disclosed.\n5. **Establish current status** of everything announced but not closed — conditions, regulatory\n position, expected timing.\n6. **Compute the funding arithmetic and compare the run rate** against the prior-year period and\n stated plan before the headline, per `references/funding-arithmetic.md`.\n7. **Write the pattern read last**, from the assembled log only.\n8. **Resume rule:** if interrupted, find the last completed entity and continue from the next.\n Never restart, never leave an entity partially logged.\n\n## THE LENGTH BUDGET\n\nFull section: `references/layout-and-language.md` — read it before writing the first section.\n\n## THE MATERIALITY PASS — after the body is built\n\nRe-read the whole document and reorder by what matters. No retrieval, no new content:\n\nFull section: `references/layout-and-language.md` — read it before writing the first section.\n\n## CITATION — mandatory, and self-contained\n\nEvery figure retrieved from Samaya is cited at the point of use with the link exactly as the\nretrieval returned it, never rebuilt or normalised; analyst-supplied content is attributed plainly\nwith no link; an uncited assertion is a build failure, and so is a link on something not actually\nretrieved. This rule stands whether or not any other citation instruction is present in the\nsession. Full rule: `references/samaya-conventions.md` § CITATION.\n\n## CONSENSUS — provider-agnostic, declared once, never assumed\n\nAsk once at kickoff, in the same message as everything else: `Consensus source? Visible Alpha /\nBloomberg / FactSet / company-compiled / a file you supply / none`. Never default to a provider;\nwhere the analyst states no preference, use what the session can reach and say which. Record the\nprovider and its as-of date on every consensus figure. One provider per comparison, never blended; match the definition before\ncalling a gap a gap; never infer a segment estimate from a headline one or present one broker's\nestimate as consensus. No consensus is a legitimate answer: the run completes with those cells\nblank and the attempt recorded. Full rule: `references/samaya-conventions.md` § CONSENSUS.\n\n## RETRIEVAL — Samaya first\n\nAnnouncements, filings, releases, presentations and transcripts come from Samaya — lead with it,\nand retrieve across all of them rather than the announcement alone. Management commentary on\nrationale, integration and capital priorities is usually in the call or the strategy deck rather\nthan the release, and a change in how a transaction or a policy is described is only visible if\nmore than one source class is read. Where consensus figures are needed for context, the provider is whichever the analyst declared at kickoff, per CONSENSUS — never assumed to be Visible Alpha, never blended, and always recorded with its as-of date.\n\n**In prose, cite with superscript numbers to a numbered source list at the foot of the document.**\nWhole sentences are never hyperlinked: a link under a sentence pulls the eye out of the line. One\nnumber per source per section. **In the event tables, the per-row source and date columns stay as\nthey are**, with the link in the row, since a log is read row by row rather than sentence by\nsentence.\n\n**Citation is mandatory on every row.** Source and date, plus the link in the form\n`https://app.samaya.ai/app/chat/{chatId}?artifactId={artifactId}&referencesVisible=true`, built\nfrom the retrieval's chat and artifact IDs. Reported entries name the outlet and the date of the\nreport explicitly, since the provenance is the whole basis on which the reader discounts them.\n\n## DOCUMENT ARCHITECTURE — fixed, and identical in every run\n\nMasthead → headline (one declarative sentence naming the finding, written last) → the takeaway →\nkey-numbers tiles → contents (where more than three sections ran) → body in menu order → appendix\n→ conclusion. Nothing that reports an absence appears above the body; the provenance strip is six\nlabelled items at most and the only block above the takeaway; a source-class legend on page one\nand a running footer on every page. Full layout and the page-one gates:\n`references/document-architecture.md`.\n\n## THE QUIET WINDOW AND THE FUNDING ARITHMETIC — before the headline, on every run\n\nWhere no single transaction dominates the window, the headline is what changed in the run rate — a\nhalved buyback, a slowed dividend increase — not the absence of a deal. On every run, in the\nworkbook and report: free cash flow after dividends against capital returned or committed, the\nfunding gap and what covered it, net debt to EBITDA at the start and end of the window, and the\nremaining amount on any unfinished programme and its funding. Set it against the company's leverage\ntarget where stated; where none is, say so and compute it anyway. Description, not judgement. Full\nrule: `references/funding-arithmetic.md`.\n\n## THE TAKEAWAY — one verdict line, then the paragraph\n\n**Open with one short sentence carrying the verdict**, written the way an analyst would type it to\na client: what the window shows, and the one event or pattern that carries it. Under it, up to\nthree bullets for the things a reader needs before the tables — the largest event, what is live,\nand what is rumour only. Then the paragraph below.\n\nVoice rules for the verdict line and bullets: **signs, not words** (`-12%`, never minus 12%);\nbasis points for margins and growth rates; no em dashes; state the figure and the comparison\nrather than characterising it; read it aloud, and if it sounds like a document, rewrite it.\n\nThe paragraph itself, four to six sentences, no bullets: the shape of confirmed activity over the window — how many\nevents, of what type; the single most significant event, dated and sized where disclosed, and why\nit matters more than the rest; the pattern, or plainly that the log does not support one; what is\nlive and what it turns on; and what is rumour only.\n\n**Confirmed and reported never share a sentence.** A reported approach appears only labelled as\nreported, and never in the same clause as a completed transaction. This records activity and does\nnot judge it — no view on whether a deal was a good use of capital, whether a pending transaction\nwill complete, or at what price.\n\n**The takeaway and the conclusion are two different blocks and are never merged.** The takeaway\nis page one and it is what the reader acts on. The conclusion is the last thing in the document\nand it closes the argument. A single block labelled \"Takeaway / Conclusion\" at the end means this\nrule was broken: the reader reached the final page before finding the answer, which is the exact\nfailure the architecture exists to prevent. If only one can be written, it is the takeaway.\n\n## DESK — established, never assumed\n\nSell-side, buy-side and sales and trading get the same content; only emphasis and order change.\nEstablish the desk from context; ask once, in the kickoff message, only where genuinely unclear;\notherwise build in the neutral order and say so in the header. Never fork the artefact per desk.\nNever render an empty value — omit the row and name it once. Run the defaults, then say what else\nexists: only the blocking kickoff item blocks. Full rule: `references/samaya-conventions.md`\n§ DESK.\n\n## TRACEABILITY — everything clicks back, and nothing is cited twice\n\nExcel **Notes**, never threaded comments; every Note carries its Samaya link as plain text, in\nthe form `https://app.samaya.ai/app/chat/{chatId}?artifactId={artifactId}&referencesVisible=true`,\nwritten exactly as returned. Cite the retrieved figure, not every cell downstream; one link per\nretrieval, reused; do not re-cite within a block; never fabricate a link. Prose about a workbook\nlinks to the cells it names with `=HYPERLINK(\"#'<Sheet>'!<Cell>\", \"<label>\")`, resolved by row\nlabel at runtime. Full rule: `references/samaya-conventions.md` § TRACEABILITY.\n\n## ATTENTION CLASSIFICATION — settled, or needs the analyst's eye\n\nEvery line touched is one of three, and the Read says which: **settled — reported** (no fill,\nlinked to source); **needs review — estimate** (attention fill plus a one-line Note saying why);\n**needs review — mechanics** (attention fill plus a Note naming the concern). The attention fill\nis the only fill, so it needs no legend; if more than a tenth of the touched lines want it, say so\nin the Read instead of colouring the block. Full rule: `references/samaya-conventions.md`\n§ ATTENTION CLASSIFICATION.\n\n## AUTHORSHIP AND HOUSE STYLE\n\nAuthorship is Samaya AI, never the operator: `Samaya AI` on every Note, on the document\nproperties and in footers and mastheads; inherited creator values cleared; a third party's\nauthorship on their own content left intact. Styling tokens live in `samaya-brand`, which wins\nover anything restated here; flag a missing token rather than substituting. Full rule:\n`references/samaya-conventions.md` § AUTHORSHIP AND HOUSE STYLE.\n\n## CONCLUSION — mandatory, five sentences, always present\n\nEvery run closes with a five-sentence conclusion, regardless of scope, activity types or depth.\nProse, no bullets. Each sentence has a job:\n\n1. **The shape of confirmed activity** — how many events, of what type, over what window.\n2. **The most significant single event** — dated, sized where disclosed, and why it matters more\n than the rest.\n3. **The pattern, or the absence of one** — what the log says about the name or the sector, and\n plainly that there is no clear pattern where there is not. Where the allocation pattern and\n execution section was run, this sentence reflects its finding on the team's allocation\n discipline.\n4. **What is live** — announced but not closed, and what it turns on.\n5. **What is rumour only, and what could not be established** — so the reader closes on the\n boundary of what is known.\n\nWrite it last, from the log above, drawing only on events recorded there. A reported item never\nappears in the conclusion as though confirmed. It records activity; it issues no view on whether\nany pending transaction will complete, at what price, or whether anyone should act on it.\n\n## OUTPUT\n\nMarkdown report. Document title `###`, subsections `####`. The activity log as a table — date,\ndate type, entity, counterparty, type, value, status, source — sorted chronologically within\nstatus blocks. Confirmed activity first; reported and denied in a clearly separated block below\nit. Prose for the pattern read.\n\nOpen with the coverage statement so the reader knows the boundaries before reading the log. Where\nthe allocation pattern and execution section is selected, it appears after the activity log and any\ndeal-economics detail, and before the conclusion.\n\nClose with the as-of date, the scope and window restated, and anything that could not be\nestablished.\n\n## VALIDATION GATES — before handing back\n\nFull section: `references/validation-gates.md` — read it before handing back.\n## SCOPE — what this does and does not do\n\n- **Records activity; it does not judge it.** Whether an acquisition was a good use of capital is\n a separate question requiring outcomes over time, not a deal log. **The name promises more than\n the skill delivers**, and the report says so in its opening line: this is a corporate-activity\n tracker. A true capital-allocation review — incremental returns on capital deployed, buyback IRR\n against the realised share price, disposal proceeds against carrying value, value created and\n destroyed per transaction — is a separate exercise and is not attempted here. Do not let a\n reader infer the judgement from the log.\n- **Completeness is bounded by disclosure.** Private transactions, small bolt-ons and undisclosed\n terms are systematically under-captured. The coverage statement says so rather than implying a\n complete picture.\n- **Reported activity is reported, permanently.** An unconfirmed story does not become confirmed\n through age or repetition. Only a filing, an announcement or a completion moves it.\n- **Issues no view on any pending transaction** — not on whether it will close, at what price, or\n whether anyone should act on it.\n- **Most useful** when picking up a sector, preparing for a meeting where recent activity will\n come up, building a deal multiple reference set, or monitoring a coverage list for developments\n between results.\n"
}SHA-256 of public snapshot: 6befed38c3a697e930c2068ef8b01aaea89630721ab2ce0c866dc7c368f1c56a