[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CDZ0835BK4VYTFXB3NV2ZX":3,"skill-same:01M7CDZ0835BK4VYTFXB3NV2ZX":377},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CDZ0835BK4VYTFXB3NV2ZX","bulletin",null,"Prepare, render, verify, and approval-finalize a weekly worship bulletin in a church folder. Use when the user asks to build or prepare a bulletin, save weekly clergy assignments, change bulletin preferences, inspect bulletin history, or finalize a reviewed bulletin.","stephenfsetzer\u002Fhandbuilt-church-labs","stephenfsetzer","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227029240?v=4","01M7CDXGG2C4H151NXEJCT76SX","Stephen Setzer","01M7CDXGGP7A3YEHPBQHECHM1C",0,"MIT","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bulletin\ndescription: Prepare, render, verify, and approval-finalize a weekly worship bulletin in a church folder. Use when the user asks to build or prepare a bulletin, save weekly clergy assignments, change bulletin preferences, inspect bulletin history, or finalize a reviewed bulletin.\n---\n\n# Weekly Bulletin\n\nWork inside the church's private folder. For a Handbuilt production run, use\nthis skill's production interface instead of calling renderer scripts directly.\nThe pastor may choose a local skill, custom editing, or another tool, including\nafter starting this workflow. Follow that request without requiring plugin\napproval. Read [Workspace customization](..\u002F..\u002Fhandbook\u002Fworkspace-customization.md)\nfor edits beyond supported settings and handling existing reviewed files.\n\nRead [Worship text and source records](references\u002Fworship-text.md) when a\nprivate or locally formatted prayer or reading text is needed. Read\n[Source import and inventory](references\u002Fsource-inventory.md) when this\nweek's input draws on a bulletin imported during onboarding; check\n`validate_for_production` before relying on that import.\nRead [Service design and scoped bulletin decisions](references\u002Fservice-design.md)\nwhen resuming saved service work, adding a recurring service, changing a\nreusable part, or reviewing a scope or layout question.\n\nThe public production interface has four operations: `orient`, `produce`,\n`revise`, and `finalize`.\n\nBefore changing church-local `CLAUDE.md` or `AGENTS.md`, and when asked to\nrecover their earlier text, follow [Instruction recovery](..\u002F..\u002Fhandbook\u002Finstruction-recovery.md).\nPlugin updates preserve these files; never replace them with a newer scaffold.\n\n## 0. Confirm the bulletin runtime\n\nBefore interviewing the pastor or staging a bulletin, run the app-loaded\nadapter once to select and verify the workflow:\n\n```bash\n\"\u003Capp-loaded-plugin-root>\u002Fbin\u002Fhandbuilt-python\" \"\u003Capp-loaded-plugin-root>\u002Ftools\u002Fchurch_workflow.py\" \\\n  --church-folder \"\u003Cchurch-folder>\" start bulletin\n```\n\nThe launcher renders and checks a temporary sample PDF. If it does not report\n`ready`, stop before production and follow the reported repair detail in\n`handbook\u002Fruntime-setup.md`. Use `setup` for missing managed packages; repair\nnative tools or rendering libraries when those failed. Repeat `start bulletin`\nafter repair. Do not ask the pastor to manage packages or use global Python.\nPassing this computer check does not replace the actual bulletin's checks.\n\nRead the exact skill path returned by `start`. Use the returned `launcher`\nprefix, including its selected plugin root and managed Python, for every\n`orient`, `produce`, `revise`, and `finalize` operation in this task. Run\n`start` once per task and do not repeat it after reading the returned skill.\nFor a supporting script with no adapter operation, use the returned\n`runtime_python` and returned skill path, never an app-cache path.\nThe normal `church-folder\u002Fhandbuilt.py start bulletin` command remains valid\nfor a person checking the connection manually. If the connection is missing,\nrepair it through onboarding. A missing connection does not prevent the pastor\nfrom choosing another tool.\n\n## 1. Orient\n\nRun the operation with the exact prefix returned by `start`:\n\n```bash\n\u003Clauncher-prefix> bulletin orient --date \u003CYYYY-MM-DD>\n```\n\nUse the result to propose defaults from approved bulletin history and available\nmusic assets. History means an item appeared in an approved bulletin. Do not\nclaim it was sung, read, or announced during the service.\n\nVerify the lectionary day and selected citations against a published calendar.\nRecord each reading source with `label`, `location`, and `verified_on`.\n\n## 1a. Guide ongoing service design\n\nWhen the request concerns a saved service or reusable worship practice, follow\nthe service-design reference before resolving weekly input. Inspect the\ninstalled workflow's returned capabilities and state, including any selected\n`service.service_id`, `service.occurrence_id`, and catalog data it actually\nsupports. Use `--service-id \u003Cid>` with `orient` for a named service and\n`--occurrence-id \u003Cid>` when that service happens twice on one date. Recover the saved service, usual parts, pending dated work, and\nunresolved decisions before asking the pastor to repeat an answer.\n\nRecommend the closest existing service or reusable part first. Keep the\nrequested edit at the scope the pastor named: this occurrence, the recurring\nservice, or church defaults. If the request is ambiguous, ask one scope\nquestion before a shared write. Read the saved state back after an authorized\nchange and state what future services inherit. Use the scoped settings\ncommands in the service-design reference for recurring changes; keep dated\nexceptions in the bulletin input.\n\nDuring review, connect wording and layout recommendations to participation,\nincluding finding a response, following a direction, reading music, and\nhandling page turns. Use the rendered proof and source comparison. A passing\nrender does not establish readable music or complete content.\n\n## 2. Resolve the service\n\nRecover the service date, standing settings, known people, and existing weekly\nmaterial before asking for more. Use the saved layout without reopening that\nchoice unless the pastor requests a change. Present a short summary that the\nreturning pastor can correct.\n\nAn incomplete partial draft is not proof that a weekly choice is unknown.\nInspect existing packages for the same date, service, and occurrence before\nasking again. Describe which dated choices you recovered and let the pastor\ncorrect them. Do not silently carry another week's assignments, music, or\nannouncements into a new date.\n\nThe agent retrieves the appointed readings, collect, and proper preface from\nverified sources using the saved lectionary and worship practice. The pastor\nsupplies local decisions such as music, announcements, petitions, special\nservice changes, and unresolved assignments. Ask at most three focused\nquestions at a time, preferably one. Explain what the next answer enables.\nDo not hand the pastor a checklist of liturgical texts to gather when the\nagent can verify and retrieve them.\n\nIf the pastor asks only to prepare assignments or pauses before production,\nsave the dated work and stop at that boundary. Explain the sourcing you will\ndo when work resumes, then ask only for the next missing local decision. For\nexample: \"I have the clergy assignments. When we build the bulletin, I will\nverify the readings and prayers. Do you have this week's music selections?\"\n\nBefore resolving the weekly input, read the `worship_profile` path in\n`church.yaml` (normally `worship\u002Fprofile.yaml`). Present its standing\nworship choices, their source or tradition pack, and any unresolved values.\nResolve the profile through the worship-resolution module before constructing\nthe weekly bulletin input:\n\n```bash\n\u003Cruntime.python> \u003Cskill-dir>\u002Fscripts\u002Fworship_resolution.py \\\n  --church-folder \u003Cchurch-folder> --weekly-input \u003Cweekly-overrides.json>\n```\n\nIts result supplies context for review; human approval remains a separate step.\nIf the result is `needs_input`, inspect the listed reasons. Retrieve and check\nmissing public worship text when a reliable source is available, then save its\nprivate source copy and provenance. Ask the pastor for unresolved choices,\nconflicts, or local and licensed material that the agent cannot obtain.\nRerun resolution before producing.\nUse a recurring service's saved `default_variant` when present. Otherwise,\nthe weekly caller supplies `service.variant` as the configured variant id\nwhen a profile declares service variants. Carry forward an already confirmed\nchoice without asking again. Read back its exact name and\nconfirmation policy, then resolve the private order file. An unknown,\nunsafe, missing, cyclic, or service-plan-mismatched variant is `needs_input`\nwith an actionable reason. Never infer a variant from a date, denomination,\nhistory, or renderer default.\n\nFor an ordinary service, the caller must supply `service.variant: none` when\nvariants are configured. The resolved object records that explicit choice at\n`liturgy.service_variant`; selected variants also record their private order\nfile chain and confirmation policy at\n`liturgy.service_variant_provenance`.\n\nUse the [bundled Sunday library](references\u002Fsunday-library.md) before fetching\nstandard worship text. Standard BCP selections need no private source path or\npastor-supplied URL. Read only the chosen collect, preface, or psalm entry.\nA private override still requires its own verification. For Lutheran licensed\nmaterial, help prepare a reusable private source from the church's permitted\nmaterial rather than asking the pastor to build technical files.\n\nResolve weekly `liturgy` fields explicitly. Never infer a Eucharistic Prayer,\nLord's Prayer form, Prayers of the People form, or local communion welcome\nfrom denomination or history. Labs supplies `general-blessing` as the standing\nfallback. A church may select a private named blessing in its worship profile\nor for one week. Other missing required choices block production until\nresolved.\n\nStanding worship preferences are saved in `worship\u002Fprofile.yaml`. The profile\nsupports traditional, custom, or omitted doxology; a confirmed psalm format\nand response starting side; continuous or repeated prayer labels; and concise\nor source rubrics. A blank psalm format remains unresolved until the church\nchooses one. A custom doxology uses the private `sources.doxology` text path.\nThe optional standing `church.yaml.bulletin.doxology_music` entry uses the\nsame fields as a hymn block. Copy it to `service_music.doxology` only when a\nweekly input omits that slot. A weekly `service_music.doxology: null` means\nthere is no doxology music that week.\n\nComplete lyrics are private church content. Labs does not determine whether a\nchurch may print material it supplies and does not require a permission record.\nDerive `lyric_columns` from text length and proof results; it is a layout proof\nvalue that the agent determines during visual review. Copyrighted lyrics must never enter\nthe public Labs repository or its fixtures.\n\nThe weekly bulletin workflow stages `church.yaml.bulletin.footer` into the\ncompanion `brand.bulletin_footer`. It consumes\n`church.yaml.leadership` and carries\n`church.yaml.bulletin.include_serving_today` and\n`church.yaml.bulletin.serving_roles` into `options`, where the role list\nfilters the Serving Today section. It renders private lyrics supplied by the\nchurch without applying a Labs permission policy. The public repository\ncontains synthetic lyric fixtures only.\n\nKeep the distinction between standing setup and this week's service explicit.\nThe church profile may supply the reusable service book, prayer forms, roster,\nfooter, recurring role slots, and selected bulletin template. The weekly input\nsupplies the date, readings, hymns, preacher, celebrant, petitions,\nannouncements, and Serving Today assignments. Resolve a person from the\nmaintained `leadership.clergy_and_staff` roster only on one exact\ncase-insensitive role match, with a first-name shortcut only when it is unique\nafter printed titles are removed. Ambiguous or missing matches need a pastor's\nchoice. Never save a weekly assignment into the standing roster.\n\n`merge_back_page` is a weekly approval question, never an inferred default.\nWhen a merge is proposed, the result and receipt must show a mandatory\nvisual-review warning and the signature pages, sides, sheets, and blanks. The\npastor must explicitly approve that week's merge before finalization.\n\nRead [Weekly input](references\u002Fweekly-input.md) and its linked field schema\nbefore preparing the production JSON. Use those contracts rather than reading\nthe Python implementation to discover ordinary input fields. The input adds:\n\n- top-level `template`: `classic` or `modern`\n- a `source` record on each reading\n- music image paths relative to the church folder or its `music\u002F` directory\n- resolved `liturgy` values, including the worship profile reference and any\n  local licensed liturgy sources\n\nNever type a reading, a psalm, the collect, or the preface into the file, a\ncommand, or a message. Name each one and let the tool copy the words from\ntheir source, as [Weekly input](references\u002Fweekly-input.md#let-the-tool-copy-the-texts)\ndescribes. Retyped scripture can be stopped by the AI app's safeguards in the\nmiddle of the pastor's bulletin, and it risks a changed word.\n\nMissing music scans are allowed as a labeled title-only fallback. Unverified\nreadings and unresolved example text block production.\n\n## 3. Produce a review package\n\nInclude the church's provided logo on both Classic and Modern front pages. Read `brand.json`\nand use the existing local mark or banner. If onboarding recorded only a logo\nURL, the agent retrieves the confirmed image, saves it under the church's\nprivate `brand\u002F` folder, and replaces the rendering path in `logo.mark` or\n`logo.banner` with that local path. Keep source provenance in the church's\nonboarding notes. Do not ask the pastor to supply the same logo again when it\ncan be recovered. A missing or unreadable configured logo blocks production\nuntil repaired; a church with no provided logo may use its name alone.\nDuring visual review, check the logo on the sequential PDF's first page and\non the corresponding outer booklet cover, including legibility and proportions.\n\nSave the resolved input to a temporary JSON file, then run:\n\n```bash\n\u003Clauncher-prefix> bulletin produce --input \u003Cresolved-bulletin.json>\n```\n\nProduction renders the selected template, creates the 11x17 booklet, runs the\nautomated quality gate, stores artifacts in the dated week folder, and writes\na production receipt. A successful result is `ready_for_review`, not approved\nor print-ready.\n\nFor a supplied-bulletin reproduction, compare each source section with the\nrendered output before closeout. Check supplied prayer paragraphs and local\npetitions, music titles, lyrics, notation, credits, and recurring information.\nA field saved in JSON is not evidence that it printed. Inspect the PDFs and\ntheir extracted text. Recover an available supplied image before accepting a\nmissing-image fallback. Explain any unsupported content and obtain the\npastor's choice before deliberately omitting it; a receipt does not establish\ncontent completeness. Broad layout changes do not authorize removing words.\n\nProduction also runs the booklet print gate before imposition. The print mode\ncomes from `options.print_mode` (`booklet`, `duplex`, or `single`; `booklet`\nwhen unset), and `options.allow_blank_inside_cover` says whether page 2 may be\nleft blank on purpose. Both may be saved once as standing preferences under\n`bulletin` in `church.yaml`; a weekly option overrides them. In booklet mode\nthe page-by-page PDF must already be a multiple of 4 pages, with no padding\nblank and the back page last. No hymn or prayer may continue across a page\nturn, and the opening hymn prints whole. No line of a text said together\n(the Creed, the Lord's Prayer, a confession) may wrap, and no heading may sit\nat the foot of a page with its text overleaf. A missing font or picture blocks\nin every print mode.\nWhen a rule fails, production fits the bulletin with small, bounded changes: a\nblank inside cover, looser line spacing, slightly larger type, music at 95% to\n100%, or one section starting a new page. It never changes wording or order.\nLarger type is kept only when no said line wraps: a said text that would wrap\nstays at the theme's size, and one that still wraps prints its speaker label\nabove the text. A piece of music split over two pages moves onto one page when\nit fits at the church's smallest music scale or larger.\n\nTwo standing settings under `bulletin` in `church.yaml` bound fitting:\n`body_size` (for example `12pt`; fitting never sets body type above it, and\n13pt is the ceiling when unset) and `music_min_scale` (for example `0.85`; the\nsmallest a piece of music may print to stay on one page, 95% when unset).\n`orient` returns them as `print_settings`, and the receipt records them.\n\nShow the pastor the sequential PDF and booklet PDF, and explain any warnings.\nKeep the receipt for your own later steps; a pastor never needs to open it.\nBefore asking for approval, state these in plain words:\n\n- `fit_summary`, when it is not empty. It names every layout adjustment, for\n  example \"To fold into 16 pages, page 2 is left blank and line spacing is a\n  little looser.\" The receipt lists the same steps in `fit_adjustments`.\n- Each `page_fill_warning`: which pages are only partly full. These are\n  allowed but are worth a look.\n- Each entry in `open_items`: bracketed text that will print and looks like a\n  blank nobody filled in, such as `[Name of the person to remember]`. Its\n  `field`, when present, says where the words live. Ask the pastor to supply\n  the wording, then revise. If the brackets belong there, the pastor can say\n  so; see step 5. Verse numbers, markings such as `[Alleluia]`, and optional\n  words in the shipped liturgy are not open items.\n\nWhen production returns `blocked` with `booklet_fit_failed`, tell the pastor\nthe error's one sentence. The bulletin needs a change the pastor chooses, such\nas fewer words, a different hymn, or a shorter announcement. Do not hand-edit\nthe rendered HTML, force page breaks, or add blank pages to reach a page\ncount; a re-render erases hand edits, and blanks print in the wrong place.\n\nHuman review is required before finalization. Printing or sending requires\nseparate explicit authorization.\n\n## 4. Revise a review package\n\nIf review requests a change, keep the prior package explicit and revise it with\nthe fourth public operation:\n\n```bash\n\u003Clauncher-prefix> bulletin revise \\\n  --prior-run \u003Cprior-bulletin-production-receipt.json> \\\n  --input \u003Crevision-input.json>\n```\n\nThe prior receipt must be an exact path to an unapproved `ready_for_review`\npackage. The revision input may contain only the changed fields. The workflow\ndeep-merges it with the prior source-safe config, then renders a temporary\nstaged config. The saved `bulletin-config.json` retains church-relative music\nand private liturgy source paths for the next revision.\n\nA pastor naming a heading means the large line printed at the top of that\npart, not the small label beside it. To reword the psalm's heading, revise\n`readings.psalm.heading`.\n\nThe replacement is rendered and verified before the files the prior run made\nmove to a recoverable `.revisions\u002F` folder. Files the church or agent added to\nthe week folder (a README, a photo, a script) stay where they are; the result\nand receipt list them as `preserved_files`. A church file that sits exactly\nwhere the new package writes is archived too and named in a warning. The new receipt links the predecessor run,\nreceipt hash, archive location, and source-config digest. Repeating the same\nrevision is idempotent. An ordinary revision can never change an approved\npackage or an approved history entry; step 6 covers an error found after\napproval.\n\nLegacy version 1 receipts are read without modification. Staged music is\nrecovered only when exactly one matching private source can be verified. A\nmissing or ambiguous source blocks revision and requires fresh source paths.\n\n## 5. Finalize only after approval\n\nCreate approval JSON containing `production_run_id`, `approved_by`, and the\nreviewed artifact hashes from the production receipt. An optional `note` and\n`approved_at` may be included. If the receipt lists `open_items`, finalization\nis refused until each one is filled in by a revision or the pastor confirms it\nshould print as written. Record that confirmation by listing each item's exact\n`text` in `confirmed_open_items`. Never add it without asking the pastor. Then\nrun:\n\n```bash\n\u003Clauncher-prefix> bulletin finalize \\\n  --receipt \u003Cbulletin-production-receipt.json> --approval \u003Capproval.json>\n```\n\nFinalization verifies that reviewed artifacts have not changed, writes the\napproval receipt, and updates approved bulletin history. If review requests a\nchange, revise through a new production run rather than finalizing the old one.\n\n## 6. Correct an error found after approval\n\nWhen a pastor finds a mistake in an approved bulletin, make a correction. Use\nthis only when the pastor has asked to change the approved bulletin:\n\n```bash\n\u003Clauncher-prefix> bulletin revise --correct-approved \\\n  --prior-run \u003Capproved-bulletin-production-receipt.json> \\\n  --input \u003Cchanged-fields.json>\n```\n\nTell the pastor what happens, in these words:\n\n- The approved bulletin is kept exactly as it was, with its approval, under\n  `.revisions\u002F` beside the week's folder. The result's `corrects_approved`\n  gives its location.\n- The week's folder now holds a corrected bulletin to review. It is not final\n  yet. Until it is approved, approved history still names the earlier bulletin.\n- Review the corrected bulletin, then finalize it as in step 5. Further changes\n  before approval use an ordinary revision of the corrected bulletin.\n- The pastor decides whether to reprint or resend. Copies already handed out\n  do not change.\n\nWithout `--correct-approved`, a revision of an approved bulletin is refused.\n\n## Boundaries\n\n- Private church data and licensed music stay in the church folder.\n- Only approved receipts update history.\n- Keep local template adaptations in the church folder; installed plugin\n  edits may be lost on update. The stock renderer does not automatically load\n  local templates. Use the selected local workflow to apply and verify them.\n- Do not call a generated package print-ready before human approval.\n\nThe separate doxology setting applies to the Episcopal service plan. In the\nLutheran service plan, keep any doxology within the church's verified local\norder or Great Thanksgiving text so it is not printed twice.\n","# Weekly Bulletin\n\nWork inside the church's private folder. For a Handbuilt production run, use\nthis skill's production interface instead of calling renderer scripts directly.\nThe pastor may choose a local skill, custom editing, or another tool, including\nafter starting this workflow. Follow that request without requiring plugin\napproval. Read [Workspace customization](..\u002F..\u002Fhandbook\u002Fworkspace-customization.md)\nfor edits beyond supported settings and handling existing reviewed files.\n\nRead [Worship text and source records](references\u002Fworship-text.md) when a\nprivate or locally formatted prayer or reading text is needed. Read\n[Source import and inventory](references\u002Fsource-inventory.md) when this\nweek's input draws on a bulletin imported during onboarding; check\n`validate_for_production` before relying on that import.\nRead [Service design and scoped bulletin decisions](references\u002Fservice-design.md)\nwhen resuming saved service work, adding a recurring service, changing a\nreusable part, or reviewing a scope or layout question.\n\nThe public production interface has four operations: `orient`, `produce`,\n`revise`, and `finalize`.\n\nBefore changing church-local `CLAUDE.md` or `AGENTS.md`, and when asked to\nrecover their earlier text, follow [Instruction recovery](..\u002F..\u002Fhandbook\u002Finstruction-recovery.md).\nPlugin updates preserve these files; never replace them with a newer scaffold.\n\n## 0. Confirm the bulletin runtime\n\nBefore interviewing the pastor or staging a bulletin, run the app-loaded\nadapter once to select and verify the workflow:\n\n```bash\n\"\u003Capp-loaded-plugin-root>\u002Fbin\u002Fhandbuilt-python\" \"\u003Capp-loaded-plugin-root>\u002Ftools\u002Fchurch_workflow.py\" \\\n  --church-folder \"\u003Cchurch-folder>\" start bulletin\n```\n\nThe launcher renders and checks a temporary sample PDF. If it does not report\n`ready`, stop before production and follow the reported repair detail in\n`handbook\u002Fruntime-setup.md`. Use `setup` for missing managed packages; repair\nnative tools or rendering libraries when those failed. Repeat `start bulletin`\nafter repair. Do not ask the pastor to manage packages or use global Python.\nPassing this computer check does not replace the actual bulletin's checks.\n\nRead the exact skill path returned by `start`. Use the returned `launcher`\nprefix, including its selected plugin root and managed Python, for every\n`orient`, `produce`, `revise`, and `finalize` operation in this task. Run\n`start` once per task and do not repeat it after reading the returned skill.\nFor a supporting script with no adapter operation, use the returned\n`runtime_python` and returned skill path, never an app-cache path.\nThe normal `church-folder\u002Fhandbuilt.py start bulletin` command remains valid\nfor a person checking the connection manually. If the connection is missing,\nrepair it through onboarding. A missing connection does not prevent the pastor\nfrom choosing another tool.\n\n## 1. Orient\n\nRun the operation with the exact prefix returned by `start`:\n\n```bash\n\u003Clauncher-prefix> bulletin orient --date \u003CYYYY-MM-DD>\n```\n\nUse the result to propose defaults from approved bulletin history and available\nmusic assets. History means an item appeared in an approved bulletin. Do not\nclaim it was sung, read, or announced during the service.\n\nVerify the lectionary day and selected citations against a published calendar.\nRecord each reading source with `label`, `location`, and `verified_on`.\n\n## 1a. Guide ongoing service design\n\nWhen the request concerns a saved service or reusable worship practice, follow\nthe service-design reference before resolving weekly input. Inspect the\ninstalled workflow's returned capabilities and state, including any selected\n`service.service_id`, `service.occurrence_id`, and catalog data it actually\nsupports. Use `--service-id \u003Cid>` with `orient` for a named service and\n`--occurrence-id \u003Cid>` when that service happens twice on one date. Recover the saved service, usual parts, pending dated work, and\nunresolved decisions before asking the pastor to repeat an answer.\n\nRecommend the closest existing service or reusable part first. Keep the\nrequested edit at the scope the pastor named: this occurrence, the recurring\nservice, or church defaults. If the request is ambiguous, ask one scope\nquestion before a shared write. Read the saved state back after an authorized\nchange and state what future services inherit. Use the scoped settings\ncommands in the service-design reference for recurring changes; keep dated\nexceptions in the bulletin input.\n\nDuring review, connect wording and layout recommendations to participation,\nincluding finding a response, following a direction, reading music, and\nhandling page turns. Use the rendered proof and source comparison. A passing\nrender does not establish readable music or complete content.\n\n## 2. Resolve the service\n\nRecover the service date, standing settings, known people, and existing weekly\nmaterial before asking for more. Use the saved layout without reopening that\nchoice unless the pastor requests a change. Present a short summary that the\nreturning pastor can correct.\n\nAn incomplete partial draft is not proof that a weekly choice is unknown.\nInspect existing packages for the same date, service, and occurrence before\nasking again. Describe which dated choices you recovered and let the pastor\ncorrect them. Do not silently carry another week's assignments, music, or\nannouncements into a new date.\n\nThe agent retrieves the appointed readings, collect, and proper preface from\nverified sources using the saved lectionary and worship practice. The pastor\nsupplies local decisions such as music, announcements, petitions, special\nservice changes, and unresolved assignments. Ask at most three focused\nquestions at a time, preferably one. Explain what the next answer enables.\nDo not hand the pastor a checklist of liturgical texts to gather when the\nagent can verify and retrieve them.\n\nIf the pastor asks only to prepare assignments or pauses before production,\nsave the dated work and stop at that boundary. Explain the sourcing you will\ndo when work resumes, then ask only for the next missing local decision. For\nexample: \"I have the clergy assignments. When we build the bulletin, I will\nverify the readings and prayers. Do you have this week's music selections?\"\n\nBefore resolving the weekly input, read the `worship_profile` path in\n`church.yaml` (normally `worship\u002Fprofile.yaml`). Present its standing\nworship choices, their source or tradition pack, and any unresolved values.\nResolve the profile through the worship-resolution module before constructing\nthe weekly bulletin input:\n\n```bash\n\u003Cruntime.python> \u003Cskill-dir>\u002Fscripts\u002Fworship_resolution.py \\\n  --church-folder \u003Cchurch-folder> --weekly-input \u003Cweekly-overrides.json>\n```\n\nIts result supplies context for review; human approval remains a separate step.\nIf the result is `needs_input`, inspect the listed reasons. Retrieve and check\nmissing public worship text when a reliable source is available, then save its\nprivate source copy and provenance. Ask the pastor for unresolved choices,\nconflicts, or local and licensed material that the agent cannot obtain.\nRerun resolution before producing.\nUse a recurring service's saved `default_variant` when present. Otherwise,\nthe weekly caller supplies `service.variant` as the configured variant id\nwhen a profile declares service variants. Carry forward an already confirmed\nchoice without asking again. Read back its exact name and\nconfirmation policy, then resolve the private order file. An unknown,\nunsafe, missing, cyclic, or service-plan-mismatched variant is `needs_input`\nwith an actionable reason. Never infer a variant from a date, denomination,\nhistory, or renderer default.\n\nFor an ordinary service, the caller must supply `service.variant: none` when\nvariants are configured. The resolved object records that explicit choice at\n`liturgy.service_variant`; selected variants also record their private order\nfile chain and confirmation policy at\n`liturgy.service_variant_provenance`.\n\nUse the [bundled Sunday library](references\u002Fsunday-library.md) before fetching\nstandard worship text. Standard BCP selections need no private source path or\npastor-supplied URL. Read only the chosen collect, preface, or psalm entry.\nA private override still requires its own verification. For Lutheran licensed\nmaterial, help prepare a reusable private source from the church's permitted\nmaterial rather than asking the pastor to build technical files.\n\nResolve weekly `liturgy` fields explicitly. Never infer a Eucharistic Prayer,\nLord's Prayer form, Prayers of the People form, or local communion welcome\nfrom denomination or history. Labs supplies `general-blessing` as the standing\nfallback. A church may select a private named blessing in its worship profile\nor for one week. Other missing required choices block production until\nresolved.\n\nStanding worship preferences are saved in `worship\u002Fprofile.yaml`. The profile\nsupports traditional, custom, or omitted doxology; a confirmed psalm format\nand response starting side; continuous or repeated prayer labels; and concise\nor source rubrics. A blank psalm format remains unresolved until the church\nchooses one. A custom doxology uses the private `sources.doxology` text path.\nThe optional standing `church.yaml.bulletin.doxology_music` entry uses the\nsame fields as a hymn block. Copy it to `service_music.doxology` only when a\nweekly input omits that slot. A weekly `service_music.doxology: null` means\nthere is no doxology music that week.\n\nComplete lyrics are private church content. Labs does not determine whether a\nchurch may print material it supplies and does not require a permission record.\nDerive `lyric_columns` from text length and proof results; it is a layout proof\nvalue that the agent determines during visual review. Copyrighted lyrics must never enter\nthe public Labs repository or its fixtures.\n\nThe weekly bulletin workflow stages `church.yaml.bulletin.footer` into the\ncompanion `brand.bulletin_footer`. It consumes\n`church.yaml.leadership` and carries\n`church.yaml.bulletin.include_serving_today` and\n`church.yaml.bulletin.serving_roles` into `options`, where the role list\nfilters the Serving Today section. It renders private lyrics supplied by the\nchurch without applying a Labs permission policy. The public repository\ncontains synthetic lyric fixtures only.\n\nKeep the distinction between standing setup and this week's service explicit.\nThe church profile may supply the reusable service book, prayer forms, roster,\nfooter, recurring role slots, and selected bulletin template. The weekly input\nsupplies the date, readings, hymns, preacher, celebrant, petitions,\nannouncements, and Serving Today assignments. Resolve a person from the\nmaintained `leadership.clergy_and_staff` roster only on one exact\ncase-insensitive role match, with a first-name shortcut only when it is unique\nafter printed titles are removed. Ambiguous or missing matches need a pastor's\nchoice. Never save a weekly assignment into the standing roster.\n\n`merge_back_page` is a weekly approval question, never an inferred default.\nWhen a merge is proposed, the result and receipt must show a mandatory\nvisual-review warning and the signature pages, sides, sheets, and blanks. The\npastor must explicitly approve that week's merge before finalization.\n\nRead [Weekly input](references\u002Fweekly-input.md) and its linked field schema\nbefore preparing the production JSON. Use those contracts rather than reading\nthe Python implementation to discover ordinary input fields. The input adds:\n\n- top-level `template`: `classic` or `modern`\n- a `source` record on each reading\n- music image paths relative to the church folder or its `music\u002F` directory\n- resolved `liturgy` values, including the worship profile reference and any\n  local licensed liturgy sources\n\nNever type a reading, a psalm, the collect, or the preface into the file, a\ncommand, or a message. Name each one and let the tool copy the words from\ntheir source, as [Weekly input](references\u002Fweekly-input.md#let-the-tool-copy-the-texts)\ndescribes. Retyped scripture can be stopped by the AI app's safeguards in the\nmiddle of the pastor's bulletin, and it risks a changed word.\n\nMissing music scans are allowed as a labeled title-only fallback. Unverified\nreadings and unresolved example text block production.\n\n## 3. Produce a review package\n\nInclude the church's provided logo on both Classic and Modern front pages. Read `brand.json`\nand use the existing local mark or banner. If onboarding recorded only a logo\nURL, the agent retrieves the confirmed image, saves it under the church's\nprivate `brand\u002F` folder, and replaces the rendering path in `logo.mark` or\n`logo.banner` with that local path. Keep source provenance in the church's\nonboarding notes. Do not ask the pastor to supply the same logo again when it\ncan be recovered. A missing or unreadable configured logo blocks production\nuntil repaired; a church with no provided logo may use its name alone.\nDuring visual review, check the logo on the sequential PDF's first page and\non the corresponding outer booklet cover, including legibility and proportions.\n\nSave the resolved input to a temporary JSON file, then run:\n\n```bash\n\u003Clauncher-prefix> bulletin produce --input \u003Cresolved-bulletin.json>\n```\n\nProduction renders the selected template, creates the 11x17 booklet, runs the\nautomated quality gate, stores artifacts in the dated week folder, and writes\na production receipt. A successful result is `ready_for_review`, not approved\nor print-ready.\n\nFor a supplied-bulletin reproduction, compare each source section with the\nrendered output before closeout. Check supplied prayer paragraphs and local\npetitions, music titles, lyrics, notation, credits, and recurring information.\nA field saved in JSON is not evidence that it printed. Inspect the PDFs and\ntheir extracted text. Recover an available supplied image before accepting a\nmissing-image fallback. Explain any unsupported content and obtain the\npastor's choice before deliberately omitting it; a receipt does not establish\ncontent completeness. Broad layout changes do not authorize removing words.\n\nProduction also runs the booklet print gate before imposition. The print mode\ncomes from `options.print_mode` (`booklet`, `duplex`, or `single`; `booklet`\nwhen unset), and `options.allow_blank_inside_cover` says whether page 2 may be\nleft blank on purpose. Both may be saved once as standing preferences under\n`bulletin` in `church.yaml`; a weekly option overrides them. In booklet mode\nthe page-by-page PDF must already be a multiple of 4 pages, with no padding\nblank and the back page last. No hymn or prayer may continue across a page\nturn, and the opening hymn prints whole. No line of a text said together\n(the Creed, the Lord's Prayer, a confession) may wrap, and no heading may sit\nat the foot of a page with its text overleaf. A missing font or picture blocks\nin every print mode.\nWhen a rule fails, production fits the bulletin with small, bounded changes: a\nblank inside cover, looser line spacing, slightly larger type, music at 95% to\n100%, or one section starting a new page. It never changes wording or order.\nLarger type is kept only when no said line wraps: a said text that would wrap\nstays at the theme's size, and one that still wraps prints its speaker label\nabove the text. A piece of music split over two pages moves onto one page when\nit fits at the church's smallest music scale or larger.\n\nTwo standing settings under `bulletin` in `church.yaml` bound fitting:\n`body_size` (for example `12pt`; fitting never sets body type above it, and\n13pt is the ceiling when unset) and `music_min_scale` (for example `0.85`; the\nsmallest a piece of music may print to stay on one page, 95% when unset).\n`orient` returns them as `print_settings`, and the receipt records them.\n\nShow the pastor the sequential PDF and booklet PDF, and explain any warnings.\nKeep the receipt for your own later steps; a pastor never needs to open it.\nBefore asking for approval, state these in plain words:\n\n- `fit_summary`, when it is not empty. It names every layout adjustment, for\n  example \"To fold into 16 pages, page 2 is left blank and line spacing is a\n  little looser.\" The receipt lists the same steps in `fit_adjustments`.\n- Each `page_fill_warning`: which pages are only partly full. These are\n  allowed but are worth a look.\n- Each entry in `open_items`: bracketed text that will print and looks like a\n  blank nobody filled in, such as `[Name of the person to remember]`. Its\n  `field`, when present, says where the words live. Ask the pastor to supply\n  the wording, then revise. If the brackets belong there, the pastor can say\n  so; see step 5. Verse numbers, markings such as `[Alleluia]`, and optional\n  words in the shipped liturgy are not open items.\n\nWhen production returns `blocked` with `booklet_fit_failed`, tell the pastor\nthe error's one sentence. The bulletin needs a change the pastor chooses, such\nas fewer words, a different hymn, or a shorter announcement. Do not hand-edit\nthe rendered HTML, force page breaks, or add blank pages to reach a page\ncount; a re-render erases hand edits, and blanks print in the wrong place.\n\nHuman review is required before finalization. Printing or sending requires\nseparate explicit authorization.\n\n## 4. Revise a review package\n\nIf review requests a change, keep the prior package explicit and revise it with\nthe fourth public operation:\n\n```bash\n\u003Clauncher-prefix> bulletin revise \\\n  --prior-run \u003Cprior-bulletin-production-receipt.json> \\\n  --input \u003Crevision-input.json>\n```\n\nThe prior receipt must be an exact path to an unapproved `ready_for_review`\npackage. The revision input may contain only the changed fields. The workflow\ndeep-merges it with the prior source-safe config, then renders a temporary\nstaged config. The saved `bulletin-config.json` retains church-relative music\nand private liturgy source paths for the next revision.\n\nA pastor naming a heading means the large line printed at the top of that\npart, not the small label beside it. To reword the psalm's heading, revise\n`readings.psalm.heading`.\n\nThe replacement is rendered and verified before the files the prior run made\nmove to a recoverable `.revisions\u002F` folder. Files the church or agent added to\nthe week folder (a README, a photo, a script) stay where they are; the result\nand receipt list them as `preserved_files`. A church file that sits exactly\nwhere the new package writes is archived too and named in a warning. The new receipt links the predecessor run,\nreceipt hash, archive location, and source-config digest. Repeating the same\nrevision is idempotent. An ordinary revision can never change an approved\npackage or an approved history entry; step 6 covers an error found after\napproval.\n\nLegacy version 1 receipts are read without modification. Staged music is\nrecovered only when exactly one matching private source can be verified. A\nmissing or ambiguous source blocks revision and requires fresh source paths.\n\n## 5. Finalize only after approval\n\nCreate approval JSON containing `production_run_id`, `approved_by`, and the\nreviewed artifact hashes from the production receipt. An optional `note` and\n`approved_at` may be included. If the receipt lists `open_items`, finalization\nis refused until each one is filled in by a revision or the pastor confirms it\nshould print as written. Record that confirmation by listing each item's exact\n`text` in `confirmed_open_items`. Never add it without asking the pastor. Then\nrun:\n\n```bash\n\u003Clauncher-prefix> bulletin finalize \\\n  --receipt \u003Cbulletin-production-receipt.json> --approval \u003Capproval.json>\n```\n\nFinalization verifies that reviewed artifacts have not changed, writes the\napproval receipt, and updates approved bulletin history. If review requests a\nchange, revise through a new production run rather than finalizing the old one.\n\n## 6. Correct an error found after approval\n\nWhen a pastor finds a mistake in an approved bulletin, make a correction. Use\nthis only when the pastor has asked to change the approved bulletin:\n\n```bash\n\u003Clauncher-prefix> bulletin revise --correct-approved \\\n  --prior-run \u003Capproved-bulletin-production-receipt.json> \\\n  --input \u003Cchanged-fields.json>\n```\n\nTell the pastor what happens, in these words:\n\n- The approved bulletin is kept exactly as it was, with its approval, under\n  `.revisions\u002F` beside the week's folder. The result's `corrects_approved`\n  gives its location.\n- The week's folder now holds a corrected bulletin to review. It is not final\n  yet. Until it is approved, approved history still names the earlier bulletin.\n- Review the corrected bulletin, then finalize it as in step 5. Further changes\n  before approval use an ordinary revision of the corrected bulletin.\n- The pastor decides whether to reprint or resend. Copies already handed out\n  do not change.\n\nWithout `--correct-approved`, a revision of an approved bulletin is refused.\n\n## Boundaries\n\n- Private church data and licensed music stay in the church folder.\n- Only approved receipts update history.\n- Keep local template adaptations in the church folder; installed plugin\n  edits may be lost on update. The stock renderer does not automatically load\n  local templates. Use the selected local workflow to apply and verify them.\n- Do not call a generated package print-ready before human approval.\n\nThe separate doxology setting applies to the Episcopal service plan. In the\nLutheran service plan, keep any doxology within the church's verified local\norder or Great Thanksgiving text so it is not printed twice.\n",{"name":5,"description":7},"main","c32b7366e6c4275e4ee70c18fd7b630d56a6ed8b","skills\u002Fbulletin","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs","https:\u002F\u002Fgethandbuilt.com\u002F","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer","2026-11-14 07:10:08",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add stephenfsetzer\u002Fhandbuilt-church-labs --skill bulletin",{"tool":37,"command":38},"bunx","bunx skills add stephenfsetzer\u002Fhandbuilt-church-labs --skill bulletin",{"tool":40,"command":41},"pnpm","pnpm dlx skills add stephenfsetzer\u002Fhandbuilt-church-labs --skill bulletin","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002FSKILL.md",true,[45,51,55,59,63,69,73,77,81,85,89,93,97,101,105,111,115,118,121,124,128,132,135,138,142,146,149,152,155,159,163,167,171,175,179,183,187,191,195,199,203,207,211,215,219,223,227,231,235,239,243,247,251,255,259,263,267,271,275,279,283,287,291,297,301,305,309,313,317,321,325,329,333,337,341,345,349,353,357,361,365,369,373],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"__init__.py","SCRIPT","脚本",32,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002F__init__.py",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"bulletin_production\u002F__init__.py",157,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fbulletin_production\u002F__init__.py",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"bulletin_production\u002Finterface.py",169449,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fbulletin_production\u002Finterface.py",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"liturgy_sources.py",5337,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fliturgy_sources.py",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fservice-design.md","REFERENCE","参考文档",8483,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Freferences\u002Fservice-design.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fsource-inventory.md",6124,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Freferences\u002Fsource-inventory.md",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fsunday-library.md",6440,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Freferences\u002Fsunday-library.md",{"path":78,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fweekly-input.md",9848,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Freferences\u002Fweekly-input.md",{"path":82,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fworship-text.md",4420,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Freferences\u002Fworship-text.md",{"path":86,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":87,"sourceHtmlUrl":88},"renderer\u002Fbrand_type.py",5678,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fbrand_type.py",{"path":90,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":91,"sourceHtmlUrl":92},"renderer\u002Fbulletin_history.py",6136,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fbulletin_history.py",{"path":94,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":95,"sourceHtmlUrl":96},"renderer\u002Fbulletin-config-schema.json",13140,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fbulletin-config-schema.json",{"path":98,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":99,"sourceHtmlUrl":100},"renderer\u002Fexample-brand.json",782,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fexample-brand.json",{"path":102,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":103,"sourceHtmlUrl":104},"renderer\u002Fexample-bulletin-config.json",2750,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fexample-bulletin-config.json",{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"renderer\u002Ffonts\u002FEBGaramond-Bold.ttf","ASSET","资产文件",851176,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FEBGaramond-Bold.ttf",{"path":112,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":113,"sourceHtmlUrl":114},"renderer\u002Ffonts\u002FEBGaramond-Italic.ttf",754468,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FEBGaramond-Italic.ttf",{"path":116,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":117},"renderer\u002Ffonts\u002FEBGaramond-Regular.ttf","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FEBGaramond-Regular.ttf",{"path":119,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":120},"renderer\u002Ffonts\u002FEBGaramond-SemiBold.ttf","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FEBGaramond-SemiBold.ttf",{"path":122,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":113,"sourceHtmlUrl":123},"renderer\u002Ffonts\u002FEBGaramond-SemiBoldItalic.ttf","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FEBGaramond-SemiBoldItalic.ttf",{"path":125,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":126,"sourceHtmlUrl":127},"renderer\u002Ffonts\u002FSourceSans3-Bold.ttf",646340,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FSourceSans3-Bold.ttf",{"path":129,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":130,"sourceHtmlUrl":131},"renderer\u002Ffonts\u002FSourceSans3-Italic.ttf",395372,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FSourceSans3-Italic.ttf",{"path":133,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":126,"sourceHtmlUrl":134},"renderer\u002Ffonts\u002FSourceSans3-Regular.ttf","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FSourceSans3-Regular.ttf",{"path":136,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":126,"sourceHtmlUrl":137},"renderer\u002Ffonts\u002FSourceSans3-SemiBold.ttf","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FSourceSans3-SemiBold.ttf",{"path":139,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":140,"sourceHtmlUrl":141},"renderer\u002Ffonts\u002FSourceSerif4-Bold.ttf",1209508,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FSourceSerif4-Bold.ttf",{"path":143,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":144,"sourceHtmlUrl":145},"renderer\u002Ffonts\u002FSourceSerif4-Italic.ttf",855432,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FSourceSerif4-Italic.ttf",{"path":147,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":140,"sourceHtmlUrl":148},"renderer\u002Ffonts\u002FSourceSerif4-Regular.ttf","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FSourceSerif4-Regular.ttf",{"path":150,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":140,"sourceHtmlUrl":151},"renderer\u002Ffonts\u002FSourceSerif4-SemiBold.ttf","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FSourceSerif4-SemiBold.ttf",{"path":153,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":144,"sourceHtmlUrl":154},"renderer\u002Ffonts\u002FSourceSerif4-SemiBoldItalic.ttf","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Ffonts\u002FSourceSerif4-SemiBoldItalic.ttf",{"path":156,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":157,"sourceHtmlUrl":158},"renderer\u002Fimpose_booklet.py",2302,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fimpose_booklet.py",{"path":160,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":161,"sourceHtmlUrl":162},"renderer\u002Fliturgy\u002Fabsolution.md",525,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fabsolution.md",{"path":164,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":165,"sourceHtmlUrl":166},"renderer\u002Fliturgy\u002Fbreaking-of-bread-lent.md",1135,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fbreaking-of-bread-lent.md",{"path":168,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":169,"sourceHtmlUrl":170},"renderer\u002Fliturgy\u002Fbreaking-of-bread.md",1279,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fbreaking-of-bread.md",{"path":172,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":173,"sourceHtmlUrl":174},"renderer\u002Fliturgy\u002Fcollect-for-purity.md",467,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fcollect-for-purity.md",{"path":176,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":177,"sourceHtmlUrl":178},"renderer\u002Fliturgy\u002Fconfession-of-sin.md",1136,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fconfession-of-sin.md",{"path":180,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":181,"sourceHtmlUrl":182},"renderer\u002Fliturgy\u002Fdismissal.md",428,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fdismissal.md",{"path":184,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":185,"sourceHtmlUrl":186},"renderer\u002Fliturgy\u002Fdoxology.md",399,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fdoxology.md",{"path":188,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":189,"sourceHtmlUrl":190},"renderer\u002Fliturgy\u002Feucharistic-prayer-a-full.md",3588,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Feucharistic-prayer-a-full.md",{"path":192,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":193,"sourceHtmlUrl":194},"renderer\u002Fliturgy\u002Feucharistic-prayer-a.md",1994,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Feucharistic-prayer-a.md",{"path":196,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":197,"sourceHtmlUrl":198},"renderer\u002Fliturgy\u002Feucharistic-prayer-b-full.md",4351,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Feucharistic-prayer-b-full.md",{"path":200,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":201,"sourceHtmlUrl":202},"renderer\u002Fliturgy\u002Feucharistic-prayer-b.md",1977,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Feucharistic-prayer-b.md",{"path":204,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":205,"sourceHtmlUrl":206},"renderer\u002Fliturgy\u002Feucharistic-prayer-c-full.md",4131,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Feucharistic-prayer-c-full.md",{"path":208,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":209,"sourceHtmlUrl":210},"renderer\u002Fliturgy\u002Feucharistic-prayer-c.md",3070,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Feucharistic-prayer-c.md",{"path":212,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":213,"sourceHtmlUrl":214},"renderer\u002Fliturgy\u002Feucharistic-prayer-d-full.md",6026,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Feucharistic-prayer-d-full.md",{"path":216,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":217,"sourceHtmlUrl":218},"renderer\u002Fliturgy\u002Feucharistic-prayer-d.md",2003,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Feucharistic-prayer-d.md",{"path":220,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":221,"sourceHtmlUrl":222},"renderer\u002Fliturgy\u002Fgeneral-blessing.md",483,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fgeneral-blessing.md",{"path":224,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":225,"sourceHtmlUrl":226},"renderer\u002Fliturgy\u002Flords-prayer-contemporary.md",753,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Flords-prayer-contemporary.md",{"path":228,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":229,"sourceHtmlUrl":230},"renderer\u002Fliturgy\u002Flords-prayer-traditional.md",792,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Flords-prayer-traditional.md",{"path":232,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":233,"sourceHtmlUrl":234},"renderer\u002Fliturgy\u002Fnicene-creed.md",1714,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fnicene-creed.md",{"path":236,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":237,"sourceHtmlUrl":238},"renderer\u002Fliturgy\u002Fopening-acclamation-easter.md",380,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fopening-acclamation-easter.md",{"path":240,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":241,"sourceHtmlUrl":242},"renderer\u002Fliturgy\u002Fopening-acclamation-lent.md",359,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fopening-acclamation-lent.md",{"path":244,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":245,"sourceHtmlUrl":246},"renderer\u002Fliturgy\u002Fopening-acclamation.md",453,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fopening-acclamation.md",{"path":248,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":249,"sourceHtmlUrl":250},"renderer\u002Fliturgy\u002Fpeace.md",350,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fpeace.md",{"path":252,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":253,"sourceHtmlUrl":254},"renderer\u002Fliturgy\u002Fpost-communion-prayer.md",802,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fpost-communion-prayer.md",{"path":256,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":257,"sourceHtmlUrl":258},"renderer\u002Fliturgy\u002Fprayers-of-the-people-i.md",2763,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fprayers-of-the-people-i.md",{"path":260,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":261,"sourceHtmlUrl":262},"renderer\u002Fliturgy\u002Fprayers-of-the-people-ii.md",1447,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fprayers-of-the-people-ii.md",{"path":264,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":265,"sourceHtmlUrl":266},"renderer\u002Fliturgy\u002Fprayers-of-the-people-iv.md",1635,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fprayers-of-the-people-iv.md",{"path":268,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":269,"sourceHtmlUrl":270},"renderer\u002Fliturgy\u002Fprayers-of-the-people-v.md",3707,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fprayers-of-the-people-v.md",{"path":272,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":273,"sourceHtmlUrl":274},"renderer\u002Fliturgy\u002Fprayers-of-the-people-vi.md",2251,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fprayers-of-the-people-vi.md",{"path":276,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":277,"sourceHtmlUrl":278},"renderer\u002Fliturgy\u002Fprayers-of-the-people.md",1397,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fliturgy\u002Fprayers-of-the-people.md",{"path":280,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":281,"sourceHtmlUrl":282},"renderer\u002Fprint_layout.py",71094,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fprint_layout.py",{"path":284,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":285,"sourceHtmlUrl":286},"renderer\u002FREADME.md",3873,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002FREADME.md",{"path":288,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":289,"sourceHtmlUrl":290},"renderer\u002Frender_bulletin.py",96915,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Frender_bulletin.py",{"path":292,"resourceType":293,"resourceTypeDesc":294,"sizeBytes":295,"sourceHtmlUrl":296},"renderer\u002Fthemes\u002Fbase.css","OTHER","其他",10043,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fthemes\u002Fbase.css",{"path":298,"resourceType":293,"resourceTypeDesc":294,"sizeBytes":299,"sourceHtmlUrl":300},"renderer\u002Fthemes\u002Fclassic.css",2241,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fthemes\u002Fclassic.css",{"path":302,"resourceType":293,"resourceTypeDesc":294,"sizeBytes":303,"sourceHtmlUrl":304},"renderer\u002Fthemes\u002Fmodern.css",4927,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Frenderer\u002Fthemes\u002Fmodern.css",{"path":306,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":307,"sourceHtmlUrl":308},"resources\u002Fbcp1979\u002Fmanifest.json",6624,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fresources\u002Fbcp1979\u002Fmanifest.json",{"path":310,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":311,"sourceHtmlUrl":312},"resources\u002Fbcp1979\u002FREADME.md",2396,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fresources\u002Fbcp1979\u002FREADME.md",{"path":314,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":315,"sourceHtmlUrl":316},"resources\u002Fbcp1979\u002Fsunday.json",577744,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fresources\u002Fbcp1979\u002Fsunday.json",{"path":318,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":319,"sourceHtmlUrl":320},"scripts\u002Fbulletin_production.py",2344,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fscripts\u002Fbulletin_production.py",{"path":322,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":323,"sourceHtmlUrl":324},"scripts\u002Fliturgy_source.py",1357,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fscripts\u002Fliturgy_source.py",{"path":326,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":327,"sourceHtmlUrl":328},"scripts\u002Fsunday_library.py",1294,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fscripts\u002Fsunday_library.py",{"path":330,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":331,"sourceHtmlUrl":332},"scripts\u002Fweekly_texts.py",1278,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fscripts\u002Fweekly_texts.py",{"path":334,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":335,"sourceHtmlUrl":336},"scripts\u002Fworship_resolution.py",1177,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fscripts\u002Fworship_resolution.py",{"path":338,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":339,"sourceHtmlUrl":340},"service_catalog.py",16471,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fservice_catalog.py",{"path":342,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":343,"sourceHtmlUrl":344},"source_inventory.py",48260,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fsource_inventory.py",{"path":346,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":347,"sourceHtmlUrl":348},"sunday_library.py",5763,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fsunday_library.py",{"path":350,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":351,"sourceHtmlUrl":352},"traditions\u002Fcatalog.yaml",210,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Ftraditions\u002Fcatalog.yaml",{"path":354,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":355,"sourceHtmlUrl":356},"traditions\u002Fepiscopal-bcp-rite-ii.yaml",1263,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Ftraditions\u002Fepiscopal-bcp-rite-ii.yaml",{"path":358,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":359,"sourceHtmlUrl":360},"traditions\u002Flutheran-elca-elw.yaml",1025,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Ftraditions\u002Flutheran-elca-elw.yaml",{"path":362,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":363,"sourceHtmlUrl":364},"traditions\u002Flutheran-lcms-lsb.yaml",1029,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Ftraditions\u002Flutheran-lcms-lsb.yaml",{"path":366,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":367,"sourceHtmlUrl":368},"weekly_texts.py",11562,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fweekly_texts.py",{"path":370,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":371,"sourceHtmlUrl":372},"worship_resolution.py",49173,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fworship_resolution.py",{"path":374,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":375,"sourceHtmlUrl":376},"worship\u002FREADME.md",4824,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002Fworship\u002FREADME.md",[378,385,392,399,406,413],{"skillNo":379,"name":380,"nameZh":6,"description":381,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":382,"categories":383,"keywords":384,"publishedAt":19},"01M7CDZRDP4PEMXMCJB7M17N50","sermon-video","Prepare a sermon video, parish thumbnail, captions, and playable review page from a full service on YouTube, Vimeo, another public embedded player, or a local recording. Use for clipping and preparing recorded sermons, not writing sermons.","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fsermon-video\u002FSKILL.md",[],[],{"skillNo":386,"name":387,"nameZh":6,"description":388,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":389,"categories":390,"keywords":391,"publishedAt":19},"01M7CDZNBDRWQ6EWCQKGMHV6DT","sermon-research","Run or resume the portable sermon research workflow from passage selection through verified readings and a cited research brief. Use when a pastor asks for sermon research or when a weekly sermon research automation invokes the workflow.","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fsermon-research\u002FSKILL.md",[],[],{"skillNo":393,"name":394,"nameZh":6,"description":395,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":396,"categories":397,"keywords":398,"publishedAt":19},"01M7CDZH1QFK9TQTSRNV75JVGK","sermon-reflection","Help a pastor turn sermon research into their own sermon. Draws out the pastor's thinking one question at a time, opens a page for them to write or speak their reflections for as long as they need, then lightly edits their writing into a sermon that still sounds like them, with an optional large-type speaker's copy. Use when a pastor finishes research and says they are ready to reflect, wants to start writing, asks for help with their sermon draft, or asks for a speaker's copy.","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fsermon-reflection\u002FSKILL.md",[],[],{"skillNo":400,"name":401,"nameZh":6,"description":402,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":403,"categories":404,"keywords":405,"publishedAt":19},"01M7CDZBWD14TBP0S60F9P7FW2","onboarding","Set up my Church Command Center: create or resume a private church folder through website discovery and worship setup. Use when a pastor asks to set up their Church Command Center or church workspace, get started, run onboarding, check saved setup, or update standing church preferences.","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002FSKILL.md",[],[],{"skillNo":407,"name":408,"nameZh":6,"description":409,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":410,"categories":411,"keywords":412,"publishedAt":19},"01M7CDZ83WR65E85R116SM163W","finance-report","Build the monthly finance report for the vestry or church council, a two-page PDF in the church's brand, from QuickBooks. Use when a pastor or treasurer asks to build or run the finance report, the vestry or council finance report, or this month's board finance packet. Read-only in QuickBooks. Finance onboarding comes first for a church that has not finished it.","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Ffinance-report\u002FSKILL.md",[],[],{"skillNo":414,"name":415,"nameZh":6,"description":416,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":417,"categories":418,"keywords":419,"publishedAt":19},"01M7CDZ4DMZGKZ2D09DF8NQAEF","finance-onboarding","Set up a church's finances for board reporting, in four stages that end with the monthly finance report locked in. Use when a pastor or treasurer asks to set up the church's finances, look at the books, get ready for a vestry or council finance report, or check where finance setup stands. Read-only in QuickBooks and every other finance system.","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Ffinance-onboarding\u002FSKILL.md",[],[]]