Use when reviewing tests or test changes in a diff, pull request, or merge request. Triggers on assessing test quality, spotting test anti-patterns, or evaluating whether an assertion earns its place.
Generate the periodic "unsolved Checkmk check crashes on 2.4+" Slack rollup, grouped by component owner. Composes the crash-report and component-owners skills and emits Slack-ready plain text (no markdown).
Queries and reads crash reports from crash.checkmk.com
Create a Jira ticket in CMK with component, team, and epic matched from compass and roadmap data
Fetch and display a Jira ticket's description, comments, attachments, and linked tickets
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Interacts with Gerrit code review to list changes and improve them
This skill should be used when Claude discovers a potential security vulnerability in existing code, during a code review, or when asked to assess a security finding. Triggers on phrases like "is this a vulnerability", "security issue", "security finding", "could this be exploited", "is this safe", or when code patterns suggest injection, path traversal, XSS, auth bypass, privilege escalation, SSRF, or other OWASP-class issues.