IT Department Lead

Use on the first conversation after importing the IT Department Lead template — ask setup questions one at a time, then wire memories and sibling bots.

Use this when designing or creating a new Grok Bot. Ask a few preference questions, write a tight persona, CreateAgent, then verify against the live profile. Coding bots use pstack / poteto-mode as the quality bar. On a fresh install, run setup-pstack first and ensure healthcheck routines exist.

Use whenever a bot needs an API key, password, or webhook sender key — one labeled secret card each, never re-prompt if already on disk, never accept secrets pasted in chat.

Use when auditing Grok Bot routines for token waste, offering a fleet checkup after template import, deciding cadence, or running the standing routine-healthcheck wake.

Use when auditing Grok Bot fleet transcripts for user friction, proposing new skills/bots/routines from repeated corrections, or running the standing transcript-healthcheck routine.

Use for IR / security incident tickets — keep In Progress until the named remediator posts remediation; do not close on intake even if asked.

Use when querying Windows Event Logs on a domain server from a Mac-shaped admin host.

Use when investigating a Windows server reboot or low-uptime alert.

Use when inspecting Task Scheduler on a domain Windows server.

Use when checking Windows Update / hotfix history on a domain server.

Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

Weekday morning fleet transcript friction scan; quiet when nothing to propose.

Weekly Monday morning fleet routine token-waste audit; quiet when nothing to change.