Find over-permissive RBAC roles and service-account token abuse paths in Kubernetes using kubectl auth can-i, rbac-police, kubectl-who-can, and rakkess during authorized cluster security reviews.
Installs into .claude/skills of the current project.
Are you the author of Cyber Auditing Kubernetes Rbac Privilege Escalation?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/nexuslinkproductions-cyber-auditing-kubernetes-rbac-privilege-escalatio)
---
name: cyber-auditing-kubernetes-rbac-privilege-escalation
description: "Find over-permissive RBAC roles and service-account token abuse paths in Kubernetes using kubectl auth can-i, rbac-police, kubectl-who-can, and rakkess during authorized cluster security reviews."
hide: true
---
<!-- GENERATED:YURI-CODEX-SKILL-ADAPTER:v1 -->
# YURI skill adapter
Authoritative source: `.claude/skills/cyber-auditing-kubernetes-rbac-privilege-escalation/SKILL.md`
Authoritative source SHA-256: `91dc74138dc4434a09c510e426cb4d8fcdba8d7467da7f9bd7054cca0a9ba472`
Source class: `cyber-armed`
Before acting, read the authoritative source file above completely from beginning to end. If the governed source is absent, run `node _SYSTEM/Scripts/skill-recall.mjs --show cyber-auditing-kubernetes-rbac-privilege-escalation` and read its complete verified output. Follow that source as the skill body; this adapter is a non-authoritative metadata-and-pointer projection.
