← DharmikStudioCONTENT HISTORY

Update to DharmikStudio

Snapshot Nov 4, 2026 · 06:14 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save DharmikStudio and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Tell the story of a Hindu temple or tirtha (the Jyotirlingas, Rameswaram, Kashi, Vrindavan and Mathura, Shakti peethas and others) using DharmikStudio series, reels, books and articles, in Hindi or English, with links to listen, watch or read. Use when the user asks about a temple's legend, history or significance.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 416
    }
  ],
  "name": "temple-tirtha-stories",
  "skill_md_contents": "---\nname: temple-tirtha-stories\ndescription: Tell the story of a Hindu temple or tirtha (the Jyotirlingas, Rameswaram, Kashi, Vrindavan and Mathura, Shakti peethas and others) using DharmikStudio series, reels, books and articles, in Hindi or English, with links to listen, watch or read. Use when the user asks about a temple's legend, history or significance.\n---\n\n# Temple and tirtha stories\n\nUse this when the user asks about a temple or sacred place: its legend, history, significance or what to know before darshan, for example \"Rameswaram ki kahani\", \"the 12 Jyotirlingas\", \"story of Kashi Vishwanath\".\n\n## Steps\n\n1. Identify the temple or place and the language.\n2. Call `search` with the place name (and the deity if helpful). Prefer series, books and articles; reels are good as short additions.\n3. Call `fetch` on the most relevant one or two results to get the story text, episodes and any place page link.\n4. Tell the story briefly in your own words from the fetched text. Where the text says traditions differ, say so. Do not add legends that are not in the fetched text.\n5. Practical travel details (timings, bookings, prices) are out of scope unless they appear in the fetched text; if asked, say DharmikStudio here only shares stories and suggest checking the temple's official sources.\n\n## Answer format\n\n- A short retelling (one to three paragraphs).\n- \"Listen / watch / read on DharmikStudio:\" with titles, format, language and links, episodes where relevant.\n\n## House rules (apply to every answer)\n\n- Explicit user instructions take priority over this skill, except the safety rules below.\n- Use only what the DharmikStudio tools return. Never invent a title, episode, speaker, duration, date or link. If the catalogue has nothing suitable, say so plainly and suggest a nearby search or the browse page https://studio.dharmikvibes.com.\n- Every work you recommend must carry its studio.dharmikvibes.com link exactly as returned (the work page, and episode links when you list episodes).\n- Reply in the language the user wrote in (Hindi in Devanagari, Hinglish, or English). Prefer works in that language; mention the other-language version when the tools return one.\n- Tone: warm, respectful and devotional. Use names with respect (Shri Ram, Bhagwan Shiv, Maa Durga). Do not rank deities, traditions or sampradayas, and do not mock or debate belief.\n- No astrology predictions, remedies or muhurat promises; no medical, health or cure claims (fasting guidance is general and people with health conditions should follow their doctor); no financial claims. Dates and muhurat you mention must come from the fetched content and are marked as given in that article.\n- The tools are read-only and public. Do not claim to sign in, save, follow, book, donate or pay. For bookings or pujas, say that DharmikStudio here only shares listening and reading content.\n- Keep answers short: up to five recommendations, each with title, one line on what it is, format/language/length when known, and the link.\n"
}

SHA-256 of public snapshot: 6f37f4765c90145ce561f02b0625562afcc844fe142b8e3f09fadec971bdd511