Name: eks-irsa
Rating: 67.2 (1 reviews)
Author: fernandezbaptiste

eks-irsa

IAM Roles for Service Accounts (IRSA) for EKS pod-level AWS permissions. Use when configuring pod IAM access, setting up AWS service integrations, implementing least-privilege security, troubleshooting OIDC trust relationships, or deploying AWS controllers.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is eks-irsa in fernandezbaptiste/Skrillz

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured reference with executable examples, real reference files, and clear navigation. Its main weakness is verbosity from repeated near-identical pattern blocks and concept explanations Claude already knows, plus validation that is split off rather than inline.

Suggestions

Collapse the seven near-identical IRSA pattern HCL blocks into one parameterized template plus a compact table of per-controller differences (role name, attach flag, namespace:sa) to recover token budget.

Trim or remove the 'What is IRSA?'/'Key Benefits' Security-Compliance-Operational sections, which restate concepts Claude already knows; keep only IRSA-specific mechanics.

Move inline validation into the Quick Start sequence as explicit numbered checkpoints (e.g., after step 4: verify OIDC provider and trust policy before declaring success) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with extensive executable code, but includes concept explanations Claude already knows ('What is IRSA?', 'Key Benefits' Security/Compliance/Operational bullet lists) and seven near-identical HCL pattern blocks that could be condensed into one template plus a differences table. Above the 2 anchor (padding is sectioned, not a wall) but not 4 because the repetition and educational framing are clearly trimmable.	3 / 5
Actionability	Fully executable, copy-paste-ready code and commands throughout (Terraform HCL, eksctl, kubectl, bash verification, Python/Node/Go SDK examples), with specific examples covering the common IRSA cases, matching the 5 anchor.	5 / 5
Workflow Clarity	Clear sequenced Quick Start (numbered prerequisites + numbered 1-4 setup + dedicated 'Verify IRSA Setup' checkpoint) plus a troubleshooting table and problem/solution blue-green section. Below 5 because inter-step validation is implicit (verify lives in a separate section rather than inline checkpoints), but above 3 since checkpoints are present.	4 / 5
Progressive Disclosure	Good structure with a 'Detailed Documentation' section signaling one-level-deep references (oidc-setup.md, role-creation.md, pod-configuration.md, all real files) each with a content description. Below 5 because substantial material (seven patterns, security practices, app-code examples) is inlined in SKILL.md that could be split out, but clearly above the 3 anchor's 'references present but not clearly signaled'.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states both what the skill does and when to use it, with concrete trigger phrases and a well-defined niche. It is third-person and well-targeted, with only minor room to add synonym variants.

Dimension	Reasoning	Score
Specificity	Names the domain ('IAM Roles for Service Accounts (IRSA) for EKS pod-level AWS permissions') and several concrete actions (configuring pod IAM access, setting up AWS service integrations, implementing least-privilege security, troubleshooting OIDC trust relationships, deploying AWS controllers), with only minor abstraction in the trigger verbs. Not a 5 because the actions are stated as gerund phrases rather than maximally concrete operations, but clearly above the 3 anchor's '1-2 concrete actions'.	4 / 5
Completeness	Explicitly answers both 'what' ('IAM Roles for Service Accounts (IRSA) for EKS pod-level AWS permissions') and 'when' ('Use when configuring pod IAM access, setting up AWS service integrations...') with concrete trigger phrases, matching the 5 anchor exactly.	5 / 5
Trigger Term Quality	Good keyword coverage with natural domain phrases a user would say ('pod IAM access', 'AWS service integrations', 'least-privilege security', 'OIDC trust relationships', 'AWS controllers'); a few natural synonyms are missing and no acronym variants beyond IRSA, so below the comprehensive 5 anchor but above the 'some relevant keywords' 3 anchor.	4 / 5
Distinctiveness Conflict Risk	EKS IRSA is a clear, narrow niche with distinct, specific triggers (OIDC trust relationships, pod IAM access) and minimal overlap risk with other skills, matching the 5 anchor's 'clear niche with distinct triggers'.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (556 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: .claude/skills/eks-irsa/SKILL.md
Commit: 93ed392

Reviewed: 1 day ago

Table of Contents

Discovery 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.