Use when user asks about a biblical passage's meaning, wants to validate an analogy or idea against the text, or needs cross-references with scholarly evidence. Also use when a question about Scripture lacks a passage anchor. Requires explicit confidence tiering, MCP data before answering, and formal verdict for analogy questions.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Use when user asks about a biblical passage's meaning, wants to validate an analogy or idea against the text, or needs cross-references with scholarly evidence. Also use when a question about Scripture lacks a passage anchor. Requires explicit confidence tiering, MCP data before answering, and formal verdict for analogy questions.
Scholarly Q&A for biblical texts. Three auto-detected modes: MEANING (lexical/linguistic explanation), VALIDATE (analogy/idea checking), CROSS-REFERENCE (related passages). Graduated confidence with hard epistemic boundaries and honest pushback when evidence is insufficient.
Foundational principle: Violating the letter of the rules is violating the spirit of the rules.
Iron Rules
Rule 1: State Confidence Tier First — Always
Every response begins with a confidence declaration. No exceptions.
Tier 1 (linguistic) or Tier 2 (discourse) from MCP tools
Full answer, no hedging
MEDIUM
Tier 3 (scholarly consensus) from web search — scholars agree, MCP inconclusive
Answer with citations + caveat: "based on scholarly consensus, not directly verifiable"
LOW
Tier 4 only — MCP inconclusive, scholars disagree
State what IS known, then: "Beyond this, I am speculating." Point to specific scholars.
CANNOT ANSWER
No MCP data, no scholarly consensus, or outside biblical scholarship
Refuse. State what's missing. Suggest where to look.
Hard limits:
Topic mode (no passage provided) caps at MEDIUM. No exceptions. MCP was not run.
VALIDATE verdicts require MEDIUM minimum. Below MEDIUM → INSUFFICIENT DATA, not a verdict.
Training-data knowledge is NOT Tier 1 evidence. Only MCP output counts as Tier 1-2.
Contested scholarly debates require confidence splitting. When scholars genuinely disagree on a question (e.g., the meaning of μονογενής), do NOT pick a winner. Present both positions with their evidence. Split confidence by claim type:
Morphological facts (what MCP returns) → can be HIGH
Semantic/theological debate (what scholars dispute) → MEDIUM at best
Flagged controversies require both-sides presentation. At the MEANING, VALIDATE, and CROSS-REFERENCE entry points, call with the passage reference and/or the topic keyword. When returns one or more records (non-empty array):
query_controversies
query_controversies
topics
Present ALL major positions with their evidence and named scholars — do not summarize into one view.
Surface the neutrality_caveat from the response verbatim or nearly verbatim.
Do NOT declare a winner, even if one position appears stronger based on the MCP linguistic data.
Apply confidence splitting: linguistic/morphological sub-claims may be HIGH; the disputed historical or interpretive conclusion is LOW or MEDIUM at most.
When query_controversies returns {topics: []} (no match): proceed normally without a controversy block.
Example (Exodus dating):
CONFIDENCE: HIGH (morphological context), LOW (date dispute)
[Called query_controversies: topic "exodus date" — record returned]
Scholarly positions:
- Early Date (ca. 1446 BCE): based on 1 Kings 6:1 (480 years before Temple) and Judges chronology.
Scholars: Kitchen (On the Reliability of the Old Testament, 2003), Merrill (Kingdom of Priests, 1996).
- Late Date (ca. 1260 BCE): based on Ramesses II Raamses/Pithom building campaigns.
Scholars: Bright (A History of Israel, 4th ed., 2000), Hoffmeier (Israel in Egypt, 1997).
Neutrality caveat: [verbatim from query_controversies neutrality_caveat]
The agent does not resolve this debate. The morphological data in the text is uninformative on the date question.
Wrong:
CONFIDENCE: MEDIUM
The Exodus most likely occurred around 1260 BCE based on the archaeological evidence for Ramesses II.
(Resolved a flagged controversy. Dismissed one scholarly position without presenting it.)
Wrong:
CONFIDENCE: HIGH
"One and only" is the linguistically accurate translation. The word does NOT mean "only begotten."
(Resolved a contested debate. Dismissed one scholarly position.)
Correct:
CONFIDENCE: HIGH (morphology), MEDIUM (semantic debate)
Morphological data: μονογενής — compound of μόνος + γένος [query_morphology]
Scholarly debate:
- Position A ("unique/one-of-a-kind"): BDAG, Moody (1953), Lee (2005) — γένος root, not γεννάω
- Position B ("only begotten"): Dahms (1983), Pendrick (1995) — patristic usage, γεννάω echo
This is an active scholarly debate. The morphological data supports Position A, but
Position B has serious patristic and contextual arguments. The agent does not resolve
what scholars dispute.
Correct:
CONFIDENCE: HIGH
Evidence: query_morphology confirms ἐκένωσεν (ekenōsen) as aorist active indicative with reflexive ἑαυτόν (heauton)
Wrong:
The text clearly shows Jesus voluntarily emptied himself.
(No confidence declaration. No MCP citation. Training knowledge presented as established fact.)
Rule 1a: Transliteration Rendering
Render every Greek/Hebrew word as script + the MCP-supplied transliteration, never a
romanization recalled from training data. query_morphology returns two distinct
transliteration fields, and the convention is applied per field, per position:
text_translit — the inflected surface form as it appears in the passage.
Render this next to the word when it appears in running prose.
lemma_translit — the dictionary headword transliteration. Render this next to
a cited lemma.
Three cases:
First occurrence in the output:script (translit) — e.g. ἐπιτελέσει (epitelesei),
lemma ἐπιτελέω (epiteleō).
Every occurrence thereafter:translit alone — e.g. epitelesei.
MCP transliteration null/absent for that field: bare script — never invent a
romanization. A word's surface form and lemma headword are independently null/populated.
Do not "correct" or improve an awkward server value — render it verbatim, even when it
looks unusual (e.g. an idiosyncratic server romanization is still the correct render).
This convention is identical to exegetical-notes' Transliteration Rendering rule — the two
skills must not disagree.
Rule 2: Gather MCP Data Before Composing Any Answer
If a passage is provided, MCP data is gathered BEFORE any prose is written.
Do not compose the answer from training data and then verify. Gather data first. Let the data shape the answer.
Primary method: Spawn the biblical-scholar agent via Agent tool (see Sub-Agent Delegation). The agent handles MCP tool selection, testament routing, and data compression internally.
Fallback method (if agent spawn fails): Call MCP tools directly using the selection table below:
Tier B (supports MEDIUM): Study Bibles with scholarly notes, TDNT, ABD, established scholars (Fee, Moo, Wright, Beale, Carson)
Tier C (MEDIUM with caveat): Popular commentaries, credentialed blogs — label: "[Tier C source, use with caution]"
Tier D (never cite): Devotional websites, AI content, uncredited blogs, forums
If only Tier C sources found, say: "No Tier A/B source located. [Tier C source, use with caution]"
If no source found after web search, say: "I could not find scholarly sources on this question." Do NOT say "scholars have not addressed this."
Rule 4: VALIDATE Mode Requires a Formal Verdict
When the user presents an analogy, illustration, or idea for validation, render one of four verdicts.
Verdict
Meaning
Usage guidance
SUPPORTED
Text evidence directly backs the analogy
Safe to present as reflecting what the text communicates
COMPATIBLE
No contradiction, no positive evidence
May use pastorally — present as APPLICATION, not what the text MEANS
NOT SUPPORTED
Text or context actively opposes this reading
Do not use as representing the passage
INSUFFICIENT DATA
Confidence below MEDIUM
No verdict rendered. State what's missing.
Format:
VERDICT: COMPATIBLE
The text does not specify the nature of Paul's thorn. Your analogy does not contradict 2 Cor 12:7-10. However:
- No lexical evidence supports "anxiety" specifically
- σκόλοψ = sharp stake/splinter; context favors physical affliction
- "Messenger of Satan" language has no modern psychological parallel
You may use this analogy pastorally, but present it as APPLICATION, not as what the text means.
Rule: Text evidence must be presented BEFORE the verdict. The verdict follows the evidence, not the other way around.
Wrong:
The analogy is pastorally useful as a point of contact but breaks down if pressed too hard exegetically.
(No verdict. Evidence not first. Drifted into pastoral application.)
Rule 5: No Devotional Drift
This skill produces scholarly analysis. Application is the user's job.
The skill explains what the text means. It does not:
Tell the user what they should do
Generate pastoral counseling
Produce devotional content
Tell the user how this "speaks to" their situation
Wrong:
God uses our anxiety for his purposes, and this passage reminds us to rest in his sufficient grace.
Correct:
The text presents divine power as perfected in human weakness (v.9b). The scope of application is the user's to determine.
Question Routing
The skill detects mode from the question. No user flag needed.
Mode 1: MEANING — triggered by:
Questions about what a word, phrase, or sentence means
"How would I explain X to a modern person?"
Questions about grammatical function, voice, tense
Mode 2: VALIDATE — triggered by:
User presents their own analogy, illustration, or comparison
"Does this hold up?" / "Is this accurate?" / "Can I say..."
User wants to check their idea against the text
Mode 3: CROSS-REFERENCE — triggered by:
"What other passages connect to this?"
Questions about thematic links, how a passage fits the biblical storyline
"How does this relate to...?"
Ambiguous questions: Default to MEANING mode. If a question genuinely spans modes (e.g., "What does X mean and can I compare it to Y?"), handle both sequentially — MEANING first, then VALIDATE.
Topic mode (no passage): When no passage is provided, the skill enters topic mode. Warn immediately:
⚠️ TOPIC MODE: No specific passage provided. Confidence ceiling: MEDIUM.
MCP data cannot be verified without a passage. This answer draws on web search and training data.
Sub-Agent Delegation
This skill delegates data gathering and scholarly interpretation to the biblical-scholar agent, which internally delegates MCP data retrieval to the data-retriever agent (Haiku).
CONFIDENCE: line → inherit as skill's confidence ceiling
VERDICT: line (VALIDATE mode) → use directly in skill output
## Scholarly Sources → integrate into Data Sources
## Limitations → surface in evidence summary
Fallback: If Agent tool fails or agent returns CANNOT ANSWER, fall back to direct MCP tool calls per Rule 2 table. Note the fallback in the response.
Workflow
1. Parse input
→ Extract passage (if any) and question
→ Detect mode: MEANING / VALIDATE / CROSS-REFERENCE
→ If no passage: enter topic mode, warn, cap confidence at MEDIUM
2. Delegate to biblical-scholar agent (if passage provided)
→ Spawn via Agent tool with mode-mapped prompt (see Sub-Agent Delegation)
→ The agent handles: pericope checking, MCP data gathering, scholarly interpretation
→ Parse agent response for: CONFIDENCE, analysis, verdict (if VALIDATE), sources
→ If agent spawn fails: fall back to direct MCP tool calls per Rule 2 table
2a. Call `query_controversies` for the passage and/or topic
→ Call BEFORE composing any prose response
→ Arg shape: `mode: "passage"` with `book` + `range` when a passage is identified;
`mode: "topic"` with `topic` for open-ended questions (e.g., topic mode, Exodus dating);
`mode: "list"` to enumerate all available controversy records.
Example (passage): `query_controversies: {"mode": "passage", "book": "Exodus", "range": "12:1-40"}`
Example (topic): `query_controversies: {"mode": "topic", "topic": "exodus date"}`
→ If `topics` array is non-empty: insert the both-sides block per the Flagged Controversies rule above
→ If `topics` is empty: proceed without controversy block
→ Fallback: if the tool call fails, note "Controversy check unavailable" and proceed
3. Topic mode (if no passage)
→ Print the ⚠️ TOPIC MODE warning block FIRST, before any analysis.
This warning is the FIRST text the user sees. Not after the answer.
Not embedded in the confidence line. A standalone block at the top.
→ Web search to identify 2-3 key passages for the topic
→ Spawn biblical-scholar for at least ONE identified passage (mandatory — topic
mode still requires MCP grounding on concrete text)
→ Confidence ceiling: MEDIUM
4. Web search (supplementary — only if agent's sources insufficient)
→ Search for scholarly commentary on passage + question topic
→ Evaluate source quality (Tier A/B/C/D)
→ For CROSS-REFERENCE: search specifically for intertextual connections
→ If search returns nothing useful: say so — do not fabricate consensus
5. State confidence tier
→ Inherit from biblical-scholar if delegation succeeded
→ Cap at MEDIUM if topic mode or if agent returned LOW/CANNOT ANSWER
→ Based only on what the agent and web search returned
6. Compose answer
→ Required: confidence declaration, evidence summary, answer, data sources
→ Mode-specific additions (see Output Format)
→ No devotional content, no unsourced claims
Output Format
Required in every response:
Topic mode warning (topic mode only) — the ⚠️ TOPIC MODE block is the FIRST
thing output, before confidence, before anything else. Not optional.
Confidence tier — prominently (after topic mode warning if applicable)
Evidence summary — what MCP tools were called, what was found
Answer — scaled to complexity
Data sources — MCP tools queried + scholarly works cited
MEANING mode adds:
Original language data with [query_morphology] attribution
Discourse context (function in clause/paragraph)
Modern explanation — labeled "for a contemporary audience," separated from technical data. Rule 5 still applies here. Explain what the Greek means in plain language. Do not shift into devotional register ("the promise here is…," "God doesn't start what he won't finish," "this reminds us…"). The section translates linguistics, not theology. Application remains the user's job.
Scholarly positions if genuinely debated (with specific citations) — split confidence: morphology HIGH, debate MEDIUM. Do not resolve what scholars dispute.
VALIDATE mode adds:
Text evidence first (MCP data on what the passage actually says)
Then: VERDICT: SUPPORTED / COMPATIBLE / NOT SUPPORTED / INSUFFICIENT DATA
Point-by-point comparison of analogy against text
Usage guidance if SUPPORTED or COMPATIBLE
CROSS-REFERENCE mode adds:
Ranked list of cross-references, each labeled:
Primary — shared lemma (query_vocabulary evidence) or explicit citation (query_ot_quotes)
Secondary — shared concept, different vocabulary (discourse/thematic evidence)
Entity — entity continuity (query_people, query_places, or query_person_network)
Editorial tradition — TSK/OpenBible-derived (query_cross_references). Always label as "editorial tradition candidate (N votes)" — NOT as Primary or Secondary evidence. These are tradition-based associations, not linguistically verified connections.
When analyzing dialogue passages, query_speakers data provides structured speaker attribution
Divine speech markers are theologically significant for revelation claims
Speaker transitions mark discourse boundaries
Caveat: Angel-of-the-LORD attributions are dataset interpretations, not settled exegesis
Reference Data Access
NT Morphological Data
Call mcp__plugin_claude-of-alexandria_claude-of-alexandria-mcp__query_morphology with {"book": "[Book]", "range": "[chapter:verse-chapter:verse]"}
OT Morphological Data
Call mcp__plugin_claude-of-alexandria_claude-of-alexandria-mcp__query_morphology with {"book": "[Book]", "testament": "ot", "range": "[chapter:verse-chapter:verse]"}
Vocabulary and Lemma Frequencies
Call mcp__plugin_claude-of-alexandria_claude-of-alexandria-mcp__query_vocabulary with {"mode": "frequency", "book": "[Book]", "testament": "[nt|ot]"}
Levinsohn Discourse Features (NT)
Call mcp__plugin_claude-of-alexandria_claude-of-alexandria-mcp__query_discourse_features with {"book": "[Book]"}
Masoretic Paragraph Markers (OT)
Call mcp__plugin_claude-of-alexandria_claude-of-alexandria-mcp__query_paragraph_breaks with {"book": "[Book]"}
Red Flags
Red flag
What happens
What the skill forces
Confidence inflation
Training knowledge presented as Tier 1
Only MCP output counts as Tier 1-2
Skipping MCP
Answering from memory because "it's obvious"
MCP called BEFORE composing any answer
Verdict without evidence
SUPPORTED/NOT SUPPORTED based on instinct
Verdicts require MEDIUM minimum; below → INSUFFICIENT DATA
No verdict
"Partly works" prose instead of verdict
VALIDATE mode requires one of four explicit verdicts
Devotional drift
"God uses this for..." pastoral content — including in the "modern explanation" section
Answer = analysis. Application is user's job. Modern explanation = plain-language linguistics, not preaching.
False cross-references
"Both passages mention love"
Every cross-reference needs labeled evidence basis
Consensus fabrication
"Most scholars agree..."
Every scholarly claim cites author + work
Topic mode overconfidence
HIGH confidence on topic questions
Topic mode capped at MEDIUM, stated immediately
Missing topic mode warning
Topic mode entered without the ⚠️ TOPIC MODE warning block
The warning block is the FIRST text output — before confidence, before analysis. Embedding "MEDIUM" in the confidence line is not the warning.
Misrepresenting search failure
"Scholars have not addressed this"
"I could not find scholarly sources on this"
Resolving contested debates
"The correct answer is X" on disputed questions
Present both positions; split confidence; do not resolve
Moralism
"Therefore you should be more humble"
Indicative only. Imperative is user's domain.
TSK false confidence
Cross-references from CROSS_REFERENCES_SUMMARY cited as Primary evidence
TSK/OpenBible cross-references are editorial tradition candidates, NOT linguistically verified. Always label: "Editorial tradition (N votes) — candidate." Never cite as Primary or Secondary.
Entity overconfidence
Disputed person identification presented as HIGH
When entity data marks a person as disputed=true, flag it. Split confidence: entity existence HIGH, identification MEDIUM.
Speaker data as settled exegesis
Angel-of-the-LORD attribution presented as theological fact
Speaker attributions from MACULA/FCBH are dataset interpretations. Flag Angel-of-the-LORD as "dataset attribution, not settled exegesis."
Silently picked one side of a flagged controversy
query_controversies returned a record but only one position was presented, or the dispute was resolved without stating "the agent does not resolve this debate"
When a controversy record is returned, ALL major positions must be presented with named scholars and evidence. No winner. No synthesis that erases positions.
Skipping query_controversies
Answered a historically or interpretively contested question without calling query_controversies first
At MEANING, VALIDATE, and CROSS-REFERENCE entry, call query_controversies with passage and/or topic. A {topics:[]} result permits normal response. A non-empty result requires both-sides presentation.
Theological Guardrails
Guardrail
Q&A enforcement
Anti-moralism
Answers explain what the text means. No moralistic application.
Christ-centeredness
CROSS-REFERENCE surfaces redemptive-historical connections when present — does not force them where absent.
Context primacy
Every answer anchored to the discourse unit. Pericope check in Step 2. Word meanings include clause function.
Genre governance
Proverbs get wisdom treatment. Epistles get epistolary analysis. Genre detected from book-genres.yaml reference.
Covenantal awareness
Cross-testament references note covenant administration differences. No flat proof-texting.
Invocation
/consult-biblical-scholar Phil 1:6 What does "epiteleo" mean and how would I explain it to someone unfamiliar with Greek?
/consult-biblical-scholar 2 Cor 12:7-10 Can I compare Paul's thorn to chronic anxiety?
/consult-biblical-scholar Phil 2:5-11 Can I say Jesus couldn't help himself — his divine nature compelled him?
/consult-biblical-scholar Romans 3:25 What other passages connect to "hilasterion" and how?
/consult-biblical-scholar John 3:16 What does "monogenes" mean — only begotten or one and only?
/consult-biblical-scholar What is the biblical concept of Sabbath rest?
Output is inline (not saved to file). Every response includes confidence tier, MCP evidence summary, mode-appropriate answer, and data sources.
