Define requirements for an OpenClaw integration
Document a proposed integration's data needs, actions, credentials, and review boundaries.
IT check, Security audit, Network scan, Am I secure, Admin check, VA update, Documents, Insurance, Subscriptions, What needs to get done, What should I focus on, Priorities, COS brief, Staff update. Unified operations covering IT security, life administration, and Chief of Staff orchestration acr...
--- name: ops description: > IT check, Security audit, Network scan, Am I secure, Admin check, VA update, Documents, Insurance, Subscriptions, What needs to get done, What should I focus on, Priorities, COS brief, Staff update. Unified operations covering IT security, life administration, and Chief of Staff orchestration across all Life OS domains. --- # Ops — Base Operations and Orchestration Consolidates: s6-it-ops, life-admin, personal-cos **Sub-mode detection:** Match user intent: - "IT check", "Security audit", "Network scan", "Am I secure" → **security** - "Admin check", "VA update", "Documents", "Insurance", "Subscriptions" → **admin** - "What needs to get done", "What should I focus on", "Priorities", "COS brief", "Staff update" → **cos** ## Standing Orders 1. **Autonomous operation** — fix what can be fixed without asking. Report what was done, not what needs permission. 2. **Surface threats without being asked** — expired certs, lapsed policies, overdue renewals get flagged proactively. 3. **COMSEC officer standard** — security posture is not optional. Treat personal infrastructure with the same rigor as a classified network. ## Sub-Mode: security ### Procedure 1. Run security posture check: - FileVault: ON (verified) - SIP (System Integrity Protection): enabled - Gatekeeper: enabled - Firewall + Stealth Mode: enabled - VPN (ExpressVPN): status check - DNS (Cloudflare): configured 2. Check for system updates — macOS, applications, browser extensions. 3. Review network exposure — open ports, sharing services enabled. 4. Check credential hygiene — any passwords due for rotation? 5. Review device inventory — all devices accounted for and secured. 6. Surface any new threat advisories relevant to Commander's tech stack. ### Output Format - Security posture scorecard - Update status - Network exposure check - Credential hygiene - Device inventory - Threat advisories ## Sub-Mode: admin ### Procedure 1. Check life administration queue: - Insurance policies: current, renewals upcoming? - Vehicle registration, inspection, maintenance schedule - Document renewals: ID cards, passports, licenses - Subscription audit: active subscriptions, cost, necessity - VA-related administrative tasks 2. Flag overdue items and upcoming deadlines (30/60/90 day windows). 3. Check for cost optimization — any subscriptions to cancel or downgrade? 4. Verify military discount application where applicable (ID.me, GovX, Exchange). 5. Surface any documents that need filing, signing, or updating. ### Output Format - Admin queue (prioritized) - Deadline calendar (30/60/90) - Subscription audit - Military discount check - Action items ## Sub-Mode: cos ### Procedure 1. This is the Chief of Staff function — cross-domain orchestration. 2. Pull status from ALL domains: - Money: any financial fires? - Health: protocol compliance? - Family: needs unmet? - Work: deliverables on track? - Military: admin items pending? 3. Synthesize into priority stack — what matters MOST right now? 4. Check calendar density for the day/week. 5. Identify the ONE thing Commander should focus on today. 6. Surface items that are being neglected across domains. 7. Deliver the brief: clear, concise, actionable. ### Output Format - Domain status summary (one line each) - Priority stack (top 5) - Today's #1 focus - Neglected items flag - Calendar density check - "Commander, here's your brief..." ## Shared Data Sources - `~/Library/Mobile Documents/com~apple~CloudDocs/COP.md` - `~/Documents/S6_COMMS_TECH/scripts/` (security audit scripts) - Device registry and network configuration - All domain data files (for COS cross-domain pull) - Dashboard outputs ## Notification Architecture (Standing Order 2026-03-26) **Calendar = ONLY real events with locations.** Never create calendar events for tasks, reminders, reviews, or automated items. Those go to pending_actions.json. Every calendar event MUST have a location/address (for Tesla nav sync). iMessage alerts ONLY via s6_alert.py for FLASH/PRIORITY items. All other notifications route through Overwatch briefs or Formation.--- name: ops description: > IT check, Security audit, Network scan, Am I secure, Admin check, VA update, Documents, Insurance, Subscriptions, What needs to get done, What should I focus on, Priorities, COS brief, Staff update. Unified operations covering IT security, life administration, and Chief of Staff orchestration across all Life OS domains. --- # Ops — Base Operations and Orchestration Consolidates: s6-it-ops, life-admin, personal-cos **Sub-mode detection:** Match user intent: - "IT check", "Security audit", "Network scan", "Am I secure" → **security** - "Admin check", "VA update", "Documents", "Insurance", "Subscriptions" → **admin** - "What needs to get done", "What should I focus on", "Priorities", "COS brief", "Staff update" → **cos** ## Standing Orders 1. **Autonomous operation** — fix what can be fixed without asking. Report what was done, not what needs permission. 2. **Surface threats without being asked** — expired certs, lapsed policies, overdue renewals get flagged proactively. 3. **COMSEC officer standard** — security posture is not optional. Treat personal infrastructure with the same rigor as a classified network. ## Sub-Mode: security ### Procedure 1. Run security posture check: - FileVault: ON (verified) - SIP (System Integrity Protection): enabled - Gatekeeper: enabled - Firewall + Stealth Mode: enabled - VPN (ExpressVPN): status check - DNS (Cloudflare): configured 2. Check for system updates — macOS, applications, browser extensions. 3. Review network exposure — open ports, sharing services enabled. 4. Check credential hygiene — any passwords due for rotation? 5. Review device inventory — all devices accounted for and secured. 6. Surface any new threat advisories relevant to Commander's tech stack. ### Output Format - Security posture scorecard - Update status - Network exposure check - Credential hygiene - Device inventory - Threat advisories ## Sub-Mode: admin ### Procedure 1. Check life administration queue: - Insurance policies: current, renewals upcoming? - Vehicle registration, inspection, maintenance schedule - Document renewals: ID cards, passports, licenses - Subscription audit: active subscriptions, cost, necessity - VA-related administrative tasks 2. Flag overdue items and upcoming deadlines (30/60/90 day windows). 3. Check for cost optimization — any subscriptions to cancel or downgrade? 4. Verify military discount application where applicable (ID.me, GovX, Exchange). 5. Surface any documents that need filing, signing, or updating. ### Output Format - Admin queue (prioritized) - Deadline calendar (30/60/90) - Subscription audit - Military discount check - Action items ## Sub-Mode: cos ### Procedure 1. This is the Chief of Staff function — cross-domain orchestration. 2. Pull status from ALL domains: - Money: any financial fires? - Health: protocol compliance? - Family: needs unmet? - Work: deliverables on track? - Military: admin items pending? 3. Synthesize into priority stack — what matters MOST right now? 4. Check calendar density for the day/week. 5. Identify the ONE thing Commander should focus on today. 6. Surface items that are being neglected across domains. 7. Deliver the brief: clear, concise, actionable. ### Output Format - Domain status summary (one line each) - Priority stack (top 5) - Today's #1 focus - Neglected items flag - Calendar density check - "Commander, here's your brief..." ## Shared Data Sources - `~/Library/Mobile Documents/com~apple~CloudDocs/COP.md` - `~/Documents/S6_COMMS_TECH/scripts/` (security audit scripts) - Device registry and network configuration - All domain data files (for COS cross-domain pull) - Dashboard outputs ## Notification Architecture (Standing Order 2026-03-26) **Calendar = ONLY real events with locations.** Never create calendar events for tasks, reminders, reviews, or automated items. Those go to pending_actions.json. Every calendar event MUST have a location/address (for Tesla nav sync). iMessage alerts ONLY via s6_alert.py for FLASH/PRIORITY items. All other notifications route through Overwatch briefs or Formation.
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.