Generate a consolidated health report across multiple OpenShift clusters. Verifies each kubeconfig context is a genuine OpenShift cluster before reporting. Non-OpenShift contexts are skipped by default. Collects node resources (CPU, memory, GPUs), namespace counts, and pod status into a single comparison view. Use when: - "Show me a report across all clusters" - "Compare cluster health" - "Multi-cluster status overview" - "How are my clusters doing?" - "Include all clusters including non-OpenShift" (override default filter) NOT for single-cluster deep-dives or troubleshooting specific pods.

Author and maintain Compass catalog-info.yaml manifests for agentic packs (skills, plugins, Locations, MCP inverse relations). Use when: - Adding or updating a skill and its Compass manifest - Registering an existing pack in Compass (manifests only; not creating a new agentic pack) - MCP usage or orchestration changed in SKILL.md - Auditing bidirectional dependsOn/dependencyOf drift against repo Compass conventions File-based only: Read/Glob/Grep/Bash. For `.catalog/` marketplace metadata use create-collection. NOT for: `.catalog/` metadata (use create-collection) or automated Compass registration.

Interactive skill creation and import with automated validation and marketplace compliance. Use when: - "Create a new skill" - "Import an existing skill" - "Create a new agentic pack" - "Add skill to <pack>" - "Build skill for <rh-product>" - User mentions "skill builder", "contribute", "new skill", "import skill", or "new pack" Two modes: create from scratch or import existing SKILL.md. Guides through discovery, definition, generation, and validation. Enforces SKILL_DESIGN_PRINCIPLES.md and agentskills.io spec.

Autonomous design critique mode using the Agentation annotation toolbar. Use when the user asks to "critique this page," "add design annotations," "review the UI," "self-driving mode," "auto-annotate," or wants an AI agent to autonomously add design feedback annotations to a web page via the browser. Requires the Agentation toolbar to be installed on the target page and agent-browser skill to be available.

Use when the user asks to "create a personality", "make a custom personality", "add a caller persona", "fork a personality", "change the testing agent's voice", "test a different accent", "add an Indian/British/Spanish accent caller", "make the caller interrupt more", "add background noise", "make it speak slower", "the testing agent keeps asking if I'm still there", "simulate a bad connection", or "which personality should I use". Also for questions about the difference between a personality and an evaluator, why instructions like "speak with an accent" or "be interruptive" don't change how the caller sounds, and why a personality's accent field cannot be set directly. Covers choosing, forking, creating and patching personalities — the simulated caller's voice, language, timing and audio layer.

Use when the user asks to create, update, or review a source-controlled Cekura JSON CI/CD test suite for a voice AI repository; create Tests-as-Code specs; turn a voice-agent code change into regression coverage; add deterministic Cekura voice tests to CI; or test an STT, LLM, TTS, VAD, interruption, idle-timer, DTMF, or call-lifecycle pipeline; or set up a CI gate that blocks a merge when the voice pipeline regresses. Inspects the repository before authoring a compact JSON suite, validates it safely against Cekura, and wires the workflow that runs it.

Turn a set of flagged production call logs into evaluator scenarios for a Cekura agent — cluster the failures into reproducible modes and create one scenario per cluster. Use when the user says "create scenarios from failed calls", "build evaluators for prod failures", "turn call logs into scenarios", "simulate the failures we saw in prod", "replay these bad calls as tests", "regression-test the agent on prod issues", or hands over a set of flagged call IDs to harden the agent against. The flagged set normally comes from `cekura-flag-call-log-failures`; if the user hasn't triaged yet, run that skill first. This skill takes the flagged calls as given — it does NOT re-mine or re-triage — clusters by failure mode, drafts one scenario per cluster, and optionally creates them via the scenarios API (or the call-logs → scenarios endpoint). Also supports a single-call fast path: given one call log ID (or an observe URL), reproduce just that call as one evaluator scenario.

Use when a pull request changes a voice agent and the repository's committed Cekura test suite has to keep up: "update the tests for this PR", "extend test coverage for these changes", "does this PR need new voice tests", "keep cekura.tests.json in sync", "add a regression test for this bug fix", "review the suite against my diff", "run a test writer on every PR". Reads the PR diff against its merge base, decides per change whether existing cases already cover it, and makes the smallest edit that closes a real gap — most often no edit at all. This skill updates an existing suite; it never creates one from scratch (use cekura-infra-test-suite), never authors dashboard evaluators (use cekura-eval-design), and never places a live call.

