CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/trivy-config

Use for any question or task about scanning infrastructure code for misconfigurations with one tool, including Kubernetes manifests, Terraform, CloudFormation, Helm, ARM and Dockerfiles that run as root, or migrating off tfsec: trivy config with severity gating, .trivyignore suppressions, custom Rego checks and SARIF for GitHub code scanning. Legacy tfsec is in its references.

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, highly actionable skill body with a clean step sequence and exemplary progressive disclosure into verified reference files. The only improvements are tightening citation preambles/References annotations and adding an explicit post-remediation re-scan validation checkpoint.

DimensionReasoningScore

Conciseness

The body is dense with tables and executable commands and explains nothing Claude already knows, but the repeated "Per [docs]" citation preambles and the multi-line link annotations in the References section are trimmable padding, fitting the 4 anchor (efficient with minor over-explanation) rather than the lean 5 anchor.

4 / 5

Actionability

Every section provides copy-paste-ready commands covering the common cases — install/verify, scans with severity filters, JSON/SARIF/JUnit output, .trivyignore and .trivyignore.yaml suppression blocks, a Rego ignore policy, and custom-check invocations — fully matching the executable-and-comprehensive anchor.

5 / 5

Workflow Clarity

Steps 1-7 form a coherent install-to-CI sequence with an explicit install verification ("Verify: `trivy --version`") and a ratchet pattern for severity gating, but there is no explicit re-run-after-remediation checkpoint in the main flow, so it sits at "most checkpoints present" rather than the full feedback-loop anchor.

4 / 5

Progressive Disclosure

The SKILL.md spine is a clear overview and all three bundle files (references/trivy-config.md, references/tfsec-legacy.md, references/tfsec-custom-rules-and-ci.md) exist, are each directly linked and clearly signaled from the spine ("For the full policy file... see"), with the bulk Rego policy and CI YAML appropriately split out one level deep.

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 strong description that explicitly covers both what the skill does and when to use it, with concrete capabilities and abundant natural trigger terms. The only gaps are missing synonyms/file extensions for trigger terms and minor overlap risk with closely related scanner skills.

DimensionReasoningScore

Specificity

"trivy config with severity gating, .trivyignore suppressions, custom Rego checks and SARIF for GitHub code scanning" lists multiple concrete, specific capabilities covering the full scan-gate-suppress-customize-CI workflow, matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

"Use for any question or task about scanning infrastructure code for misconfigurations... or migrating off tfsec" gives an explicit when-clause with concrete triggers, and the colon clause states precisely what the skill does, satisfying both what and when explicitly.

5 / 5

Trigger Term Quality

Natural terms users would say are well covered ("Terraform", "Kubernetes manifests", "CloudFormation", "Helm", "Dockerfiles", "tfsec", "trivy"), but synonyms and file extensions ("IaC", "infrastructure as code", ".tf", "k8s") are absent, which the 5 anchor requires.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly tool-anchored (trivy/tfsec migration) and mostly distinct, but generic IaC-type triggers like "Terraform" and "Kubernetes manifests" could also match a closely related sister scanner skill (checkov-policy is referenced in the body), leaving minor overlap risk rather than minimal.

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

On this page