From milo-activity
Investigate a cluster incident by systematically checking recent activity, failed operations, and resource changes. Use when the user reports something is broken, asks "what happened", mentions an outage, incident, or error, or wants to understand recent cluster changes.
npx claudepluginhub datum-cloud/claude-code-plugins --plugin milo-activityThis skill uses the workspace's default tool permissions.
Investigate the following incident:
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Investigate the following incident:
$ARGUMENTS
Start by establishing the time window and scope from the description above. If no time window is specified, default to the last 1 hour. If no namespace or resource is specified, search across all namespaces.
Follow your investigation methodology and return a structured report with timeline, key actors, failures, root cause hypothesis, and next steps.