← Samaya Finance SkillsCONTENT HISTORY

Update to Samaya Finance Skills

Snapshot Nov 16, 2026 · 18:17 UTC · version 1.2.2

Collection source: downloaded plugin package.

WHAT CHANGED

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 JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "\"alert me when X files their 10-K\", \"notify me on Y's next earnings transcript\" — sets up a standing Samaya alert for new filings, transcripts, press releases or research. For price alerts use samaya-trigger-price-move.",
  "included_files": [],
  "name": "samaya-trigger-doc-drop",
  "skill_md_contents": "---\nname: samaya-trigger-doc-drop\ndescription: >-\n  \"alert me when X files their 10-K\", \"notify me on Y's next earnings transcript\" — sets up a\n  standing Samaya alert for new filings, transcripts, press releases or research. For price alerts\n  use samaya-trigger-price-move.\n---\n\n# Trigger: Doc Drop\n\nWatches for new documents. Notifies the moment one lands.\n\nNot a search — that's `financial_qa`'s job. This sets up a standing alert:\n\n- \"Alert me the next time Tesla files an 8-K.\"\n- \"Notify me on Apple's next earnings call transcript.\"\n- \"Let me know when any of these three drop a press release.\"\n- \"Ping me on new FOMC statements.\"\n\n## No details yet\n\nOne line, then ask for the two things needed. Nothing else.\n\n> \"I will send you an analysis when new documents you monitor drop. Documents I support include filings, transcripts, IR presentations, press releases, and MS research. Which company (or companies), and what kind of document should I watch for?\"\n\n## Given company + document type\n\n**1. Resolve every company in one batch.** Name or ticker, all in a single `companies` list — never loop calls per company.\n\n**2. Map the ask to a filter:**\n- Broad (\"any filing\", \"everything they publish\") → `datasource_group` (FILINGS, TRANSCRIPTS, PRESENTATIONS, RESEARCH_REPORTS, PRESS_RELEASES, CENTRAL_BANK_COMMUNICATIONS, NEWS, CORPUS_UPLOADS, THIRD_BRIDGE).\n- Specific (\"10-K\", \"earnings call\", \"press release\") → `document_type`.\n- Content-level ask on top (\"...only if it mentions an acquisition\") → `freeform_conditions`. These AND together — stacking more than one or two narrows the alert hard. Say so if the user's piling them on.\n- More than one category asked for in one go (\"filings, transcripts, and press releases\") → one `subscribe_to_document_event` call per category, same company batch in each — `datasource_group` only takes one value per call.\n\n**3. `how_to(\"alerts\")` first, every session** — call order and batching rules live there, not in this skill.\n\n**4. One `subscribe_to_document_event` call per category, every company together within each.**\n\n**5. Confirm what actually got set up** — one line per company per category. A company that failed to resolve gets its own line, not a silent drop.\n\n**6. Point them to the portal, always the same link** — the tool's response doesn't return a usable per-alert URL, so don't hunt for one or show session IDs. Close with: \"Check out the event-triggered agent(s) you just set up: [click here](https://app.samaya.ai/app/agents).\"\n\n**7. Tell them how they'll hear about it:** when a matching document lands, they get the write-up by email and on the Samaya platform — nothing to check manually.\n\n## Rules\n\n- Every company sharing the same filter goes in one call. A loop of single-company calls is a defect.\n- `freeform_conditions` are AND, not OR — flag it when several are stacked.\n- Portal link is always `https://app.samaya.ai/app/agents` — never a per-session or per-subscription URL, and never show a raw session ID or subscription ID to the user.\n- A company that can't be resolved is reported, not silently skipped.\n\n## Before sending\n\n- Company batch and document filter(s) both confirmed before calling.\n- `how_to(\"alerts\")` called this session before `subscribe_to_document_event`.\n- Every company's outcome (success or error), per category, is named.\n- Portal link (`https://app.samaya.ai/app/agents`) included — no session IDs, no invented links.\n- User told: email + Samaya platform, the moment it fires.\n"
}

SHA-256 of public snapshot: 70ad35947e1c0ae0a54a1537be714ef4a22ca05dfa9b98fec7aece7bf5004c62