← 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": "\"historical pattern\", \"has this happened before\", \"precedents for X\" — confirms and generalizes the situation, finds 3-5 similar cases via Samaya, rates how close each is, and says what they suggest for the current one.",
  "included_files": [],
  "name": "samaya-historical-pattern",
  "skill_md_contents": "---\nname: samaya-historical-pattern\ndescription: >-\n  \"historical pattern\", \"has this happened before\", \"precedents for X\" — confirms and generalizes\n  the situation, finds 3-5 similar cases via Samaya, rates how close each is, and says what they\n  suggest for the current one.\n---\n\n# Historical Pattern\n\n## Samaya rules\n- Use `financial_qa` for every lookup. If it returns `running`, poll `financial_qa_result` with the `job_id`. Never re-call for the same question.\n- Keep relative time wording (\"last 5 years\", \"most recent\") verbatim in the question.\n- `financial_qa` returns citations, not answers. Write your own answer from the snippets. Cite each source with its date and link.\n- If a source has no publication date, cite it as \"undated\". Never guess a date.\n- Batch related lookups into one call. Aim for 6-10 `financial_qa` calls per run.\n\n## Steps\n\n1. **Confirm the situation.** Call `financial_qa` for the facts: who did what, when, and why.\n   - If the sources don't confirm the situation as the user described it, say so in one line. Then generalize from what the sources show actually happened.\n   - Record the event date.\n\n2. **Generalize it.** Write one sentence that removes the company names and keeps the mechanism.\n   - Example: RELY lowers price to match WU promotions becomes \"A company responds to competitor pricing pressure by cutting its own price.\"\n   - Note 2-3 features that matter for matching: industry structure, relative size of the players, whether the move is temporary or permanent.\n\n3. **Search for precedents.** Run 2-4 `financial_qa` calls in parallel, each with a fresh `session_id`. Phrase them around the general situation:\n   - The general situation across industries, in the last 5 years\n   - The same, limited to the current company's industry\n   - The same, limited to adjacent industries\n\n   Only use instances dated before the event. You may include a later instance, labelled \"peer case (after the event)\".\n\n4. **Pick and rate 3-5 instances.**\n   - Rate each one for similarity:\n     - **3:** same mechanism, same industry, similar structure\n     - **2:** same mechanism, different industry or structure\n     - **1:** same mechanism only\n   - Drop 1s unless fewer than 3 instances remain. Drop any instance with no clear outcome.\n   - Get outcomes (margins, share, stock reaction, and management commentary on later calls) in 1-2 batched calls.\n\n5. **Check what happened since.** If the current event is more than 3 months old, make one call on what has happened since: results, guidance, stock move.\n\n## Output\n\n1. **Takeaway:** 1-2 sentences giving the main conclusion. For example: \"The precedents point to share gains with modest take-rate pressure. The main risk is a de-rating, not margin damage.\"\n2. **Situation:** the generalized situation in one line. Add a premise note if step 1 didn't confirm the situation as described.\n3. **Instances:** one table per instance, ordered by similarity with the highest first:\n\n| Field | Content |\n|---|---|\n| Similarity | 1-3, with a one-line reason |\n| Historical situation | Company, date, what they did |\n| Why it resembles now | Shared mechanism and features |\n| Outcome | What happened to price, share, margin, stock, with dates |\n| Implication for now | What this case suggests for the current situation |\n\n4. **Since the event:** include only if step 5 ran. A few lines on what has already played out.\n5. **Overall read:** 2-3 lines covering where the precedents agree, where they split, and the key difference from the current case.\n\nCite every fact with the source name, date and link."
}

SHA-256 of public snapshot: 4a8ad1a123ae7d93e0d2dc890b44ce9c448d9965009e845303e05876cd532f86