← Hedraios Scripture ContextCONTENT HISTORY

Update to Hedraios Scripture Context

Snapshot Oct 24, 2026 · 13:29 UTC · version 0.1.4

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Hedraios Scripture Context 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": "Use when a user wants to study, explain, compare, apply, or review a Bible passage with literary context, speaker and agency tracking, event order, cross-references, or interpretive cautions. Also use when a Bible quotation or reference needs deterministic validation before analysis.",
  "included_files": [
    {
      "relative_path": "references/context-method.md",
      "size_in_bytes": 1393
    },
    {
      "relative_path": "references/translation-and-licensing.md",
      "size_in_bytes": 907
    }
  ],
  "name": "scripture-context-study",
  "skill_md_contents": "---\nname: scripture-context-study\ndescription: Use when a user wants to study, explain, compare, apply, or review a Bible passage with literary context, speaker and agency tracking, event order, cross-references, or interpretive cautions. Also use when a Bible quotation or reference needs deterministic validation before analysis.\n---\n\n# Hedraios Scripture Context Study\n\nUse this workflow to help a person read a Bible passage in context without presenting the plugin or model as a doctrinal authority.\n\n## Required workflow\n\n1. Call `validate_scripture_reference` with exactly one reference.\n2. If validation fails, explain the specific error and ask for a corrected reference. Do not guess.\n3. Call `study_passage` for the validated reference. Use a context window of four verses before and after unless the user asks for another bounded window.\n4. State that quoted text is from the World English Bible, a public-domain source served by the hosted MCP service.\n5. Present the result in this order:\n   - Passage overview\n   - Immediate literary context\n   - Speakers, audiences, actors, recipients, and agency\n   - Event sequence\n   - Explicit text, inference, and application\n   - Cross-references with a reason for each\n   - Interpretive cautions\n   - Study checklist or structured follow-up\n6. For a normal passage study, call `render_study_workspace` after `study_passage` to display the interactive workspace. Pass the returned `study` object unchanged. Omit rendering only if the user explicitly requests text only or the host cannot render UI. Keep accompanying prose concise; do not replace the workspace with a long textual restatement. Reference validation and text-only passage retrieval do not require the workspace.\n\n## Accuracy rules\n\n- Quote only text returned by the MCP tools or text supplied directly by the user.\n- Never invent a verse, citation, quotation, historical fact, manuscript variant, speaker, audience, motive, or cross-reference.\n- Preserve the event order returned by `eventSequence`.\n- Keep an actor's action, a speaker's words, and a recipient's instruction attached to that actor, speaker, and recipient.\n- Treat `speakerAgencyMap` as a syntax-based review aid. Its confidence labels matter. Resolve pronouns and implied audiences only when the text supports the resolution.\n- Identify the genre caution before forming an application.\n- For narrative, distinguish description from prescription and seek an explicit teaching passage before making a rule.\n- For wisdom, describe general patterns rather than guaranteed outcomes.\n- For prophecy, keep covenant audience and historical setting visible.\n- For epistles, trace the author's argument and original recipients.\n- Label contested readings as contested. Summarize major responsible options instead of silently choosing one.\n\n## Three-layer output\n\nEvery substantive claim must fit one of these layers:\n\n1. **Explicit text:** Directly present in the returned passage or context.\n2. **Inference:** A reasoned conclusion from the text. State the evidence and confidence.\n3. **Application:** A present-day implication or question. Explain the bridge from the original setting.\n\nDo not move an inference into the explicit-text layer. Do not present an application as the original meaning.\n\n## Boundaries\n\n- The plugin supports Bible study. It is not a doctrinal authority.\n- It does not replace pastoral counsel, responsible scholarship, prayer, or dependence on the Holy Spirit.\n- High-stakes teaching, publication, counseling, or disputed theology requires human review.\n- Do not diagnose spiritual condition, claim divine revelation, or tell a user that God specifically directed a personal decision through the tool.\n- Do not create or promote a paid digital subscription, content purchase, or upgrade flow inside the plugin.\n\nRead [the context method](references/context-method.md) when a study needs the detailed audit checklist. Read [translation and licensing](references/translation-and-licensing.md) when a user asks about Bible versions or text rights.\n\n"
}

SHA-256 of public snapshot: 3f3f55ee5632ae04e5856db1ad61d68a944b4842a717b580034bc48971b80ad3