here.now lets agents publish websites and files to live URLs in seconds. Publish HTML, documents, images, PDFs, videos, and static files to live URLs at {slug}.here.now or custom domains. Use when asked to "publish this", "host this", "deploy this", "share this on the web", "make a website", "put this online", "create a webpage", "generate a URL", "build a chatbot", "password protect this site", "make this site private", or "share this site with only certain people". here.now also includes workspaces — shared team accounts where Sites belong to the team and serve at {label}.{workspace}.here.now — use when asked to "publish this to our team workspace", "share this with my team", or "put this in our company workspace". Agents can also buy a domain for a Site through here.now (no markup, DNS and SSL automatic) — use when asked to "buy a domain", "get me a .com for this", or "register a domain".

here.now lets agents publish websites and files to live URLs in seconds. Publish HTML, documents, images, PDFs, videos, and static files to live URLs at {slug}.here.now or custom domains. Use when asked to "publish this", "host this", "deploy this", "share this on the web", "make a website", "put this online", "create a webpage", "generate a URL", "build a chatbot", "password protect this site", "make this site private", or "share this site with only certain people". here.now also includes workspaces — shared team accounts where Sites belong to the team and serve at {label}.{workspace}.here.now — use when asked to "publish this to our team workspace", "share this with my team", or "put this in our company workspace". Agents can also buy a domain for a Site through here.now (no markup, DNS and SSL automatic) — use when asked to "buy a domain", "get me a .com for this", or "register a domain".

Generates architecture diagrams from Azure Bicep files. Use when user has .bicep files or asks to visualize Bicep infrastructure.

This skill should be used when the user asks to "deepen a module", "find shallow modules", "run an architecture review", "open a refactor PR", "improve the codebase architecture unattended", or wants a hands-off run that scans a codebase for deepening opportunities, picks the highest-leverage one, implements it test-first, and opens a PR. Runs end to end with no questions, so it is safe for cron jobs, routines, and headless firings. Also triggered by the /pm-deepen command.

Create GitHub Releases with AI-analyzed changelogs for every calendar day with commits on origin/main. Use when creating daily release notes, backfilling releases, or generating AI-categorized changelogs per day. Uses collect → bucket → analyze → synthesize → publish pipeline via Haiku subagents. Idempotent — skips up-to-date days, updates releases where new commits were added. Accepts optional --start-date, --end-date, --branch, and --dry-run arguments.

Create, update, search, transition, link, and read comments on Jira issues via CLI. MUST use this skill whenever the user pastes or mentions any atlassian.net URL (Jira issues, Confluence pages, focusedCommentId links, board links — anything from *.atlassian.net). Also use for: TSLA-* ticket references, JQL searches, issue status changes, reading comments, creating bugs, updating descriptions. This is the ONLY way to interact with Jira/Atlassian — there is no MCP Atlassian available.

Review API endpoints for security, validation, error handling, and production readiness.

Review backend API endpoints for security, validation, errors, and safe production behaviour.

Review API endpoints for authentication, authorization, input validation, and secure error handling.

Invoke when user asks to do something with Cypilot, or wants to analyze/validate artifacts, or create/generate/implement anything using Cypilot workflows, or plan phased execution. Core capabilities: workflow routing (plan/analyze/generate/auto-config); deterministic validation (structure, cross-refs, traceability, TOC); code↔artifact traceability with @cpt-* markers; spec coverage measurement; ID search/navigation; init/bootstrap; adapter + registry discovery; auto-configuration of brownfield projects (scan conventions, generate rules); kit management (install/update with file-level diff); TOC generation; agent integrations (Windsurf, Cursor, Claude, Copilot, OpenAI).

Artifacts: ADR, CODEBASE, DECOMPOSITION, DESIGN, FEATURE, PR-CODE-REVIEW-TEMPLATE, PR-REVIEW, PR-STATUS-REPORT-TEMPLATE, PRD; Workflows: migrate-openspec, pr-review, pr-status

Multi-repo workspace setup — discover repos, configure sources, generate workspace config, validate