CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

container-audit

Audit container images, Dockerfiles, and Kubernetes manifests for misconfigurations, excessive privileges, exposed secrets, and runtime risks. Use when the user mentions 'container security,' 'Docker security,' 'Dockerfile audit,' 'Kubernetes security,' 'K8s security,' 'pod security,' 'container hardening,' 'kubectl audit,' 'image scanning,' 'distroless,' 'rootless containers,' 'pod security policy,' 'pod security standards,' 'PSS,' 'network policy,' 'OPA Gatekeeper,' 'Kyverno,' 'runtime security,' or needs to review container or orchestration security.

Quality

96%

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

92%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.

An exemplary audit skill: maximal-density checklists with per-item grep patterns, copy-paste commands, a rigorous verdict/refutation workflow with validation checkpoints, and clean one-level-deep reference structure with all links resolving. The only slack is minor — an unlinked standards list at the end and a few rationale clauses restating common knowledge — which keeps conciseness at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is dense and checklist-driven with grep patterns and rationale instead of padding, and version-sensitive details (PSP deprecation, MPTCP per-netns behavior) are framed as deprecation notes or deferred to references. It falls short of the 5 anchor because of minor trimmable content: the closing References section lists standards (CIS, NSA/CISA, OWASP, MITRE ATT&CK) without links or use instructions, and a few clauses restate knowledge Claude already has ('K8s Secrets are base64-encoded, NOT encrypted').

4 / 5

Actionability

Fully executable throughout: per-item grep patterns ('grep -rln "privileged: *true" ...'), a copy-paste one-liners block (trivy, kube-bench, git ls-files pipeline), concrete validation commands ('node references/validate-findings.mjs findings.json'), jq redaction commands, and worked fingerprint examples. Not the 4 anchor because commands are complete and cover the common cases rather than having gaps.

5 / 5

Workflow Clarity

The pipeline is clearly sequenced — Authorization → Scope the Audit (numbered) → checklists → 'Verify, then record' → output format — with explicit validation checkpoints: the refutation pass before confirming, findings.json validation, a needs_validation protocol with blocker+plan, and a 'Verify Fixes at Runtime' section with per-fix checks. Checklists cover the complex process; error-recovery feedback loops are present, so the destructive/batch cap does not apply (and the skill is read-only by design).

5 / 5

Progressive Disclosure

The body keeps the working checklists inline and pushes deep material one level deep into references/ with purpose-signaled links ('the refutation pass in references/verification.md', 'the gate in references/severity-calibration.md'); every referenced path (runtime-exposure.md, findings-format.md, verification.md, severity-calibration.md, vendor-severity.md, enrich-advisories.mjs, validate-findings.mjs, to-sarif.mjs, findings.schema.json) exists in the bundle. Navigation is easy and nothing that belongs in a separate file is inlined.

5 / 5

Total

19

/

20

Passed

Description

100%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 model description: concrete capabilities, an explicit 'Use when' clause, and an exhaustive list of natural trigger terms including synonyms and abbreviations. Every dimension sits at the top anchor with no vague or padded language.

DimensionReasoningScore

Specificity

The description names the artifacts ('container images, Dockerfiles, and Kubernetes manifests') and multiple concrete audit targets ('misconfigurations, excessive privileges, exposed secrets, and runtime risks'), matching the comprehensive multi-action anchor. It is not the 4 anchor because coverage of what is audited is complete rather than showing minor gaps.

5 / 5

Completeness

It explicitly answers both questions: the first sentence states what the skill does, and 'Use when the user mentions ... or needs to review container or orchestration security' states when, with concrete trigger phrases. This mirrors the 5 anchor's structure exactly; a 4 would require the 'when' clause to be less explicit than it is.

5 / 5

Trigger Term Quality

It lists ~20 natural trigger phrases including synonyms and abbreviations users actually say: 'container security,' 'Docker security,' 'K8s security,' 'pod security,' 'kubectl audit,' 'distroless,' 'rootless containers,' 'PSS,' 'network policy,' 'OPA Gatekeeper,' 'Kyverno.' Both long forms and short forms appear ('pod security policy' and 'pod security standards' alongside 'PSS'; 'Kubernetes security' alongside 'K8s security'), so nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — container/orchestration-layer security — and triggers like 'distroless,' 'PSS,' 'Kyverno,' and 'OPA Gatekeeper' belong to no other skill domain. 'Image scanning' and 'runtime security' carry at most token overlap with adjacent skills, which stays within 'minimal conflict risk.'

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

briiirussell/cybersecurity-skills

Path

skills/container-audit/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.