Menú
Inspect Mac host speed risks and Agentic OS generated-artifact hygiene with observe-only reports and approval-gated cleanup classes.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | os-health |
| description | Inspect Mac host speed risks and Agentic OS generated-artifact hygiene with observe-only reports and approval-gated cleanup classes. |
Use when the user asks to investigate a sluggish Mac, heavy indexing, OrbStack or runtime pressure, stale worktrees, or Agentic OS-generated logs, runs, artifacts, and worklogs.
Canonical program: harness/shared_factory/00-programs/host_agentic_os_health/.
harness/shared_factory/00-programs/host_agentic_os_health/program.md
when present.harness/commands/os-health.md for the command contract.harness/commands/system-tool-registry.md before non-trivial host
inspection or cleanup.Run an observe-only report:
agentic-os health report --root <os-root> --output <work-item>/artifacts/health-report.yml
Review host pressure:
Review Agentic OS pressure:
Separate follow-up actions:
safe-auto: allowed only by an approved policyapproval-required: ask before mutationmanual-only: user/operator handles directlyUse narrower cleanup commands only after their own dry-run report is reviewed.
Report:
Groom rough software ideas into source-backed implementation specs with original intent, capability discovery, tracker hierarchy, QA, Gherkin, and Notion documentation projection.
Append environment variables to ~/.zshenv on bigmac, genomesbox, and the Mac laptop in one step. Use when the user pastes `KEY=value` pairs and asks to add them to zshenv, or when setting secrets that need to be available on all three hosts. ssh aliases `bigmac`, `genomesbox`, and `mac` are already configured where needed.
Commit all local changes in logical groups until the repository is clean. Use when the user asks to commit everything, make all needed commits, or cleanly commit the full worktree without pushing.
Help users operate the published Composio CLI to find the right tool, connect accounts, inspect schemas, execute tools, subscribe to trigger events with `composio listen`, script workflows with `composio run`, and call authenticated app APIs with `composio proxy`. Use when the user asks how to do something with `composio`, wants to run a known tool slug, needs to discover a slug with `composio search`, fix a missing connection with `composio link`, inspect tool inputs with `--get-schema` or `--dry-run`, troubleshoot top-level CLI flows, or explicitly needs `composio dev` guidance.
Use when the user wants to work a LOS Jira ticket or non-trivial LOS task in a dedicated fast worktree, especially when they mention /workon, /orchestrate, fast worktree, use a worktree, or parallel agents.
Use when working or resuming LOS Jira implementation in a fast worktree with minimal chat output, especially after noisy /workon loops, repeated stack setup, test polling, or context/token burn.