CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/trivy-image

Configures and runs Trivy for container image scanning: Aqua Security's all-in-one scanner combining vuln + secret + misconfiguration + license detection in one pass; `trivy image {image}` with --severity HIGH,CRITICAL filter; --format sarif/json (incl. scan-embedded CycloneDX; for standalone SBOM generation see syft-generation + sbom-formats); .trivyignore CVE suppression file; --ignore-unfixed for actionable filter; --scanners vuln/misconfig/license/secret toggle. Use when the team wants a single tool covering container image security across multiple dimensions, not for producing a standalone CycloneDX SBOM.

71

Quality

89%

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

Overview
Quality
Evals
Security
Files

Quality

Content

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

A well-structured, execution-ready skill body: fully executable commands at every step, a clear sequenced workflow with suppression governance, and clean delegation of the CI workflow and tool-composition detail to a real one-level-deep reference file. The only trimmable fat is repeated source citations and slight duplication between the Overview and secret-scanning sections.

DimensionReasoningScore

Conciseness

Mostly lean: terse commands, tables for scanners/formats/anti-patterns, and no explanation of concepts Claude already knows. Not 5: minor padding could be trimmed — "Per [tv-img][tv-img]" is repeated in Steps 2-8, and the Step 6 block-quote largely duplicates the Overview scanner table.

4 / 5

Actionability

Every step is copy-paste-ready executable bash (install paths, scan commands, severity/format/--vex invocations) plus a filled-in .trivyignore example with justification comments. Not 4: the common cases (basic scan, PR gating, suppression) are all covered by concrete runnable commands.

5 / 5

Workflow Clarity

Steps 1-10 are clearly sequenced, with explicit exit-code semantics ("0 = no findings at the configured severity; 1 = findings present") as a validation checkpoint, a mandatory suppression-justification template, and a quarterly audit cadence. Not 5: there is no explicit error-recovery/feedback loop for what to do when a gated scan fails or a finding needs triage.

4 / 5

Progressive Disclosure

SKILL.md is a scan-command spine; the heavy CI workflow YAML and sister-tool composition table are split into references/ci-and-composition.md — one level deep, clearly signaled with markdown links, and the file exists and delivers exactly what is promised. Not 4: nothing that belongs in a separate file is inlined, and navigation is easy.

5 / 5

Total

18

/

20

Passed

Description

88%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 dense, highly specific description that explicitly states both capabilities and a use/disuse boundary, and actively disambiguates against the nearest sibling skills. Keyword coverage is strong though slightly jargon-leaning ("vuln", flag names) rather than natural user phrasing.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "Configures and runs Trivy for container image scanning", "`trivy image {image}` with --severity HIGH,CRITICAL filter", "--format sarif/json", ".trivyignore CVE suppression file", "--scanners vuln/misconfig/license/secret toggle" — with comprehensive coverage from scanning to suppression. Not 4: there are no meaningful gaps in the action coverage.

5 / 5

Completeness

Explicitly answers both what ("Configures and runs Trivy for container image scanning: ... all-in-one scanner combining vuln + secret + misconfiguration + license detection") and when ("Use when the team wants a single tool covering container image security across multiple dimensions, not for producing a standalone CycloneDX SBOM"). Not 4: the when-clause is explicit and concrete, not weakly implied.

5 / 5

Trigger Term Quality

Good keyword coverage ("Trivy", "container image scanning", "secret", "misconfiguration", "CVE", "SBOM", "CycloneDX", "SARIF"), but it abbreviates "vuln" and omits natural phrases users would say like "vulnerability scan" or "security scan". Not 5: a few common synonyms/variants are missing; not 3: the coverage clearly exceeds 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche with an explicit negative boundary ("not for producing a standalone CycloneDX SBOM") and a pointer to syft-generation, disambiguating the closest sibling. Not 5: a sibling trivy-config skill (non-image Trivy use) still overlaps on the bare "Trivy" trigger, leaving minor conflict risk with a closely related skill.

4 / 5

Total

18

/

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.

Reviewed

Table of Contents