[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CDZBWD14TBP0S60F9P7FW2":3,"skill-same:01M7CDZBWD14TBP0S60F9P7FW2":101},{"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},"01M7CDZBWD14TBP0S60F9P7FW2","onboarding",null,"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.","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\u002Fonboarding\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: onboarding\ndescription: \"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.\"\n---\n\n# Set up my Church Command Center\n\nCreate a private church folder, a useful church profile, and a visible progress\nrecord. Recover source facts before asking the pastor for configuration details.\n\nThe pastor owns this workspace and may change its instructions, skills, and files.\nThis skill governs Handbuilt setup; it does not restrict other work. For local edits,\nread [Workspace customization](..\u002F..\u002Fhandbook\u002Fworkspace-customization.md); before editing or restoring instructions,\nuse [Instruction recovery](..\u002F..\u002Fhandbook\u002Finstruction-recovery.md).\n\nRead supporting references when their stage is reached:\n\n- [Computer preparation and progress](references\u002Fcomputer-preparation.md) at the start or when resuming setup, with [Guided computer setup](references\u002Fguided-setup.md) whenever a tool is missing, an error appears, or the pastor must act.\n- [Connection and visual setup](references\u002Fconnection-and-brand.md) when creating or resuming a church folder.\n- [Website discovery and QR](references\u002Fwebsite-discovery.md) for bounded\n  website inspection, brand candidates, and QR destinations.\n- [Worship onboarding](references\u002Fworship-onboarding.md) after the private\n  folder exists and the pastor can provide a bulletin or use the fallback\n  questions.\n  when onboarding identifies more than one recurring service, a reusable part,\n  or a scoped change that must carry into later bulletins.\n\n## Source roles\n\n- **Website:** public identity, names, leadership, contact details, service\n  times, brand candidates, newcomer information, and likely QR destinations.\n- **Recent bulletin:** the initial working template for the order of worship,\n  printed responses, music and service structure, recurring sections, role\n  slots, and page layout.\n- **Pastor:** resolution of conflicts, missing values, local or\n  licensed text, and later changes to the working template.\n\nThe website proposes public identity values for one bundled confirmation. A\nbulletin deliberately supplied for onboarding is the church's working template\nuntil the pastor changes it. Carry its observable structure forward without\nasking the pastor to approve each section separately. Keep date-specific\nreadings, hymns, petitions, announcements, and names as weekly replacements.\n\nFor recurring services and reusable parts, follow [Service design](..\u002Fbulletin\u002Freferences\u002Fservice-design.md).\nRecover saved choices, recommend the closest order, verify scoped saves, and explain what carries forward.\n\n## Proactive working-template contract\n\nComplete all safe inspection and extraction before asking a question. The\npastor should approve a concrete proposal, not help the agent discover facts\nthat are already available on the website or in the bulletin.\n\nAsk only when:\n\n- two sources conflict in a way that changes the result;\n- a required value cannot be observed and blocks the first useful result;\n- local or licensed text needs a confirmed source location; or\n- the pastor must choose between materially different outcomes.\n\nBundle related website facts into one confirmation. Do not ask for a second\nconfirmation of the bulletin template. Save a clear bulletin structure and\nchoice as a working default; ask one bundled question only where it is\nambiguous.\n\nAssume the pastor is new to a local agent. Say what you are doing, why it\nmatters, what happens next, whether anything leaves the computer, and what was\nsaved. Announce and take the next defined action. Do not wait for the pastor to ask \"what's next?\"\nEvidence ledgers and internal artifacts support the work. Maintain them quietly. Report the useful result and link progress once.\n\n## Required stage sequence\n\nDo not ask a later-stage question while an earlier stage is incomplete:\n\n`workspace runtime ready -> welcome -> website discovery -> identity confirmed -> private\nfolder created -> worship source chosen -> worship setup -> first useful result\n-> optional setup when requested`\n\nAt each transition, inspect available sources, take defined safe actions,\nexplain why the decision matters and what it enables, ask one focused question when needed, then\nread back the answer in plain language, then batch and verify the update.\nReport the pastor-facing result, not an internal\nfile inventory.\n\nAsk no more than three questions in one turn (prefer none when sources answer them), counting each thing the\npastor must answer, not the numbers on a list; ask the rest after they answer. Say each choice in plain words, not only its letter. Never ask again what a source settled.\n“Later,” “not sure,” “unknown,” and “not applicable” are valid; require no magic confirmation phrase.\n\n## Runtime gate\n\nGive a brief setup orientation, then follow\n[Computer preparation and progress](references\u002Fcomputer-preparation.md).\nCheck all dependencies together, using workspace readiness for this stage:\n\n```bash\n\"\u003Cplugin-root>\u002Fbin\u002Fhandbuilt-python\" \"\u003Cplugin-root>\u002Ftools\u002Fhandbuilt_runtime.py\" doctor --capability workspace --format json\n```\n\n`handbuilt-python` is Handbuilt's own Python (`bin\\handbuilt-python.cmd` on Windows without\nGit Bash); never ask the pastor to install Python. After `ready`, use the returned\n`runtime.python` for workflow commands. `\u003Cplugin-root>` is the installed plugin directory. Quote complete executable and file paths.\nMissing PDF tools remain pending until PDF import or bulletin work needs them.\nBefore that work, run the separate `verify` check described in the reference.\n\nAfter the private church folder exists, run the app-loaded adapter once:\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 onboarding\n```\n\nRead the returned skill path and use its exact `launcher` prefix for every\nonboarding operation in this task. Do not run `start` again after reading it.\nThe normal `church-folder\u002Fhandbuilt.py start onboarding` command remains valid\nfor a person checking the connection manually.\n\nRun `onboarding status` through the returned launcher and read back saved values\nand progress. Use the plugin root's `AGENTS.md` commands for requested tests.\n\n## Welcome\nStart with a short orientation before collecting details:\n\n> Welcome. I’ll help set up a private church folder on this computer. It will\n> hold your church information, bulletins, and sermon work. I’ll use your\n> public website for public facts and, when available, a recent bulletin to\n> understand the detailed order of worship. Nothing changes on your website.\n> I’ll show you what I find before using it. You can say “not sure” or “later”\n> at any point.\n\nAsk for the church website. If there is no website, ask for the formal church\nname and a short folder name instead. Never request passwords, payment details,\nor private pastoral information about parishioners.\n\n## Website discovery\n\nAfter receiving a website, read the bounded website reference. Inspect the\nhomepage first, then only clearly relevant pages such as About, Worship,\nContact, Staff, Newcomers, Give, and Events. Do not crawl the whole site by\ndefault.\n\nReturn a concise discovery report with:\n\n- **What I found:** public name, tradition if clearly stated, address, service\n  times, public leaders, contact details, and relevant links.\n- **Brand preview:** logo candidates, colors, source pages, and print-quality\n  concerns.\n- **Possible conflicts:** disagreements across pages or with the pastor.\n- **Still unknown:** only values that are missing and relevant to the\n  first useful result.\n\nLabel each value as found on the website, supplied by the pastor, or proposed\nfrom a visual sample. Show source pages before saving a value. A website\ncandidate is not a confirmed standing setting.\n\n## Identity and private folder\n\nUse website findings to propose the formal name, short name, tradition, city,\naddress, website, and regular services. Bundle the identity, folder name,\nlocation, conflicts and the look into one confirmation, not a turn each. With\nno logo or colors on the website, the look to confirm is \"neutral colors and\nno logo for now\"; save the answer, never leave it for the first bulletin.\n\nThe default location is the Desktop. Read back the exact folder name and location, and say what will happen:\n\n> I have the folder name as “...” and the location as “...”. I’ll create that\n> private folder now. It will contain a visible onboarding record showing what\n> we found, what you confirmed, and what still needs attention.\n\nFollow [Identity setup](references\u002Fidentity-setup.md) to create the confirmed\nfolder with `church_setup.py create`, save the supported identity patch, and\nverify its files. Immediately record the folder path, website source,\ndiscovery summary, confirmed identity, pending items, and next step in\n`ONBOARDING.md`. Tell the pastor the exact private path.\n\nIf the folder already exists, switch to update mode. Preserve custom skills,\nhost instructions, sermons, bulletins, and church-edited notes. Do not restore\nintentionally removed files. Reconnection does not replace workspace guidance.\n\n## Route to worship onboarding\n\nOnce the private folder exists, ask whether the pastor can provide a recent\nbulletin in Word or PDF format. Explain that the website remains important for\nidentity, leadership, contact, brand, and QR work, while the bulletin can\nbecome the initial working template for detailed worship and bulletin work.\n\nIf a usable bulletin is available, read and follow\n[Worship onboarding](references\u002Fworship-onboarding.md), using the bulletin as\nthe working template for worship details and recurring bulletin structure. For\na supplied PDF, run the canonical [source import and\ninventory](..\u002Fbulletin\u002Freferences\u002Fsource-inventory.md) workflow and account\nfor every page; a shorter website roster never excuses skipping a supplied\nstanding directory or recurring section, only a recorded conflict or omission.\n\nIf no bulletin is available, read the same reference and use its standard\npurpose-first worship questions. Missing a bulletin must not block onboarding\nor pressure the pastor to find one.\n\n## Safety and progress\n\nChurch-specific information, uploaded bulletins, licensed material, and\nreceipts belong in the private folder; this public repository holds only\nreusable workflows and synthetic tests.\n\nAfter each meaningful stage, report:\n\n- what is **saved** and verified;\n- what is **pending** because a tool or asset needs attention; and\n- what is **still unresolved** because the pastor has not decided it.\n\nBatch related changes and update the progress record at meaningful stage boundaries, not for every intermediate edit.\n\nA successful terminal command or helper call is not proof onboarding is\ncomplete: check the folder, progress record, configuration, and first result.\n\n## Bounded setup updates\nOn return, read existing setup notes and preserve local work. Update requested values only.\n\nWhen a setup value must be saved or changed, use the skill's\n`scripts\u002Fchurch_setup.py` helper. It reads the existing `church.yaml` and `worship\u002Fprofile.yaml`, validates a\nsmall named patch, and writes only standing settings the bulletin and sermon\nworkflows already consume; it refuses paths inside the Labs repository,\neither plugin cache, or a symlink into those locations. `status` reports\nactual folder, bulletin, sermon, and first-result readiness from the files. Write every patch file inside the church folder (`\u003Cchurch-folder>\u002F.onboarding-standing-patch.json`), never anywhere else on the computer, and remove it once its values are saved.\nUse `--scope standing` for church defaults and `--scope service --service-id\n\u003Cid>` for a saved service's usual choices. See the service-design reference\nfor previews, affected services, and stale-update protection. Keep dated\nassignments and exceptions in the weekly workflow. This helper never edits\nhistory or sermon files.\nFor a request that also prepares weekly clergy assignments or bulletin work,\nread the bulletin skill and use its orientation and weekly-input guidance.\nFinish the standing preference update, then continue that workflow from the\nsaved church context.\nBefore closeout, use the returned launcher prefix for `onboarding status`; do\nnot switch to the mutable church-folder launcher during this task.\nReport each workflow from its readiness boolean. `needs_input` and\n`partially_ready` never mean both workflows are complete. Correct stored values\nfrom confirmed answers before asking again. Stop when the requested workflow\nis ready or the pastor defers it. Call an actual first result only after checking\nits output and receipt. The next requests can be “build my bulletin” and\n“start my sermon research.” Do not automatically continue into QR, leadership,\nlayout, research-preference, or other optional questions.\n","# Set up my Church Command Center\n\nCreate a private church folder, a useful church profile, and a visible progress\nrecord. Recover source facts before asking the pastor for configuration details.\n\nThe pastor owns this workspace and may change its instructions, skills, and files.\nThis skill governs Handbuilt setup; it does not restrict other work. For local edits,\nread [Workspace customization](..\u002F..\u002Fhandbook\u002Fworkspace-customization.md); before editing or restoring instructions,\nuse [Instruction recovery](..\u002F..\u002Fhandbook\u002Finstruction-recovery.md).\n\nRead supporting references when their stage is reached:\n\n- [Computer preparation and progress](references\u002Fcomputer-preparation.md) at the start or when resuming setup, with [Guided computer setup](references\u002Fguided-setup.md) whenever a tool is missing, an error appears, or the pastor must act.\n- [Connection and visual setup](references\u002Fconnection-and-brand.md) when creating or resuming a church folder.\n- [Website discovery and QR](references\u002Fwebsite-discovery.md) for bounded\n  website inspection, brand candidates, and QR destinations.\n- [Worship onboarding](references\u002Fworship-onboarding.md) after the private\n  folder exists and the pastor can provide a bulletin or use the fallback\n  questions.\n  when onboarding identifies more than one recurring service, a reusable part,\n  or a scoped change that must carry into later bulletins.\n\n## Source roles\n\n- **Website:** public identity, names, leadership, contact details, service\n  times, brand candidates, newcomer information, and likely QR destinations.\n- **Recent bulletin:** the initial working template for the order of worship,\n  printed responses, music and service structure, recurring sections, role\n  slots, and page layout.\n- **Pastor:** resolution of conflicts, missing values, local or\n  licensed text, and later changes to the working template.\n\nThe website proposes public identity values for one bundled confirmation. A\nbulletin deliberately supplied for onboarding is the church's working template\nuntil the pastor changes it. Carry its observable structure forward without\nasking the pastor to approve each section separately. Keep date-specific\nreadings, hymns, petitions, announcements, and names as weekly replacements.\n\nFor recurring services and reusable parts, follow [Service design](..\u002Fbulletin\u002Freferences\u002Fservice-design.md).\nRecover saved choices, recommend the closest order, verify scoped saves, and explain what carries forward.\n\n## Proactive working-template contract\n\nComplete all safe inspection and extraction before asking a question. The\npastor should approve a concrete proposal, not help the agent discover facts\nthat are already available on the website or in the bulletin.\n\nAsk only when:\n\n- two sources conflict in a way that changes the result;\n- a required value cannot be observed and blocks the first useful result;\n- local or licensed text needs a confirmed source location; or\n- the pastor must choose between materially different outcomes.\n\nBundle related website facts into one confirmation. Do not ask for a second\nconfirmation of the bulletin template. Save a clear bulletin structure and\nchoice as a working default; ask one bundled question only where it is\nambiguous.\n\nAssume the pastor is new to a local agent. Say what you are doing, why it\nmatters, what happens next, whether anything leaves the computer, and what was\nsaved. Announce and take the next defined action. Do not wait for the pastor to ask \"what's next?\"\nEvidence ledgers and internal artifacts support the work. Maintain them quietly. Report the useful result and link progress once.\n\n## Required stage sequence\n\nDo not ask a later-stage question while an earlier stage is incomplete:\n\n`workspace runtime ready -> welcome -> website discovery -> identity confirmed -> private\nfolder created -> worship source chosen -> worship setup -> first useful result\n-> optional setup when requested`\n\nAt each transition, inspect available sources, take defined safe actions,\nexplain why the decision matters and what it enables, ask one focused question when needed, then\nread back the answer in plain language, then batch and verify the update.\nReport the pastor-facing result, not an internal\nfile inventory.\n\nAsk no more than three questions in one turn (prefer none when sources answer them), counting each thing the\npastor must answer, not the numbers on a list; ask the rest after they answer. Say each choice in plain words, not only its letter. Never ask again what a source settled.\n“Later,” “not sure,” “unknown,” and “not applicable” are valid; require no magic confirmation phrase.\n\n## Runtime gate\n\nGive a brief setup orientation, then follow\n[Computer preparation and progress](references\u002Fcomputer-preparation.md).\nCheck all dependencies together, using workspace readiness for this stage:\n\n```bash\n\"\u003Cplugin-root>\u002Fbin\u002Fhandbuilt-python\" \"\u003Cplugin-root>\u002Ftools\u002Fhandbuilt_runtime.py\" doctor --capability workspace --format json\n```\n\n`handbuilt-python` is Handbuilt's own Python (`bin\\handbuilt-python.cmd` on Windows without\nGit Bash); never ask the pastor to install Python. After `ready`, use the returned\n`runtime.python` for workflow commands. `\u003Cplugin-root>` is the installed plugin directory. Quote complete executable and file paths.\nMissing PDF tools remain pending until PDF import or bulletin work needs them.\nBefore that work, run the separate `verify` check described in the reference.\n\nAfter the private church folder exists, run the app-loaded adapter once:\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 onboarding\n```\n\nRead the returned skill path and use its exact `launcher` prefix for every\nonboarding operation in this task. Do not run `start` again after reading it.\nThe normal `church-folder\u002Fhandbuilt.py start onboarding` command remains valid\nfor a person checking the connection manually.\n\nRun `onboarding status` through the returned launcher and read back saved values\nand progress. Use the plugin root's `AGENTS.md` commands for requested tests.\n\n## Welcome\nStart with a short orientation before collecting details:\n\n> Welcome. I’ll help set up a private church folder on this computer. It will\n> hold your church information, bulletins, and sermon work. I’ll use your\n> public website for public facts and, when available, a recent bulletin to\n> understand the detailed order of worship. Nothing changes on your website.\n> I’ll show you what I find before using it. You can say “not sure” or “later”\n> at any point.\n\nAsk for the church website. If there is no website, ask for the formal church\nname and a short folder name instead. Never request passwords, payment details,\nor private pastoral information about parishioners.\n\n## Website discovery\n\nAfter receiving a website, read the bounded website reference. Inspect the\nhomepage first, then only clearly relevant pages such as About, Worship,\nContact, Staff, Newcomers, Give, and Events. Do not crawl the whole site by\ndefault.\n\nReturn a concise discovery report with:\n\n- **What I found:** public name, tradition if clearly stated, address, service\n  times, public leaders, contact details, and relevant links.\n- **Brand preview:** logo candidates, colors, source pages, and print-quality\n  concerns.\n- **Possible conflicts:** disagreements across pages or with the pastor.\n- **Still unknown:** only values that are missing and relevant to the\n  first useful result.\n\nLabel each value as found on the website, supplied by the pastor, or proposed\nfrom a visual sample. Show source pages before saving a value. A website\ncandidate is not a confirmed standing setting.\n\n## Identity and private folder\n\nUse website findings to propose the formal name, short name, tradition, city,\naddress, website, and regular services. Bundle the identity, folder name,\nlocation, conflicts and the look into one confirmation, not a turn each. With\nno logo or colors on the website, the look to confirm is \"neutral colors and\nno logo for now\"; save the answer, never leave it for the first bulletin.\n\nThe default location is the Desktop. Read back the exact folder name and location, and say what will happen:\n\n> I have the folder name as “...” and the location as “...”. I’ll create that\n> private folder now. It will contain a visible onboarding record showing what\n> we found, what you confirmed, and what still needs attention.\n\nFollow [Identity setup](references\u002Fidentity-setup.md) to create the confirmed\nfolder with `church_setup.py create`, save the supported identity patch, and\nverify its files. Immediately record the folder path, website source,\ndiscovery summary, confirmed identity, pending items, and next step in\n`ONBOARDING.md`. Tell the pastor the exact private path.\n\nIf the folder already exists, switch to update mode. Preserve custom skills,\nhost instructions, sermons, bulletins, and church-edited notes. Do not restore\nintentionally removed files. Reconnection does not replace workspace guidance.\n\n## Route to worship onboarding\n\nOnce the private folder exists, ask whether the pastor can provide a recent\nbulletin in Word or PDF format. Explain that the website remains important for\nidentity, leadership, contact, brand, and QR work, while the bulletin can\nbecome the initial working template for detailed worship and bulletin work.\n\nIf a usable bulletin is available, read and follow\n[Worship onboarding](references\u002Fworship-onboarding.md), using the bulletin as\nthe working template for worship details and recurring bulletin structure. For\na supplied PDF, run the canonical [source import and\ninventory](..\u002Fbulletin\u002Freferences\u002Fsource-inventory.md) workflow and account\nfor every page; a shorter website roster never excuses skipping a supplied\nstanding directory or recurring section, only a recorded conflict or omission.\n\nIf no bulletin is available, read the same reference and use its standard\npurpose-first worship questions. Missing a bulletin must not block onboarding\nor pressure the pastor to find one.\n\n## Safety and progress\n\nChurch-specific information, uploaded bulletins, licensed material, and\nreceipts belong in the private folder; this public repository holds only\nreusable workflows and synthetic tests.\n\nAfter each meaningful stage, report:\n\n- what is **saved** and verified;\n- what is **pending** because a tool or asset needs attention; and\n- what is **still unresolved** because the pastor has not decided it.\n\nBatch related changes and update the progress record at meaningful stage boundaries, not for every intermediate edit.\n\nA successful terminal command or helper call is not proof onboarding is\ncomplete: check the folder, progress record, configuration, and first result.\n\n## Bounded setup updates\nOn return, read existing setup notes and preserve local work. Update requested values only.\n\nWhen a setup value must be saved or changed, use the skill's\n`scripts\u002Fchurch_setup.py` helper. It reads the existing `church.yaml` and `worship\u002Fprofile.yaml`, validates a\nsmall named patch, and writes only standing settings the bulletin and sermon\nworkflows already consume; it refuses paths inside the Labs repository,\neither plugin cache, or a symlink into those locations. `status` reports\nactual folder, bulletin, sermon, and first-result readiness from the files. Write every patch file inside the church folder (`\u003Cchurch-folder>\u002F.onboarding-standing-patch.json`), never anywhere else on the computer, and remove it once its values are saved.\nUse `--scope standing` for church defaults and `--scope service --service-id\n\u003Cid>` for a saved service's usual choices. See the service-design reference\nfor previews, affected services, and stale-update protection. Keep dated\nassignments and exceptions in the weekly workflow. This helper never edits\nhistory or sermon files.\nFor a request that also prepares weekly clergy assignments or bulletin work,\nread the bulletin skill and use its orientation and weekly-input guidance.\nFinish the standing preference update, then continue that workflow from the\nsaved church context.\nBefore closeout, use the returned launcher prefix for `onboarding status`; do\nnot switch to the mutable church-folder launcher during this task.\nReport each workflow from its readiness boolean. `needs_input` and\n`partially_ready` never mean both workflows are complete. Correct stored values\nfrom confirmed answers before asking again. Stop when the requested workflow\nis ready or the pastor defers it. Call an actual first result only after checking\nits output and receipt. The next requests can be “build my bulletin” and\n“start my sermon research.” Do not automatically continue into QR, leadership,\nlayout, research-preference, or other optional questions.\n",{"name":5,"description":7},"main","c32b7366e6c4275e4ee70c18fd7b630d56a6ed8b","skills\u002Fonboarding","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 onboarding",{"tool":37,"command":38},"bunx","bunx skills add stephenfsetzer\u002Fhandbuilt-church-labs --skill onboarding",{"tool":40,"command":41},"pnpm","pnpm dlx skills add stephenfsetzer\u002Fhandbuilt-church-labs --skill onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002FSKILL.md",true,[45,51,57,61,65,69,73,77,81,85,89,93,97],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",206,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"bulletin_import.py","SCRIPT","脚本",44221,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Fbulletin_import.py",{"path":58,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fcomputer-preparation.md",5503,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Freferences\u002Fcomputer-preparation.md",{"path":62,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fconnection-and-brand.md",4013,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Freferences\u002Fconnection-and-brand.md",{"path":66,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fguided-setup.md",10360,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Freferences\u002Fguided-setup.md",{"path":70,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fidentity-setup.md",2631,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Freferences\u002Fidentity-setup.md",{"path":74,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fwebsite-discovery.md",4501,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Freferences\u002Fwebsite-discovery.md",{"path":78,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fworship-onboarding.md",23063,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Freferences\u002Fworship-onboarding.md",{"path":82,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fbrand_setup.py",13800,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Fscripts\u002Fbrand_setup.py",{"path":86,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fchurch_setup.py",59296,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Fscripts\u002Fchurch_setup.py",{"path":90,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fimport_bulletin.py",7247,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Fscripts\u002Fimport_bulletin.py",{"path":94,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fqr_setup.py",4420,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Fscripts\u002Fqr_setup.py",{"path":98,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":99,"sourceHtmlUrl":100},"source_choices.py",16898,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fonboarding\u002Fsource_choices.py",[102,109,116,123,130,137],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"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":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"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",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":19},"01M7CDZ0835BK4VYTFXB3NV2ZX","bulletin","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.","https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Fbulletin\u002FSKILL.md",[],[]]