CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/trivy-config

Runs Trivy's misconfiguration scanner (`trivy config`) against IaC directories to detect security issues across Terraform, CloudFormation, Kubernetes manifests, Helm charts, Dockerfiles, and Azure ARM templates - installs Trivy, scans with severity gating via `--exit-code`, suppresses findings via `.trivyignore` / `.trivyignore.yaml` or inline annotations, extends built-in checks with custom Rego policies, and emits SARIF for GitHub Code Scanning. Trivy is the tfsec successor - the forward path from tfsec per Aqua Security's own migration guidance - and the legacy tfsec workflow (install, custom YAML rules, ignore annotations, migration steps) is kept in references/tfsec-legacy.md. Use when adopting a consolidated IaC scanner for new projects, migrating away from tfsec (or still operating a Terraform-only tfsec stack), or scanning mixed IaC stacks with a single tool.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

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

The body is highly actionable and well-structured with a clean step sequence and proper progressive disclosure to real reference files. It is slightly verbose in spots and lacks an explicit validate-then-suppress checkpoint for the CI gating workflow.

Suggestions

Add an explicit validation checkpoint between scanning and suppressing (e.g. 'review HIGH/CRITICAL findings before adding .trivyignore entries') to strengthen the batch/destructive gating workflow.

Trim the restated capability list in the Overview and condense the Pinned versions prose, since the description already enumerates what the skill does.

Move the date stamp '2026-06-30' into a small note rather than inline table text to keep the pin row scannable.

DimensionReasoningScore

Conciseness

The body is dense and largely lean — flag tables, copy-paste commands, and one-line rationale per section — but the description-level capabilities are partly restated and the Overview/Pinned-versions prose could be trimmed; not a 5 because of minor redundancy.

4 / 5

Actionability

Nearly every section gives executable, copy-paste-ready bash/rego/yaml covering the common cases (install, scan, gate, format, suppress, custom policies, CI), with concrete flags and example values.

5 / 5

Workflow Clarity

The install→scan→gate→format→suppress→custom→CI sequence is clearly numbered, but there is no explicit validate-after-scan checkpoint for the batch/destructive CI gating path (e.g. confirm findings before suppressing), which caps it below 5.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview spine with well-signaled one-level-deep references (references/trivy-config.md for full Rego + CI workflow, references/tfsec-legacy.md), and all referenced files exist; content is appropriately split with easy navigation.

5 / 5

Total

18

/

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.

The description is specific, trigger-rich, and explicitly states both what the skill does and when to use it, with a clear niche around Trivy-as-tfsec-successor. It is on the longer side but every clause carries load-bearing detail.

DimensionReasoningScore

Specificity

Names many concrete actions (install, scan with severity gating, suppress via .trivyignore/.trivyignore.yaml or inline annotations, extend with custom Rego, emit SARIF) with comprehensive coverage across the supported IaC types.

5 / 5

Completeness

Explicitly answers 'what' (installs Trivy, scans with severity gating, suppresses findings, extends with Rego, emits SARIF) and 'when' via a concrete 'Use when adopting... migrating away from tfsec... or scanning mixed IaC stacks' clause.

5 / 5

Trigger Term Quality

Covers natural terms users would say — 'trivy config', 'terraform', 'kubernetes', 'dockerfile', 'helm', 'cloudformation', 'rego', 'sarif', plus the migration-from-tfsec phrasing — including synonyms and tool names.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Trivy config misconfig scanning, tfsec successor) with distinct triggers (trivy config, tfsec migration, mixed-IaC scanning) that minimize overlap with other skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents