managing-network-policies

Execute use when managing Kubernetes network policies and firewall rules. Trigger with phrases like "create network policy", "configure firewall rules", "restrict pod communication", or "setup ingress/egress rules". Generates Kubernetes NetworkPolicy manifests following least privilege and zero-trust principles.

Quality

83%

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

Quality

Content

77%Weight 40%Scale 1-3

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

A well-structured, concise workflow with validation feedback loops, but it is materially weakened by the absence of any example NetworkPolicy manifest and by a disconnected, partially broken bundle that the body never links into.

Suggestions

Include at least one complete, copy-paste-ready NetworkPolicy YAML example (default-deny + a labeled allow rule) inline, or explicitly reference assets/network_policy_template.yaml from the Instructions.

Wire the body to the bundle: reference scripts/generate_network_policy.py where generation is described, and remove or implement the README-listed files (validate_network_policy.py, deploy_network_policy.sh, example_network_policies/) that do not exist.

Add a verification step that runs `kubectl get networkpolicy -A` and a connectivity test against the applied manifests so the validate-fix-retry loop is fully concrete.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense — numbered instructions, a compact error-handling table, and short examples — without explaining Kubernetes concepts Claude already knows; every section earns its place.	3 / 3
Actionability	It supplies real commands (`kubectl exec`, `calicoctl node status`, `cilium monitor`, `kubectl get pods --show-labels`) but, for a skill whose output is manifests, includes no actual NetworkPolicy YAML example inline and never points to the bundled template or generator script — a key executable detail is missing.	2 / 3
Workflow Clarity	The 9-step sequence includes explicit validation (step 6 'verify connectivity with kubectl exec curl/wget', step 7 'Monitor for blocked traffic') and a feedback loop (step 8 'Iterate on policies: add missing allow rules'), with an error-handling table for recovery — satisfying the validation requirement for potentially destructive policy changes.	3 / 3
Progressive Disclosure	The body is organized into clear sections but never references the existing bundle (assets/network_policy_template.yaml, scripts/generate_network_policy.py), and the bundle READMEs list files (validate_network_policy.py, deploy_network_policy.sh, example_network_policies/) that do not exist — references are present but unsignaled and partially broken.	2 / 3
	Total	10 / 12 Passed

Description

90%Weight 40%Scale 1-3

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, specific description with explicit trigger phrases and a clear Kubernetes niche; its main weakness is the awkward imperative 'Execute use when' phrasing, which violates third-person voice and costs a specificity point.

Dimension	Reasoning	Score
Specificity	Names concrete domain actions ('managing Kubernetes network policies and firewall rules', 'Generates Kubernetes NetworkPolicy manifests following least privilege and zero-trust principles'), which would anchor at 3, but the imperative 'Execute use when' opening uses second-person/imperative voice rather than third person, triggering the required 1-point specificity reduction.	2 / 3
Completeness	It answers both 'what' ('Generates Kubernetes NetworkPolicy manifests following least privilege and zero-trust principles') and 'when' ('Execute use when managing...' plus explicit trigger phrases), satisfying the explicit-trigger requirement to avoid the completeness cap.	3 / 3
Trigger Term Quality	Explicit natural triggers are provided — 'create network policy', 'configure firewall rules', 'restrict pod communication', 'setup ingress/egress rules' — matching the anchor for good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	The Kubernetes NetworkPolicy niche with k8s-specific triggers (ingress/egress rules, pod communication) is distinct and unlikely to fire for unrelated skills, though 'firewall rules' adds minor breadth.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/devops/network-policy-manager/skills/managing-network-policies/SKILL.md
Commit: c4eafaf

Reviewed: 5 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.