eks-security

EKS security hardening and best practices. Use when configuring cluster security, implementing pod security, managing secrets, preparing for compliance audits, hardening infrastructure, scanning containers, or responding to security incidents.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/eks-security/SKILL.md

Quality

Content

68%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, reference-rich skill body with concrete code and commands throughout. Its main weaknesses are verbosity/redundancy across overlapping sections and missing explicit validation checkpoints in the workflows.

Suggestions

Collapse the redundancy between the Quick Start checklist, Security Workflow phases, and the Week-by-Week Roadmap into a single sequenced path, moving detail into the reference files.

Add explicit validation checkpoints to each workflow phase (e.g. verify the API endpoint is private, confirm RBAC with a test binding, re-run kube-bench after changes) to lift workflow clarity above 3.

Move the large ASCII architecture diagram and some inline control details into the references so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Content is largely actionable reference material, but the 600+ line body has notable redundancy — the ASCII diagram, Quick Start checklist, Security Workflow, Roadmap, and Detailed Documentation overlap heavily, so it could be tightened significantly.	3 / 5
Actionability	Abundant copy-paste-ready executable guidance: YAML manifests (ServiceAccount, Namespace, NetworkPolicy, ExternalSecret), kubectl and aws CLI commands, and a Terraform module covering common cases.	5 / 5
Workflow Clarity	The six-phase Security Workflow and incident-response workflow give clear sequences, but validation/checkpoint steps are implicit or absent, and for cluster configuration changes that cap keeps it at 3 rather than 4.	3 / 5
Progressive Disclosure	Real one-level-deep references (cluster-security.md, workload-security.md, secrets-management.md) are clearly signaled with a dedicated Detailed Documentation navigation section, though a large amount of inline content could arguably live in those files.	4 / 5
	Total	15 / 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 what the skill does and gives an explicit 'Use when' clause with multiple natural trigger phrases. Slight room to sharpen the action verbs toward more concrete operations.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('configuring cluster security, implementing pod security, managing secrets, preparing for compliance audits, hardening infrastructure, scanning containers, or responding to security incidents') but each is phrased at a fairly high level rather than the granular action verbs of a 5-anchor.	4 / 5
Completeness	Explicitly answers both what ('EKS security hardening and best practices') and when ('Use when configuring cluster security, ... responding to security incidents') with concrete trigger phrases, matching the 5-anchor pattern.	5 / 5
Trigger Term Quality	Strong natural keywords ('EKS security', 'cluster security', 'pod security', 'compliance audits', 'security incidents') that users would say, though it lacks some synonyms and explicit file/standard extensions a 5 would include.	4 / 5
Distinctiveness Conflict Risk	The EKS-specific scope and concrete trigger list carve a clear niche with minimal overlap risk against other skills.	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 (633 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

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

Reviewed: 2 days 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.