[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K3VQ7JGRA4CBGABRY8Z97X":3,"skill-same:01M6K3VQ7JGRA4CBGABRY8Z97X":63},{"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":17,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M6K3VQ7JGRA4CBGABRY8Z97X","grant-opportunity-screen",null,"Quickly screen a grant for eligibility, strategic fit, match burden, operating tail, and probability of success.","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\u002Fgrant-opportunity-screen\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28],"opportunity","screen","grant opportunity screen","probability","name","fit","operating","strategic","match","tail","for","2026-11-10 10:12:30",false,"---\nname: grant-opportunity-screen\ndescription: Quickly screen a grant for eligibility, strategic fit, match burden, operating tail, and probability of success.\nargument-hint: [grant-name]\n---\n\n## Purpose\nMake a fast go\u002Fno-go call on whether the city should invest staff time in an application. The cost of a grant is rarely the match alone: it includes grant-writing hours, compliance burden, the operating tail after the grant ends, and the opportunity cost of staff.\n\n## Required inputs\n- Notice of funding opportunity (NOFO) or program guidelines, with deadline, eligible applicants, eligible activities, and scoring criteria.\n- Funder type (federal, state pass-through, foundation) and award size range and expected number of awards.\n- Candidate project, its cost, readiness (design, environmental, site control), and sponsor department.\n- Adopted plans, CIP, and council priorities the project would serve.\n- Available local match and its source.\n\n## Workflow\n1. Eligibility gate: applicant type, population or income thresholds, geography, eligible costs, prior-award restrictions, SAM.gov\u002FUEI registration, and required audits. Any hard failure ends the screen.\n2. Fit: map the project to the scoring criteria with a rough point estimate per criterion. Note criteria the city cannot meet (e.g., partnership letters, benefit-cost analysis).\n3. Readiness: construction-ready vs. planning-only. Many programs reward readiness; unfunded environmental review or right-of-way can disqualify.\n4. Match and cash flow: required percentage, cash vs. in-kind, source and approval needed. Determine whether the grant is reimbursement-based (the city fronts cash) and whether the general fund can carry that float.\n5. Operating tail: staffing, maintenance, insurance, and reporting after the grant ends. Compare the tail to the benefit. State whether the project is in the CIP; grants should accelerate priorities, not create new ones the city cannot sustain.\n6. Compliance burden: Uniform Guidance procurement, Davis-Bacon, Buy America preferences, environmental review, reporting, and records (see grant-compliance-check).\n7. Probability and effort: estimate competitiveness (applications vs. awards if known), staff hours to apply, whether a consultant is needed, and cost of a consultant (check fee structure: contingency fees may be prohibited as a cost under federal awards).\n8. Decision: Pursue, Pursue with partner, Defer to next cycle, or Pass, with the reason.\n\n## Output structure\n| Criterion | Finding | Pass\u002FConcern\u002FFail |\nRows: eligibility, fit, readiness, match, cash flow, operating tail, compliance burden, competitiveness, staff effort.\n\nAdd: scoring-self-assessment table, timeline back from deadline, council actions needed (authorization to apply, match commitment), and recommendation.\n\n## Red flags \u002F escalate\n- Match source not identified or requiring a vote before the deadline.\n- Project not in any adopted plan or CIP.\n- Recurring cost obligations created without a funding source.\n- Prohibited consultant fee arrangements or conflicts of interest in grant-writing contracts.\n- Deadline too close to complete required letters, resolutions, or environmental documents.\n\n## Common mistakes\n- Chasing available money rather than an adopted priority.\n- Counting the grant amount without the tail.\n- Ignoring reimbursement float.\n- Underestimating application hours.\n- Treating a competitive program as likely without award history.\n\n## State-law variance\nCouncil authorization rules for applying, accepting, and matching funds vary by charter and state law.\n","## Purpose\nMake a fast go\u002Fno-go call on whether the city should invest staff time in an application. The cost of a grant is rarely the match alone: it includes grant-writing hours, compliance burden, the operating tail after the grant ends, and the opportunity cost of staff.\n\n## Required inputs\n- Notice of funding opportunity (NOFO) or program guidelines, with deadline, eligible applicants, eligible activities, and scoring criteria.\n- Funder type (federal, state pass-through, foundation) and award size range and expected number of awards.\n- Candidate project, its cost, readiness (design, environmental, site control), and sponsor department.\n- Adopted plans, CIP, and council priorities the project would serve.\n- Available local match and its source.\n\n## Workflow\n1. Eligibility gate: applicant type, population or income thresholds, geography, eligible costs, prior-award restrictions, SAM.gov\u002FUEI registration, and required audits. Any hard failure ends the screen.\n2. Fit: map the project to the scoring criteria with a rough point estimate per criterion. Note criteria the city cannot meet (e.g., partnership letters, benefit-cost analysis).\n3. Readiness: construction-ready vs. planning-only. Many programs reward readiness; unfunded environmental review or right-of-way can disqualify.\n4. Match and cash flow: required percentage, cash vs. in-kind, source and approval needed. Determine whether the grant is reimbursement-based (the city fronts cash) and whether the general fund can carry that float.\n5. Operating tail: staffing, maintenance, insurance, and reporting after the grant ends. Compare the tail to the benefit. State whether the project is in the CIP; grants should accelerate priorities, not create new ones the city cannot sustain.\n6. Compliance burden: Uniform Guidance procurement, Davis-Bacon, Buy America preferences, environmental review, reporting, and records (see grant-compliance-check).\n7. Probability and effort: estimate competitiveness (applications vs. awards if known), staff hours to apply, whether a consultant is needed, and cost of a consultant (check fee structure: contingency fees may be prohibited as a cost under federal awards).\n8. Decision: Pursue, Pursue with partner, Defer to next cycle, or Pass, with the reason.\n\n## Output structure\n| Criterion | Finding | Pass\u002FConcern\u002FFail |\nRows: eligibility, fit, readiness, match, cash flow, operating tail, compliance burden, competitiveness, staff effort.\n\nAdd: scoring-self-assessment table, timeline back from deadline, council actions needed (authorization to apply, match commitment), and recommendation.\n\n## Red flags \u002F escalate\n- Match source not identified or requiring a vote before the deadline.\n- Project not in any adopted plan or CIP.\n- Recurring cost obligations created without a funding source.\n- Prohibited consultant fee arrangements or conflicts of interest in grant-writing contracts.\n- Deadline too close to complete required letters, resolutions, or environmental documents.\n\n## Common mistakes\n- Chasing available money rather than an adopted priority.\n- Counting the grant amount without the tail.\n- Ignoring reimbursement float.\n- Underestimating application hours.\n- Treating a competitive program as likely without award history.\n\n## State-law variance\nCouncil authorization rules for applying, accepting, and matching funds vary by charter and state law.\n",{"name":5,"description":7,"argument-hint":34},[35],"grant-name","master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Ffinance\u002Fgrant-opportunity-screen",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill grant-opportunity-screen",{"tool":49,"command":50},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill grant-opportunity-screen",{"tool":52,"command":53},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill grant-opportunity-screen","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Ffinance\u002Fgrant-opportunity-screen\u002FSKILL.md",true,[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"grant-screen-template.md","REFERENCE","参考文档",124,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Ffinance\u002Fgrant-opportunity-screen\u002Fgrant-screen-template.md",[64,83,96,127,146,160],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":29},"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",[],[71,72,73,74,75,76,77,78,79,80,81,82],"town hall kit","kit","follow-up","questions","with","event","agenda","prepare","priorities","message","Rules","up",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":29},"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",[],[85,90,91,92,93,94,76,95,28],"draft","council","voice","but","head","manager",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":112,"publishedAt":29},"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",[102,107],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[113,114,115,116,117,23,118,75,119,120,121,122,123,124,125,126],"social post","series","post","social","social post series","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":29},"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":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000034","行政与办公人员",[137,138,139,140,141,142,143,74,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":29},"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,157,158,159,75],"press release writer","press release","writer","release","review","write","legal",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":29},"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",[166],{"categoryNo":134,"categoryName":135,"taxonomyType":110,"taxonomyTypeDesc":111},[168,145,169,170,81,137,171,90,172,173,28,91],"meeting notice drafter","notice","content","board","posting","type"]