Menu
Scans Founder OS plugin deployment, scores coverage by business area, and produces an actionable automation scorecard. Used by /audit:scan and /audit:report commands.
Loads structured business context files into plugin execution context. Activates at the start of any plugin command to provide business knowledge, current strategy, and operational data. Plugins inline the loading logic directly (same pattern as gws CLI usage).
Read Google Calendar events and check availability using gws CLI. Use this skill when any Founder OS plugin needs to list events, check schedules, or query free/busy status — replaces Google Calendar MCP server read operations.
Create, update, and delete Google Calendar events using gws CLI. Use this skill when any Founder OS plugin needs to modify calendar events — replaces Google Calendar MCP server write operations.
Search, list, and retrieve Google Drive files using gws CLI. Use this skill when any Founder OS plugin needs to find, read, or export Drive files — replaces Google Drive MCP server read operations.
Upload, create, and update Google Drive files using gws CLI. Use this skill when any Founder OS plugin needs to write files to Drive — replaces Google Drive MCP server write operations.
Read Gmail messages and threads using gws CLI. Use this skill when any Founder OS plugin needs to search, list, or retrieve email messages — replaces Gmail MCP server read operations.
| name | automation-audit |
| description | Scans Founder OS plugin deployment, scores coverage by business area, and produces an actionable automation scorecard. Used by /audit:scan and /audit:report commands. |
The automation audit infrastructure detects which of the 30 Founder OS plugins are installed and actively configured, then scores coverage across 9 business areas using weighted metrics from the audit registry.
For each plugin in schema/audit-registry.json:
[directory]/.claude-plugin/plugin.json exists on the filesystem.mcp.json in plugin directory)Founder OS Automation Scorecard
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Plugin Deployment: [X]% ([N]/30 plugins installed)
Area Coverage: [Y]% (weighted by business impact)
By Business Area:
[Area Name] [bar] [%] ([active plugins])
...
Top Gaps:
1. [Area] at [%] — install [Plugin] for +[weight]% boost
2. ...
Scheduled Plugins: [N]/[installed] (see /audit:report for details)
Write audit results to Reports DB:
schema/audit-registry.json — Plugin-to-area mapping with coverage weightsreferences/task-categories.md — Detailed breakdown of what each area covers