SKILLEMALL.ai

BB performing-kubernetes-cis-benchmark-with-kube-bench

Turns kube-bench output into a finished CIS Kubernetes Benchmark audit: interpreting PASS/FAIL/WARN per control, judging which failures are genuine on a managed cluster, writing remediation, and packaging evidence for SOC 2 or PCI DSS. Use when conducting a scheduled compliance audit, triaging kube-bench results, deciding which controls are not applicable on EKS, GKE, or AKS, or producing hardening evidence for an auditor. Keywords: CIS Kubernetes Benchmark, control plane, remediation, compliance evidence, SOC 2, PCI DSS, managed cluster exception. Do not use for installing and running the tool - use benchmarking-kubernetes-with-kube-bench.

mukul975/Anthropic-Cybersecurity-Skills Agent Skills author: mukul975 Apache-2.0 8 files · 2 scripts body ≈ 1 453 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Turns kube-bench output into a finished CIS Kubernetes Benchmark audit: interpreting PASS/FAIL/WARN per control, judging which failures are genuine on a…

As a process B 66/100 · Nearly there — weak spots: failures and branches, progress reporting

AnalyzerKubernetesSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
98
Quality 40%
82
Run on models
none yet
Process rating
B
66/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
50
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 2

    ✓ No critical or high findings

    Medium and low: 2
    • low Risky intent intent-offensive-security references/api-reference.md:23
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
      dangerous capabilities (SYS_ADMIN, NET_ADMIN, ALL), privilege escalation.
      detector
    • low Dangerous commands cmd-privilege SKILL.md:61
      Privilege escalation / world-writable permissions (documentation of a security skill)
      sudo mv kube-bench /usr/local/bin/
      security skill

    Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "domain"
    • note frontmatter-key unknown frontmatter key "subdomain"
    • note frontmatter-key unknown frontmatter key "nist_csf"
    • note frontmatter-key unknown frontmatter key "mitre_attack"

    Process rating: all ten parameters 66/100

    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (node) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 14 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1453 tokens
    • 100Running it twice. No mutating operations
    • low 10 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • -43 reference files, but SKILL.md never points to them: the model will not open them
    • -32 of 2 scripts are never mentioned in SKILL.md
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 648: enough signal without eating the budget
    • +4Structure: 19 headings
    • +3Step-by-step instructions: 14 items
    • +3Output format is stated explicitly
    • +4Has examples (10 code blocks)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.