Government

Use for government and public sector workflows — formal documents, meeting minutes, reporting, procurement, compliance, and inter-department communication.

Security Scan

The skill's instructions align with its stated purpose (government/public-sector document and meeting support); it is instruction-only, requests no credentials or installs, but it implicitly assumes access to organizational calendars/documents which you should explicitly control before enabling.

Purpose & Capability

Name/description (government workflows, documents, meetings, procurement, compliance) matches the SKILL.md content. The actions described (draft memos, prepare briefings, track procurement stages, flag compliance deadlines) are appropriate for this purpose.

Instruction Scope

SKILL.md contains only high-level, legitimate instructions for drafting documents and tracking items. It repeatedly assumes the agent can see deadlines, pending approvals, meetings, procurement status, and document history but does not specify HOW to access that data (no APIs, file paths, or credentials). That assumption should be addressed before use so the agent only accesses data you permit.

Install Mechanism

No install spec and no code files — lowest-risk instruction-only skill. Nothing will be written to disk by an installer in the skill bundle.

Credentials

Skill declares no required environment variables or credentials, which is consistent with an instruction-only helper. However, practical use will likely require access to calendars, document stores, or procurement systems; the skill does not declare or request those credentials/permissions, so you should explicitly provision minimal, scoped access if you enable it.

Persistence & Privilege

always is false (not force-included). disable-model-invocation is false (agent may invoke autonomously), which is normal for skills. The heartbeat behavior implies periodic checks when enabled — review and control when/where heartbeats run and what data they can read.

Assessment

This skill is internally coherent and appears to do what it says (drafting formal documents, preparing briefings, tracking procurement/compliance). Before installing, decide how it will access your organizational data: calendars, document repositories, procurement/tracking systems, and versioned archives. Provide only narrowly scoped permissions (read-only where possible), configure where outputs are stored, and confirm whether the agent will run automatic 'heartbeat' checks; if autonomous runs are enabled, limit their scope and require human review for sensitive actions (submitting filings, sending official correspondence, or releasing procurement decisions).

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