CtrlK

kubernetes-rbac-analyzer

Kubernetes Rbac Analyzer - Auto-activating skill for Security Advanced. Triggers on: kubernetes rbac analyzer, kubernetes rbac analyzer Part of the Security Advanced skill category.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill kubernetes-rbac-analyzer

What are skills?

Overall
score

19%

Review — 4%

Does it follow best practices?

Validation — 11 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Activation

This description is essentially a placeholder with no substantive content. It merely repeats the skill name as trigger terms and assigns a category, but provides zero information about what the skill actually does or when it should be used. This would be nearly useless for Claude to make informed skill selection decisions.

Suggestions

Add specific capabilities the skill performs, such as 'Analyzes Kubernetes RBAC configurations, identifies overly permissive roles, audits service account permissions, and detects privilege escalation risks'.

Include a 'Use when...' clause with natural trigger scenarios like 'Use when reviewing cluster security, auditing role bindings, checking service account permissions, or analyzing RBAC policies'.

Add common user terms and variations: 'k8s', 'RBAC', 'role-based access control', 'ClusterRole', 'RoleBinding', 'service accounts', 'permissions audit'.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions - only the skill name repeated and a category label. There is no indication of what the skill actually does (e.g., 'analyzes RBAC policies', 'identifies permission gaps', 'audits role bindings').	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent guidance.	1 / 3
Trigger Term Quality	The only trigger terms listed are 'kubernetes rbac analyzer' repeated twice. Missing natural user terms like 'RBAC', 'role-based access control', 'permissions', 'cluster roles', 'service accounts', 'k8s security'.	1 / 3
Distinctiveness Conflict Risk	The term 'kubernetes rbac' is fairly specific to a niche domain, which provides some distinctiveness. However, without describing actual capabilities, it could still conflict with other Kubernetes security tools.	2 / 3
	Total	5 / 12 Passed

Implementation

This skill is essentially a placeholder template with no actual content about Kubernetes RBAC analysis. It contains only generic descriptions of what a skill should do without any concrete guidance, code examples, kubectl commands, or security analysis workflows. The content provides zero value beyond what Claude already knows.

Suggestions

Add concrete kubectl commands for RBAC analysis (e.g., `kubectl auth can-i --list`, `kubectl get rolebindings -A -o yaml`)

Include specific examples of RBAC misconfigurations to look for (overly permissive ClusterRoleBindings, wildcard permissions, service account abuse patterns)

Provide a clear workflow: 1) Enumerate roles/bindings, 2) Identify risky permissions, 3) Generate findings report with severity ratings

Add example output format showing how to present RBAC analysis findings with remediation recommendations

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing specific about Kubernetes RBAC analysis. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need.	1 / 3
Actionability	No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually analyze RBAC configurations, what tools to use, or what output to expect.	1 / 3
Workflow Clarity	No workflow is defined. There are no steps for analyzing RBAC, no validation checkpoints, and no sequence of operations. The 'step-by-step guidance' mentioned is never actually provided.	1 / 3
Progressive Disclosure	The content is a flat, uninformative document with no structure beyond generic headings. There are no references to detailed materials, examples, or related documentation that would help with actual RBAC analysis.	1 / 3
	Total	4 / 12 Passed

Validation

69%

Warnings & errors only

Validation — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow	Warning

	Total	11 / 16 Passed

Reviewed: 22 days ago

Table of Contents

Activation Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.