This skill should be used when the user asks to "search logs", "check errors", "tail logs", "show recent logs", "find log entries", "correlate events", "list hosts", "log stats", "syslog", "check homelab logs", or mentions system logs, syslog, log analysis, or log intelligence across homelab hosts.
This skill should be used after running cortex action=abuseinvestigate to analyze the resulting evidence bundle. Use when the user asks to assess frustration incidents, evaluate abuse signals, analyze agent or user friction, produce a frustration report, or follow up on abuseinvestigate results.
This skill should be used after running cortex assess hooks [--hook ] (or the underlying hookinvestigate MCP action that produces HookIncidentEvidence) to analyze why a Claude Code/Codex/Gemini hook failed, timed out, misfired, or otherwise degraded the agent session. Use when the user asks to assess hook reliability…
Triage and manage cortex-detected incidents — unacknowledged error signatures, recent notification firings, similar past incidents, and full incident context around a time window. Use whenever the user asks "what errors haven't been addressed", "what's still firing", "have we seen this before", "ack this error"…
Tail or follow cortex service logs from Docker Compose. Use when the user asks for cortex service logs, startup logs, crash logs, plugin deployment logs, Docker logs, or follow mode. This is for the service's stdout/stderr, not client syslog entries.
This skill should be used after running cortex assess mcp (or the underlying cortex sessions mcpinvestigate pipeline that produces McpIncidentEvidence) to analyze why an MCP tool or server call failed, misfired, or confused the agent. Use when the user asks to assess MCP tool reliability, evaluate why a tool call…
This skill should be used when the user asks for a homelab health report, syslog summary, fleet status report, log analysis summary, 'what happened in the last 24 hours', 'show me this week's errors', 'summarize recent activity', or any time-bounded log analysis that should produce a written markdown report.
Search and explore AI/Claude/Codex conversation history stored in cortex. Trigger when: the user asks to "search sessions", "find conversations", "what did I work on", "session history", "past conversations", "ask history", "when did I last use X", "show recent sessions", "list AI projects", "what tools have I used"…
This skill should be used after running cortex assess skill (or the cortex sessions skillinvestigate pipeline that produces PR 3's SkillIncidentEvidence) to analyze whether a Claude Code/Codex/Gemini skill performed well. Use when the user asks to assess skill quality, evaluate why a skill failed or underperformed…
Answer homelab topology and cross-host correlation questions using cortex's graph-backed inventory — what services run on a host, what depends on what, fleet-wide heartbeat state, correlating events across hosts around a point in time, and graph entity/neighborhood/explanation queries. Use whenever the user asks…
Check whether the running cortex Docker container matches the local Compose image. Use when the user asks whether cortex is current, stale, deployed, updated, running the latest plugin image, or needs a restart/recreate after an upgrade. Supports an optional --pull mode for Docker image comparison.