container-security-auditor
Container Security Auditor - Auto-activating skill for Security Advanced. Triggers on: container security auditor, container security auditor Part of the Security Advanced skill category.
36
Quality
3%
Does it follow best practices?
Impact
99%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/04-security-advanced/container-security-auditor/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that provides almost no useful information for skill selection. It merely restates the skill name and category without describing any concrete capabilities, use cases, or natural trigger terms. Claude would have no meaningful basis to select this skill over others when a user needs container security auditing.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Scans container images for vulnerabilities, analyzes Dockerfiles for security misconfigurations, audits Kubernetes pod security policies, detects exposed secrets in container configurations.'
Include a 'Use when...' clause with natural trigger terms like 'Docker security', 'container vulnerabilities', 'image scanning', 'Kubernetes security', 'CVE detection', 'Dockerfile audit'.
Remove the redundant trigger term repetition and replace with diverse, user-natural keywords covering common variations users would actually say when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Container Security Auditor' is just a name, not a description of what the skill actually does. There are no verbs describing capabilities like 'scans', 'analyzes', 'detects vulnerabilities', etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only states the skill name and category membership without explaining capabilities or providing explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'container security auditor' repeated twice. This is the skill name itself, not natural keywords users would say. Missing terms like 'Docker', 'Kubernetes', 'container vulnerabilities', 'image scanning', 'CVE', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'container security' does provide some domain specificity that distinguishes it from general security skills. However, without concrete actions described, it could still conflict with other container or security-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially an empty placeholder with no actual content. It describes what a container security auditor skill should do but provides zero actionable guidance, no concrete tools or commands, and no actual security auditing techniques. The entire content could be replaced with a single sentence without losing any information.
Suggestions
Add concrete container security scanning commands (e.g., trivy, grype, docker scan) with executable examples
Include a step-by-step workflow for auditing container images: pull -> scan -> analyze findings -> remediate -> verify
Provide specific Dockerfile security checks with good/bad examples (e.g., running as non-root, minimal base images, no secrets in layers)
Add references to detailed guides for specific areas like Kubernetes pod security, registry scanning, or runtime security monitoring
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual container security content. | 1 / 3 |
Actionability | There is zero concrete guidance - no commands, no code, no specific tools, no actual container security techniques. The skill describes what it claims to do rather than providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for any container security auditing process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure pointing to detailed materials. There are no references to external files, examples, or deeper documentation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
994edc4
- 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.