[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K3VVV3YTMNRDVDSETMTYAY":3,"skill-same:01M6K3VVV3YTMNRDVDSETMTYAY":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6K3VVV3YTMNRDVDSETMTYAY","invoice-claim-review",null,"Summarize a claim, invoice batch, or approval item for executive or council review, including funding source and red flags.","BrianPillmore\u002FMayorGPT","BrianPillmore","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F89977304?v=4","01M6K3S5PAA7GX17DJCHR5QFZ2","01M6K3S5TAA6HKGD1BY6VTV0QB",1,"MIT","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Ffinance\u002Finvoice-claim-review\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000040","财务","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36],"review","claim","invoice","invoice claim review","summarize","council review","council","batch","approval","flags","red","for","source","funding","2026-11-10 10:12:30",false,"---\nname: invoice-claim-review\ndescription: Summarize a claim, invoice batch, or approval item for executive or council review, including funding source and red flags.\nargument-hint: [claim-batch]\n---\n\n## Purpose\nPrepare a pre-audit review of a claims\u002Fwarrant register or individual invoice so that approvers can see what is being paid, under what authority, from which fund, and what could be wrong. This is a review summary; it does not replace the finance officer's certification or the legal duty to audit claims.\n\n## Required inputs\n- Claims list or invoice images with vendor, invoice number, date, amount, fund\u002Faccount, and department approver.\n- Purchase orders, contracts, change orders, receiving documents, and bid or quote file for items of concern.\n- Budget status for each affected account and appropriation level.\n- Vendor master data: W-9, address, bank change requests, and prior payments.\n\n## Workflow\n1. Verify each item against the three-way match: purchase order or contract, receiving or acceptance evidence, and invoice. Missing receiving evidence is an exception.\n2. Authority check: contract executed before service? Within the delegated spending authority of the approver? Above the competitive bidding threshold or council approval threshold (use the city's adopted thresholds; state thresholds vary)?\n3. Duplicate and splitting test: same vendor, similar amounts, same dates; multiple invoices just under a purchasing threshold; invoice numbers sequential or repeated.\n4. Funding test: correct fund and account? Enough appropriation? Restricted funds used only for eligible purposes (grants, gas tax, utility enterprise)? Interfund implications?\n5. Vendor test: new vendor or changed bank details (verify by independent call-back to a known contact), employee or official relationship (conflict of interest), debarment for federally funded items, 1099 reporting, and sales tax exemption handling.\n6. Pricing and terms: unit prices vs. contract, change orders not approved, retainage handling on construction, prompt-payment law interest, and travel or P-card items against policy.\n7. Timing: late fees, discounts, year-end cutoff (accrual to correct fiscal year), and whether the item is a prior-year obligation.\n8. Summarize: totals by fund, exceptions by severity, items to hold, and items recommended for approval.\n\n## Output structure\n| Claim # | Vendor | Amount | Fund\u002FAccount | Authority | 3-way match | Exception | Severity | Recommendation (approve\u002Fhold\u002Fquery) |\n\nAdd: totals by fund, funding-source note, exceptions list with the question to ask, and items requiring council action (above thresholds, no contract, emergency purchase ratification).\n\n## Red flags \u002F escalate\n- Payment without a contract or purchase order, or backdated documents.\n- Vendor bank-account change request by email (possible business email compromise).\n- Related-party vendors, or an approver who is also the requester.\n- Splitting to avoid bidding or approval limits.\n- Payment from restricted funds for ineligible purposes.\n- Round-dollar, unusual, or after-hours invoices from a new vendor.\n- Suspected fraud: stop, preserve records, and notify the finance director and city attorney.\n\n## Common mistakes\n- Treating department approval as proof of delivery.\n- Approving to avoid late charges without resolving exceptions.\n- Mixing multiple fiscal years in one cutoff.\n- Not documenting why an exception was accepted.\n\n## State-law variance\nClaims audit, warrant signing, and prompt-pay rules differ by state. Emergency purchase ratification procedures vary.\n","## Purpose\nPrepare a pre-audit review of a claims\u002Fwarrant register or individual invoice so that approvers can see what is being paid, under what authority, from which fund, and what could be wrong. This is a review summary; it does not replace the finance officer's certification or the legal duty to audit claims.\n\n## Required inputs\n- Claims list or invoice images with vendor, invoice number, date, amount, fund\u002Faccount, and department approver.\n- Purchase orders, contracts, change orders, receiving documents, and bid or quote file for items of concern.\n- Budget status for each affected account and appropriation level.\n- Vendor master data: W-9, address, bank change requests, and prior payments.\n\n## Workflow\n1. Verify each item against the three-way match: purchase order or contract, receiving or acceptance evidence, and invoice. Missing receiving evidence is an exception.\n2. Authority check: contract executed before service? Within the delegated spending authority of the approver? Above the competitive bidding threshold or council approval threshold (use the city's adopted thresholds; state thresholds vary)?\n3. Duplicate and splitting test: same vendor, similar amounts, same dates; multiple invoices just under a purchasing threshold; invoice numbers sequential or repeated.\n4. Funding test: correct fund and account? Enough appropriation? Restricted funds used only for eligible purposes (grants, gas tax, utility enterprise)? Interfund implications?\n5. Vendor test: new vendor or changed bank details (verify by independent call-back to a known contact), employee or official relationship (conflict of interest), debarment for federally funded items, 1099 reporting, and sales tax exemption handling.\n6. Pricing and terms: unit prices vs. contract, change orders not approved, retainage handling on construction, prompt-payment law interest, and travel or P-card items against policy.\n7. Timing: late fees, discounts, year-end cutoff (accrual to correct fiscal year), and whether the item is a prior-year obligation.\n8. Summarize: totals by fund, exceptions by severity, items to hold, and items recommended for approval.\n\n## Output structure\n| Claim # | Vendor | Amount | Fund\u002FAccount | Authority | 3-way match | Exception | Severity | Recommendation (approve\u002Fhold\u002Fquery) |\n\nAdd: totals by fund, funding-source note, exceptions list with the question to ask, and items requiring council action (above thresholds, no contract, emergency purchase ratification).\n\n## Red flags \u002F escalate\n- Payment without a contract or purchase order, or backdated documents.\n- Vendor bank-account change request by email (possible business email compromise).\n- Related-party vendors, or an approver who is also the requester.\n- Splitting to avoid bidding or approval limits.\n- Payment from restricted funds for ineligible purposes.\n- Round-dollar, unusual, or after-hours invoices from a new vendor.\n- Suspected fraud: stop, preserve records, and notify the finance director and city attorney.\n\n## Common mistakes\n- Treating department approval as proof of delivery.\n- Approving to avoid late charges without resolving exceptions.\n- Mixing multiple fiscal years in one cutoff.\n- Not documenting why an exception was accepted.\n\n## State-law variance\nClaims audit, warrant signing, and prompt-pay rules differ by state. Emergency purchase ratification procedures vary.\n",{"name":5,"description":7,"argument-hint":42},[43],"claim-batch","master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Ffinance\u002Finvoice-claim-review",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill invoice-claim-review",{"tool":57,"command":58},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill invoice-claim-review",{"tool":60,"command":61},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill invoice-claim-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Ffinance\u002Finvoice-claim-review\u002FSKILL.md",true,[],[66,85,97,127,146,159],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":37},"01M6K466QB0Q2EVZRJ5X1XY21C","town-hall-kit","Prepare a town hall kit with agenda, ground rules, likely questions, follow-up method, and message priorities.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Ftown-hall-kit\u002FSKILL.md",[],[73,74,75,76,77,78,79,80,81,82,83,84],"town hall kit","kit","follow-up","questions","with","event","agenda","prepare","priorities","message","Rules","up",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":37},"01M6K462B8XJ2FFYH8BAXR0ZM5","speechwriter","Draft remarks for the mayor, council, manager, or department head in a strong but grounded municipal voice.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fspeechwriter\u002FSKILL.md",[],[87,92,29,93,94,95,78,96,34],"draft","voice","but","head","manager",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":111,"publishedAt":37},"01M6K45Z8MYT7FVMV48WE0MACS","social-post-series","Generate a multi-post city social media series with tone control, accessibility, and channel fit.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fsocial-post-series\u002FSKILL.md",[103,108],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":109,"categoryName":110,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000035","市场营销",[112,113,114,115,116,117,118,77,119,120,121,122,123,124,125,126],"social post","series","post","social","social post series","fit","multi","social media","control","accessibility","generate","Media","channel","campaign","tone",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":136,"publishedAt":37},"01M6K45W3AWHA1GMZV2PRDYJBS","public-comment-summarizer","Synthesize hearing or meeting comments into themes, misconceptions, unanswered questions, and response options.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fpublic-comment-summarizer\u002FSKILL.md",[133],{"categoryNo":134,"categoryName":135,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000034","行政与办公人员",[137,138,139,140,141,142,143,76,144,145],"public","public comment summarizer","public comment","summarizer","options","synthesize","themes","comments","meeting",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":37},"01M6K45QWBXSDMGQTA1E9NC43M","press-release-writer","Write a city press release that is accurate, readable, and aligned with legal and operational review needs.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fpress-release-writer\u002FSKILL.md",[],[153,154,155,156,23,157,158,77],"press release writer","press release","writer","release","write","legal",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":166,"publishedAt":37},"01M6K45JXZRSW4XXH78FTRBB2A","meeting-notice-drafter","Draft a legally sufficient public notice for any city council, board, commission, or committee meeting — covering required content, posting deadlines, and special-meeting or emergency-meeting rules.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fmeeting-notice-drafter\u002FSKILL.md",[165],{"categoryNo":134,"categoryName":135,"taxonomyType":20,"taxonomyTypeDesc":21},[167,145,168,169,83,137,170,92,171,172,34,29],"meeting notice drafter","notice","content","board","posting","type"]