Techtide kubernetes rbac review
Skill TechTideOhio/techtide-harness-kit/skills/kubernetes/techtide-kubernetes-rbac-review
Trust contracts for AI agent skills: JSON Schema risk tiers, tool permissions, deny-by-default egress, approval gates, prompt-injection fixtures, ~28 CI validation gates. Apache-2.0.
npx -y skills add TechTideOhio/techtide-harness-kit --skill techtide-kubernetes-rbac-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use this skill for Kubernetes RBAC, Role, ClusterRole, RoleBinding, ClusterRoleBinding, ServiceAccount, workload identity, or least-privilege review tasks. Trigger when the user asks whether cluster access is too broad, how to grant workload permissions safely, or how to audit RBAC state.
SKILL.md
2.0 KB, 313 tokens by cl100k_base, as published. Nobody here has run it
Kubernetes RBAC Review
Purpose
Review Kubernetes RBAC objects - Roles, ClusterRoles, RoleBindings, ClusterRoleBindings, and ServiceAccounts - against least privilege, namespace scope minimization, and operational safety.
Lean operating rules
- Prefer live cluster evidence (
kubectl auth can-i,kubectl get rolebinding, audit logs) when the active client exposes it; otherwise fall back to official Kubernetes documentation and sanitized user evidence. - Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge cluster-scoped access granted to workloads that only need namespace-scoped access.
- Challenge wildcard verbs (
*), wildcard resources (*), and wildcard API groups (*) unless explicitly justified. - Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
References
Load these only when needed:
- Evidence path and tooling - use when choosing live cluster evidence, confirming MCP capability, or switching to documentation mode.
- Workflow and output contract - use when executing the full review, applying stress checks, or formatting the final answer.
- Official sources - use when you need the detailed Kubernetes documentation list or source notes.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main risks or control gaps,
- the safest next actions,
- the assumptions or blockers that prevent stronger conclusions.