[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CDZ4DMZGKZ2D09DF8NQAEF":3,"skill-same:01M7CDZ4DMZGKZ2D09DF8NQAEF":61},{"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},"01M7CDZ4DMZGKZ2D09DF8NQAEF","finance-onboarding",null,"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.","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\u002Ffinance-onboarding\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: finance-onboarding\ndescription: 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.\n---\n\n# Finance Onboarding\n\nFour stages that lead to the monthly finance report. The report is the\ndestination, not the starting point: many churches' books need some work\nbefore a board report can be trusted, and the pastor should see the books\nbefore the board does.\n\n| Stage | Outcome | Ends when |\n|---|---|---|\n| 1. Look | A plain-language finance overview for the pastor, and questions for the treasurer | The overview exists and the pastor has read it |\n| 2. First report | Settings saved and a sample edition, with stage 1's findings shown as caveats | Settings saved; sample built |\n| 3. Make the books report-ready | A readiness checklist and a one-page treasurer packet | Every item met, or waived with a reason |\n| 4. Lock the monthly report | Calendar, approver, and the first real edition approved by the treasurer | Locked; the finance report workflow takes over |\n\nOnboarding keeps its place in `finance\u002Fonboarding-state.json` and can be\npaused and resumed at any stage.\n\n## Start or resume\n\nRun the app-loaded adapter once, for this workflow and for the finance\nreport, whose operations stages 1, 2, and 4 use:\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 finance-onboarding\n```\n\nUse the returned `launcher` prefix (written `\u003Clauncher>` below) for every\noperation. Then:\n\n```bash\n\u003Clauncher> finance-onboarding orient\n```\n\nTell the person, in one or two sentences, which stage they are in, what it is\nfor, and what is blocking it. Work on that stage only. Ask one question at a\ntime.\n\n## Stage 1: Look\n\n1. Readiness and QuickBooks connection: follow step 0 of the finance report\n   skill (connection, company name check, read-only). Nothing is changed in\n   QuickBooks at any stage.\n2. Pull the setup set into `finance\u002Fboard\u002Fsetup-pulls\u002F` as described in the\n   finance report skill's `references\u002Ffirst-time-setup.md`, step 1.\n3. Run the findings:\n\n   ```bash\n   \u003Clauncher> finance-onboarding look \\\n     --balance-sheet finance\u002Fboard\u002Fsetup-pulls\u002Fbalance-sheet.json \\\n     --pl-12m finance\u002Fboard\u002Fsetup-pulls\u002Fpl-12m.json \\\n     --pl-recent finance\u002Fboard\u002Fsetup-pulls\u002Fpl-recent.json\n   ```\n\n   Run it on the pulls as saved, even one you suspect the connector cut off.\n   The script checks each pull and, when one is cut off, stops and records\n   the refusal in `finance\u002Fonboarding\u002Flook-blocked.json`. Then tell the\n   pastor in plain words that the books could not be read in full yet, and\n   offer a shorter period or a QuickBooks export. The section totals in that\n   record are correct and may be quoted as totals; nothing else comes from\n   the cut-off pull.\n\n4. Write `finance\u002Ffinance-overview.md` for the pastor from\n   `finance\u002Fonboarding\u002Ffindings.json`, following\n   `references\u002Foverview-template.md`. Every figure names its source. Label\n   anything uncertain as an estimate. Anything that could alarm is framed as\n   a question for the treasurer, not a conclusion. Take balances and dates\n   from the findings as written (a liability below zero carries its balance\n   and the month it went below zero in `detail`); never work one out from\n   the pull's opening and change rows. When income stopped while clearing\n   or undeposited balances rose, say it looks like income not yet recorded,\n   and that the books do not show giving fell.\n5. Walk the pastor through it. Then `\u003Clauncher> finance-onboarding stage --done 1`.\n\n## Stage 2: First report\n\nRun first-time setup from the finance report skill's\n`references\u002Ffirst-time-setup.md`, then build and render a sample edition of\nthe last complete month with `--sample`. Open readiness items appear on it as\ncaveats. Show it. Then `stage --done 2`.\n\n## Stage 3: Make the books report-ready\n\n1. Show the checklist (`orient`). For each item, explain in two sentences\n   what it is and why a board needs it, then ask what is true today:\n\n   | Item | How it is known |\n   |---|---|\n   | Payment services cleared each month | The data, every pull |\n   | Money received is recorded | The data, when payment services are connected |\n   | Bank accounts reconciled monthly | Ask the treasurer, once |\n   | Months locked after checking | Ask the treasurer, once |\n   | Restricted funds confirmed | Ask, with the stage 1 data flag |\n   | A budget, or a decision to go without | Setup |\n\n2. Write the one-page treasurer packet (`references\u002Ftreasurer-packet.md`).\n   The treasurer or bookkeeper makes any changes in their own books; this\n   workflow never does.\n3. Record each answer:\n\n   ```bash\n   \u003Clauncher> finance-onboarding readiness --item month_lock --status met\n   \u003Clauncher> finance-onboarding readiness --item reconciliation --status waived \\\n     --reason \"The bookkeeper reconciles quarterly for now\"\n   ```\n\n   A waiver needs a reason. Waived and open items appear on every report, in\n   the Books readiness row and as plain caveats, until they are met. Items\n   checked from data are re-checked every month and flagged again if the\n   problem returns.\n4. When nothing is open: `stage --done 3`.\n\n## Stage 4: Lock the monthly report\n\n1. Agree the calendar and approver with the treasurer:\n\n   ```bash\n   \u003Clauncher> finance-onboarding calendar --books-closed-by \"the 15th\" \\\n     --report-by \"the 20th\" --meeting \"second Tuesday\" --approver \"NAME\"\n   ```\n\n2. Build the first real edition with the finance report workflow. The\n   treasurer approves it; set its `meta.status` to `final` and render once\n   more.\n3. `stage --done 4`. Onboarding is complete; each month after this, use the\n   finance report workflow.\n\n## Guardrails\n\n- Read-only in QuickBooks and every finance system, at every stage.\n- The overview is for the pastor. The board sees reports, not the overview.\n- Anything that could alarm goes to the treasurer first.\n- Not financial advice; the books are described, decisions stay with people.\n","# Finance Onboarding\n\nFour stages that lead to the monthly finance report. The report is the\ndestination, not the starting point: many churches' books need some work\nbefore a board report can be trusted, and the pastor should see the books\nbefore the board does.\n\n| Stage | Outcome | Ends when |\n|---|---|---|\n| 1. Look | A plain-language finance overview for the pastor, and questions for the treasurer | The overview exists and the pastor has read it |\n| 2. First report | Settings saved and a sample edition, with stage 1's findings shown as caveats | Settings saved; sample built |\n| 3. Make the books report-ready | A readiness checklist and a one-page treasurer packet | Every item met, or waived with a reason |\n| 4. Lock the monthly report | Calendar, approver, and the first real edition approved by the treasurer | Locked; the finance report workflow takes over |\n\nOnboarding keeps its place in `finance\u002Fonboarding-state.json` and can be\npaused and resumed at any stage.\n\n## Start or resume\n\nRun the app-loaded adapter once, for this workflow and for the finance\nreport, whose operations stages 1, 2, and 4 use:\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 finance-onboarding\n```\n\nUse the returned `launcher` prefix (written `\u003Clauncher>` below) for every\noperation. Then:\n\n```bash\n\u003Clauncher> finance-onboarding orient\n```\n\nTell the person, in one or two sentences, which stage they are in, what it is\nfor, and what is blocking it. Work on that stage only. Ask one question at a\ntime.\n\n## Stage 1: Look\n\n1. Readiness and QuickBooks connection: follow step 0 of the finance report\n   skill (connection, company name check, read-only). Nothing is changed in\n   QuickBooks at any stage.\n2. Pull the setup set into `finance\u002Fboard\u002Fsetup-pulls\u002F` as described in the\n   finance report skill's `references\u002Ffirst-time-setup.md`, step 1.\n3. Run the findings:\n\n   ```bash\n   \u003Clauncher> finance-onboarding look \\\n     --balance-sheet finance\u002Fboard\u002Fsetup-pulls\u002Fbalance-sheet.json \\\n     --pl-12m finance\u002Fboard\u002Fsetup-pulls\u002Fpl-12m.json \\\n     --pl-recent finance\u002Fboard\u002Fsetup-pulls\u002Fpl-recent.json\n   ```\n\n   Run it on the pulls as saved, even one you suspect the connector cut off.\n   The script checks each pull and, when one is cut off, stops and records\n   the refusal in `finance\u002Fonboarding\u002Flook-blocked.json`. Then tell the\n   pastor in plain words that the books could not be read in full yet, and\n   offer a shorter period or a QuickBooks export. The section totals in that\n   record are correct and may be quoted as totals; nothing else comes from\n   the cut-off pull.\n\n4. Write `finance\u002Ffinance-overview.md` for the pastor from\n   `finance\u002Fonboarding\u002Ffindings.json`, following\n   `references\u002Foverview-template.md`. Every figure names its source. Label\n   anything uncertain as an estimate. Anything that could alarm is framed as\n   a question for the treasurer, not a conclusion. Take balances and dates\n   from the findings as written (a liability below zero carries its balance\n   and the month it went below zero in `detail`); never work one out from\n   the pull's opening and change rows. When income stopped while clearing\n   or undeposited balances rose, say it looks like income not yet recorded,\n   and that the books do not show giving fell.\n5. Walk the pastor through it. Then `\u003Clauncher> finance-onboarding stage --done 1`.\n\n## Stage 2: First report\n\nRun first-time setup from the finance report skill's\n`references\u002Ffirst-time-setup.md`, then build and render a sample edition of\nthe last complete month with `--sample`. Open readiness items appear on it as\ncaveats. Show it. Then `stage --done 2`.\n\n## Stage 3: Make the books report-ready\n\n1. Show the checklist (`orient`). For each item, explain in two sentences\n   what it is and why a board needs it, then ask what is true today:\n\n   | Item | How it is known |\n   |---|---|\n   | Payment services cleared each month | The data, every pull |\n   | Money received is recorded | The data, when payment services are connected |\n   | Bank accounts reconciled monthly | Ask the treasurer, once |\n   | Months locked after checking | Ask the treasurer, once |\n   | Restricted funds confirmed | Ask, with the stage 1 data flag |\n   | A budget, or a decision to go without | Setup |\n\n2. Write the one-page treasurer packet (`references\u002Ftreasurer-packet.md`).\n   The treasurer or bookkeeper makes any changes in their own books; this\n   workflow never does.\n3. Record each answer:\n\n   ```bash\n   \u003Clauncher> finance-onboarding readiness --item month_lock --status met\n   \u003Clauncher> finance-onboarding readiness --item reconciliation --status waived \\\n     --reason \"The bookkeeper reconciles quarterly for now\"\n   ```\n\n   A waiver needs a reason. Waived and open items appear on every report, in\n   the Books readiness row and as plain caveats, until they are met. Items\n   checked from data are re-checked every month and flagged again if the\n   problem returns.\n4. When nothing is open: `stage --done 3`.\n\n## Stage 4: Lock the monthly report\n\n1. Agree the calendar and approver with the treasurer:\n\n   ```bash\n   \u003Clauncher> finance-onboarding calendar --books-closed-by \"the 15th\" \\\n     --report-by \"the 20th\" --meeting \"second Tuesday\" --approver \"NAME\"\n   ```\n\n2. Build the first real edition with the finance report workflow. The\n   treasurer approves it; set its `meta.status` to `final` and render once\n   more.\n3. `stage --done 4`. Onboarding is complete; each month after this, use the\n   finance report workflow.\n\n## Guardrails\n\n- Read-only in QuickBooks and every finance system, at every stage.\n- The overview is for the pastor. The board sees reports, not the overview.\n- Anything that could alarm goes to the treasurer first.\n- Not financial advice; the books are described, decisions stay with people.\n",{"name":5,"description":7},"main","c32b7366e6c4275e4ee70c18fd7b630d56a6ed8b","skills\u002Ffinance-onboarding","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 finance-onboarding",{"tool":37,"command":38},"bunx","bunx skills add stephenfsetzer\u002Fhandbuilt-church-labs --skill finance-onboarding",{"tool":40,"command":41},"pnpm","pnpm dlx skills add stephenfsetzer\u002Fhandbuilt-church-labs --skill finance-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Ffinance-onboarding\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Foverview-template.md","REFERENCE","参考文档",1503,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Ffinance-onboarding\u002Freferences\u002Foverview-template.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Ftreasurer-packet.md",1049,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Ffinance-onboarding\u002Freferences\u002Ftreasurer-packet.md",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"scripts\u002Ffinance_onboarding.py","SCRIPT","脚本",21683,"https:\u002F\u002Fgithub.com\u002Fstephenfsetzer\u002Fhandbuilt-church-labs\u002Fblob\u002Fmain\u002Fskills\u002Ffinance-onboarding\u002Fscripts\u002Ffinance_onboarding.py",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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",[],[]]