redhat-et

Create or update a competitive intelligence profile for a company in the Physical AI space

Check preferred sources for new Physical AI content in last 30 days

Refresh company intelligence reports and generate cross-company trend analysis

Compare OSS projects and proprietary solutions for a building block, with Red Hat pick recommendation

Evaluate community health, governance, and sustainability of an OSS project

Evaluate technical architecture, code quality, dependencies, and platform fit of an OSS project

Map content to building blocks and update cross-references

Evaluate community health, openness, and governance of an open-source project

Perform root cause analysis and log analysis for failed jobs. Use when user wants to investigate job failures, analyze logs, find root causes, debug errors, troubleshoot infrastructure issues, or understand why a job failed. Investigate AAP job failures using Splunk correlation and AgnosticD/AgnosticV configuration analysis. Correlates local Ansible/AAP job logs with Splunk OCP pod logs and retrieves relevant configuration from GitHub repositories.

Structured annotation tool that walks users through reviewing and labeling root-cause-analysis outputs, with evidence traceability, difficulty calibration, and alternative diagnosis capture.

Ask user if they would like to provide feedback. Call scripts/formatting.py. Don't ask any follow up questions.

Perform root cause analysis and log analysis for failed jobs.Investigate AAP job failures using Splunk correlation and AgnosticD/AgnosticV configuration analysis. Correlates local Ansible/AAP job logs with Splunk OCP pod logs and retrieves relevant configuration from GitHub repositories.

Perform root cause analysis and log analysis for failed jobs. Investigate AAP job failures using Splunk correlation and AgnosticD/AgnosticV configuration analysis. Correlates local Ansible/AAP job logs with Splunk OCP pod logs and retrieves relevant configuration from GitHub repositories.

Perform root cause analysis and log analysis for failed jobs. Use when user wants to investigate job failures, analyze logs, find root causes, debug errors, troubleshoot infrastructure issues, or understand why a job failed. Investigate AAP job failures using Splunk correlation and AgnosticD/AgnosticV configuration analysis. Correlates local Ansible/AAP job logs with Splunk OCP pod logs and retrieves relevant configuration from GitHub repositories.

End-to-end incident investigation workflow that fetches logs and performs root cause analysis. Use when a user wants to investigate incidents, analyze job failures, fetch and analyze logs in one workflow, or debug infrastructure issues. Combines log-fetcher, root-cause-analysis and context-fetcher into a unified pipeline.

Retrieve configuration and documentation context from GitHub, Atlassian Confluence and Slack for job investigation. Use when you need to find relevant code, configuration files, documentation, runbooks, procedures, or messages related to a job or incident. You must use feedback-capture skill at the end

Pull skills dynamically via the skill-puller sidecar

Audit checklists for consistency against a corporate standard. Identifies gaps, inconsistencies, and missing steps. Use when verifying process documents across departments.

Compare policy documents side by side. Produces a structured comparison matrix. Use when analyzing policies from multiple sources against a baseline.

Screen resumes against a job description. Scores candidates on qualification alignment, experience match, and fit. Use when HR uploads resumes for a job opening.

Review code files for bugs, style, and security issues

Fetch a URL and produce a structured summary

Convert PDF documents to text and summarize them

Compiles executive briefings from multiple source documents. Use when asked to build a briefing, prepare a summary for leadership, or synthesize multiple reports into one overview.

Composes professional email responses based on context and recipient. Use when asked to draft, compose, or reply to an email, message, or written communication.

Extracts action items, decisions, and follow-ups from meeting notes. Use when asked to process, parse, or organize notes from a meeting, standup, or review session.

Reviews technical documents for clarity, completeness, and consistency. Identifies gaps, ambiguities, and structural issues. Use when asked to review, critique, or provide feedback on a document before sharing or publishing.

Summarizes technical documents, RFCs, design specs, and long-form content into structured, actionable summaries with key decisions, open questions, and action items. Use when asked to summarize, condense, or extract highlights from a document.

A simple example skill that greets the user. Use this as a template for creating new skills.

Analyzes Kubernetes manifests for security posture, threat modeling, and attack path identification. Use when reviewing manifests for security risks beyond simple lint checks. This skill identifies compound vulnerabilities where multiple misconfigurations create exploitable attack chains: privilege escalation paths, defense-in-depth violations, lateral movement vectors, secret exposure, and blast radius analysis. Applies NSA/CISA hardening guidance, MITRE ATT&CK for Containers, CIS Kubernetes Benchmark, and Pod Security Standards.

