CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

k8s-security-policies

Implement Kubernetes security policies including NetworkPolicy, Pod Security Admission, and RBAC for production-grade security. Use when securing Kubernetes clusters, implementing network isolation, or enforcing pod security standards.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

Highly actionable reference material with complete, executable YAML and real, clearly-signaled one-level-deep bundle files. Weighed down by boilerplate filler sections that duplicate the description, generic compliance checklists, and the absence of a sequenced apply-and-verify workflow with validation checkpoints.

Suggestions

Delete the 'Instructions', 'Purpose', and 'Do not use this skill when' sections — they restate the description or give generic advice that adds no skill-specific value.

Replace the generic CIS/NIST bullet lists with either concrete control-to-manifest mappings or a short pointer into a reference file, and move the OPA Gatekeeper and Istio sections into their own reference files to slim the SKILL.md overview.

Add an explicit implementation workflow with validation checkpoints (e.g., apply PSA labels → verify with a non-compliant test pod, apply NetworkPolicy → verify isolation, apply RBAC → verify with 'kubectl auth can-i') instead of only reactive troubleshooting.

DimensionReasoningScore

Conciseness

The bulk is lean, copy-paste YAML with no basic-concept explanations, but several sections are pure filler: 'Instructions' ('Clarify goals, constraints, and required inputs. Apply relevant best practices'), 'Purpose' and 'Use this skill when' duplicating the frontmatter, a circular 'Do not use this skill when', and generic CIS/NIST bullet lists ('Implement defense in depth', 'Enable logging and monitoring') Claude already knows. Fits 'mostly efficient but includes some unnecessary explanation' — not score 2, since padding is a minority of the file and the core content is dense.

3 / 5

Actionability

Fully executable, copy-paste-ready examples cover the common cases: complete NetworkPolicy YAML (default deny, frontend-to-backend, DNS egress), Role/ClusterRole/RoleBinding, PSA namespace labels, a hardened Pod securityContext, a full OPA Gatekeeper ConstraintTemplate with Rego, Istio PeerAuthentication/AuthorizationPolicy, and concrete verification commands ('kubectl auth can-i list pods --as system:serviceaccount:default:my-sa'). Matches the anchor-5 'fully executable; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The body is a catalog of example configurations with no explicit implementation sequence — sections imply an order (PSA → NetworkPolicy → RBAC) but no steps are enumerated, and validation exists only reactively in the Troubleshooting section rather than as checkpoints in an apply-verify flow. Applying cluster-wide security policies is risky with no 'verify after applying' step, so this fits 'sequence present but checkpoints missing or implicit' and cannot exceed 3.

3 / 5

Progressive Disclosure

Two real bundle files exist and are clearly signaled twice — inline ('**Reference:** See `assets/network-policy-template.yaml`', 'See `references/rbac-patterns.md`') and in a 'Reference Files' section — and both files contain no nested references, so navigation is one level deep. Not score 5 because sizable content that could live in references (Gatekeeper, Istio, compliance lists) is inlined in a 344-line SKILL.md rather than split out.

4 / 5

Total

15

/

20

Passed

Description

83%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 when to use it, with concrete technology names and explicit trigger phrases. Its only weaknesses are a single-verb action statement and missing common synonyms like 'k8s'.

DimensionReasoningScore

Specificity

Names the domain and enumerates concrete technologies — 'NetworkPolicy, Pod Security Admission, and RBAC' — but relies on a single generic verb ('Implement') rather than multiple distinct actions, and omits covered areas like admission control (OPA/Kyverno) and service mesh security. Matches 'several specific actions; minor gaps in coverage' rather than score 5's comprehensive multi-action coverage, and is well above score 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both: what ('Implement Kubernetes security policies including NetworkPolicy, Pod Security Admission, and RBAC') and when ('Use when securing Kubernetes clusters, implementing network isolation, or enforcing pod security standards') with three concrete trigger phrases — mirroring the anchor-5 example's structure. Not score 4, since the 'when' clause is already explicit and specific rather than needing more detail.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — 'securing Kubernetes clusters', 'implementing network isolation', 'enforcing pod security standards' — but misses common synonyms and variations such as 'k8s', 'network policies', 'RBAC roles', or 'admission control'. Fits 'good keyword coverage; a few natural terms missing' rather than score 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers (pod security standards, network isolation), but 'production-grade security' and Kubernetes generally overlap with closely related skills — the body itself lists 'k8s-manifest-generator' and 'gitops-workflow' as neighbors. Fits 'mostly distinct; minor overlap risk' rather than score 5's minimal conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/k8s-security-policies/SKILL.md

Reviewed

Table of Contents

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.