debug-scc

Diagnose OpenShift SCC violations by analyzing Deployment, ReplicaSet, Event, and ServiceAccount data.

48|31|Updated Feb 2, 2026

Search Tags:#remediation #OpenShift #diagnosis #SCC #pod creation

Ready to run

npx skills add https://github.com/RHEcosystemAppEng/agentic-plugins --skill debug-scc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-scc
Source: https://github.com/RHEcosystemAppEng/agentic-plugins/tree/main/rh-developer/skills/debug-scc
Command: npx skills add https://github.com/RHEcosystemAppEng/agentic-plugins --skill debug-scc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires resources_get, resources_list, events_list, pods_list, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates the diagnosis of OpenShift Security Context Constraint (SCC) violations that block pod creation, streamlining the process and reducing manual effort.

Core Features & Use Cases

Automated SCC Diagnosis: Identifies and analyzes SCC violations in OpenShift deployments.
Security Context Analysis: Checks pod and container security contexts for compliance with SCCs.
ServiceAccount SCC Binding: Inspects ServiceAccount SCC bindings for proper permissions.
Use Case: Use this skill when pods fail to create due to SCC violations. It will analyze the situation and provide a structured summary with remediation options.

Quick Start

Run /debug-scc <deployment-name> to diagnose SCC violations for a specific deployment.

Frequently Asked Questions about debug-scc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose Security Context Constraint violations blocking pod creation in OpenShift?▼

To diagnose SCC violations blocking pod creation in OpenShift, this skill analyzes Deployment, ReplicaSet, Event, and ServiceAccount data to identify security context issues and provide structured remediation options.

Why do my OpenShift pods fail to create due to SCC violations?▼

OpenShift pods fail to create due to SCC violations when container security contexts or ServiceAccount bindings lack proper permissions. This skill inspects these configurations to pinpoint the exact compliance failures.

Do I need specific MCP tools to troubleshoot SCC violations in OpenShift?▼

Yes, troubleshooting SCC violations requires the openshift MCP servers and specific tools: resources_get, resources_list, events_list, and pods_list to access and analyze the necessary cluster resource data.

What is the best way to check ServiceAccount SCC bindings for OpenShift deployments?▼

The best way to check ServiceAccount SCC bindings for OpenShift deployments is using an automated diagnostic skill that inspects permissions and analyzes security contexts for compliance violations.

How do I run an automated SCC diagnosis for a specific OpenShift deployment?▼

To run an automated SCC diagnosis for a specific OpenShift deployment, execute the /debug-scc command with the deployment name to analyze security contexts and generate remediation options.