Runs comprehensive Kubernetes manifest linting with kube-linter, kubeconform, and pluto. This skill should be used when the user wants to validate K8s manifests. Validations can include best practices, schema correctness, deprecated APIs, and security issues. Aggregates results from multiple linters into a unified, filterable output format. Use for pre-commit validation, CI/CD integration, or comprehensive manifest audits.

Use when validating Kubernetes manifests against compliance frameworks (CIS Kubernetes Benchmark, Pod Security Standards, PCI-DSS, HIPAA, SOC2, NIST). Use when generating compliance reports, audit evidence, or mapping controls to regulatory requirements. Use when preparing for audits, assessing compliance gaps, or explaining why specific security controls are required by regulation. Use when determining Pod Security Standards levels (Restricted/Baseline/Privileged).

Use when reviewing Kubernetes manifests for resource cost implications, overprovisioning waste, reliability gaps (single replica, no PDB, missing anti-affinity), or cost-vs-reliability tradeoff decisions. Use when someone asks "how much does this cost?" or "is this production-ready?"

Use when reviewing, creating, or modifying Kubernetes manifests that contain multiple resources. Use when Services, Deployments, ConfigMaps, Secrets, RBAC resources, Ingress, Routes, or NetworkPolicies appear together. Use when manifests reference other resources by name, label selector, or service account. Use when debugging why pods aren't receiving traffic, why containers fail to start, or why RBAC permissions aren't working.

Use when reviewing Kubernetes manifests to validate design intent and architectural decisions. Use when manifests contain unexplained port exposure, single-replica production deployments, multi-container Pods, unusual update strategies, or any configuration where the WHY behind a decision is unclear. Use when creating new manifests to ensure the author has thought through architectural tradeoffs. Use when multi-container Pods need pattern classification (sidecar, init, ambassador, adapter). Use when manifests show signs of anti-patterns like stateful Deployments, sidecar sprawl, or distributed monoliths.

Check currently firing Grafana alerts, analyze alert status, and investigate alert issues in the Kagenti platform

Query and analyze logs using Grafana Loki for the Kagenti platform, search for errors, and investigate issues

Query Prometheus metrics, check resource usage, and analyze platform performance in the Kagenti platform

Investigate platform incidents, perform RCA, create incident documentation, and follow alert runbooks in the Kagenti platform

Check comprehensive platform health including ArgoCD apps, pods, services, certificates, and resources across the Kagenti platform

Generate a structured campaign brief for a marketing initiative

Build a multi-channel content calendar for a planning period

Summarize a long document into a 1-page executive brief

Produce a structured budget-vs-actual variance analysis

Generate role-specific onboarding checklists for new hires

Translates Kyverno policies to OPA Gatekeeper ConstraintTemplates and Constraints with RHACM PolicyGenerator output.

Deploys OPA Gatekeeper policies for BSI IT-Grundschutz compliance (SYS.1.6 Containerisation, APP.4.4 Kubernetes) following ch-stark patterns with BSI requirement labels.

Interactive Rego policy generator assistant. Analyzes requirements, recommends admission controllers (Gatekeeper/Kyverno/VAP), generates Rego code, validates with OPA, and creates RHACM-ready constraint files.

Deploys OPA Gatekeeper policies for NIST SP 800-53 compliance following ch-stark/gatekeeper-examples patterns. Adds NIST control labels and annotations to all constraints for compliance tracking.

Automates OPA Gatekeeper integration with RHACM following ch-stark/gatekeeper-examples. Reads cluster version via MCP, compares gatekeeper-library policies against OpenShift SCCs, and generates optimized PolicyGenerator with SCC-filtered library inclusion.

Communicate with agents on other OpenClaw instances via A2A protocol

Query the National Park Service agent for park information

Run E2E verification of the Browser Use Chrome extension against real websites. 3-tier system: Tier 1 (surgical single-ATS, 3-5min), Tier 2 (full LinkedIn flow, 15min), Tier 3 (batch 15 jobs, 60min). OpenClaw acts as passive commander while the extension autonomously executes.

Structured E2E test result tracking for the Browser Use extension heartbeat loop. After each E2E run, write a structured JSON result, validate it, and auto-aggregate per-provider benchmarks and failure trends. Use when: an E2E test completes and needs recording, checking E2E trends, querying "which ATS providers are failing", reviewing benchmark history, or when the heartbeat loop reports E2E results. Triggers on: "record E2E result", "E2E observability", "benchmark status", "ATS provider history", "failure trends", "what's failing", "E2E summary".