← Sermon ScribeCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Sermon Scribe
Snapshot Sep 30, 2026 · 23:15 UTC · version 1.1.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Reconstruct, expand, condense, or publish a Christian sermon from transcripts, notes, recordings already transcribed, or an existing sermon record. Use for faithful narrative sermon accounts and publication-ready sermon records; do not use to invent a new sermon or critique its theology.",
"included_files": [],
"name": "sermon-chronicle",
"skill_md_contents": "---\nname: sermon-chronicle\ndescription: Reconstruct, expand, condense, or publish a Christian sermon from transcripts, notes, recordings already transcribed, or an existing sermon record. Use for faithful narrative sermon accounts and publication-ready sermon records; do not use to invent a new sermon or critique its theology.\n---\n\n# Sermon Chronicle\n\nCreate a coherent pastoral record for readers who were not present while remaining answerable to the supplied sermon material.\n\nBefore writing, read [the shared fidelity and style standard](../../references/fidelity-and-style.md) and apply it throughout.\n\n## Interpret the request naturally\n\nInfer the intended mode from ordinary language; commands are optional aliases, not prerequisites.\n\n- **Reconstruct / WRITE:** turn fragmented source material into a complete narrative.\n- **Expand / EXPAND:** deepen clarity, continuity, and source-supported development without adding content.\n- **Condense / SUMMARISE:** create a shorter but still pastoral and theologically substantive account.\n- **Publish / PUBLISH:** edit the record for a church website, newsletter, archive, or ministry publication while retaining a narrative form.\n\nIf more than one source is supplied, treat all relevant files as the sermon evidence base. Do not ask for confirmation merely because a file was provided. If the requested mode or length is not stated, default to a full reconstruction proportionate to the source.\n\n## Reconstruct the sermon\n\n1. Identify the preacher's actual movement: opening, Scripture engagement, exposition, illustrations or testimony, application, closing appeal, and prayer where present.\n2. Separate transcription noise and verbal repetition from meaningful emphasis. Preserve repetitions that perform a pastoral or rhetorical function.\n3. Restore complete sentences, clear antecedents, natural transitions, and readable paragraphs.\n4. Preserve the preacher's order unless reordering is necessary for intelligibility and does not alter emphasis or causality.\n5. Make the result one connected sermon account, not an analytical outline or commentary on preaching technique.\n\n## Default full-record structure\n\nFor a full reconstruction or publication-ready record, use these Markdown headings in order:\n\n1. Title / Theme\n2. Scripture Basis\n3. Opening Reflection\n4. Main Exposition and Key Points\n5. Illustrations and Personal Testimonies\n6. Practical Applications\n7. Closing Appeal and Prayer\n\nWrite full paragraphs rather than bullets. A heading may state that the source contains no distinct material for that section, but do not fabricate content to fill it. If the source genuinely combines sections, preserve the required heading order while avoiding repetition. For a user-requested summary, excerpt, or house format, adapt the structure to the requested deliverable rather than forcing all seven headings.\n\nUse a source-supported title or a restrained descriptive title. Do not create a sensational or marketing-oriented title.\n\n## Deliver\n\nReturn the finished record directly. Add a short source note only when gaps, contradictions, or uncertain quotations materially affect reliability. Do not append a command menu, `HELP` reminder, or mandatory closing question.\n"
}SHA-256 of public snapshot: 79232dbbeeac6be155860a9666e883c19c7b109314f47f287b9b034634a248c8