Skill: rithythul/koompi-government (version 0.2.1)

--- name: government description: Use for government and public sector workflows — formal documents, meeting minutes, reporting, procurement, compliance, and inter-department communication. version: "0.1.0" author: koompi tags: - government - public-sector - compliance - procurement - formal-documents --- # Government & Public Sector Skill Assist government ministries, departments, and public institutions with document processing, meeting management, reporting, and inter-department communication. ## Heartbeat When activated during a heartbeat cycle: 1. **Report deadlines approaching?** Weekly/monthly/quarterly reports due in next 3 days → start drafting 2. **Overdue document requests?** Flag any pending approvals or responses past deadline 3. **Meetings in next 48h?** Prepare briefing docs for any without prep materials 4. **Pending procurement items?** Check status, flag bottlenecks 5. **Compliance deadlines?** Filing dates, audit requirements, regulatory submissions 6. If nothing needs attention → `HEARTBEAT_OK` ## Document Types ### Memos / Directives Structure: 1. Organization header 2. Department / institution 3. Reference number and date 4. Subject 5. Review / background 6. Request / recommendation 7. Signature block Tone: formal register. Use proper titles and honorifics. Avoid colloquial language in official documents. ### Reports - **Weekly:** Accomplishments, issues, next week priorities - **Monthly:** KPIs, budget status, milestones, risks - **Quarterly:** Performance review, strategic updates, resource needs - **Annual:** Comprehensive review, next year plan, budget request When drafting: lead with outcomes, not activities. "Achieved X" not "Worked on X." ### Meeting Minutes Structure: date/time/location → attendees with titles → agenda items → discussion per item → decisions made → action items with owners and deadlines. Keep minutes factual. Record what was decided, not everything that was said. ## Meeting Preparation For inter-department or ministerial meetings: 1. **Briefing doc** (1 page max): key talking points, data needed, potential questions 2. **Background:** prior decisions, current status 3. **Position:** what is our department's stance 4. **Anticipated counterpoints** from other departments 5. **Decision items:** what needs approval ## Reporting Weekly summary structure: - Completed work - Issues / concerns - Next week priorities - Items requiring approval Monthly KPI tracking: define metrics per function, track against targets, flag deviations >10%. ## Procurement Workflow Track these stages: requirement → approval → bidding/selection → evaluation → contract → delivery → payment When assisting: track deadlines, prepare comparison matrices, flag compliance issues, generate status reports. Never skip required approvals. ## Inter-Department Communication - Use formal register for official correspondence - Reference prior correspondence by number/date - Include clear action requests with deadlines - CC relevant departments - Maintain a correspondence log ## Compliance - Track regulatory deadlines and filing requirements - Flag upcoming audits and prepare documentation - Maintain document versioning — never overwrite, always append - Archive decisions with date, participants, and rationale


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)