Back to skill
v1.0.0

Helm Chart Auditor

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 6:40 AM.

Analysis

This is a coherent, instruction-only Helm chart review skill; its file reads and linting commands match the audit purpose, though users should avoid exposing real secrets in chart values.

GuidanceThis skill appears safe for its stated purpose. Use it on Helm charts you intend to review, ensure Helm is installed if you want linting, and redact any real secrets from values.yaml or template files before sharing them with the agent.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Tool Misuse and Exploitation
SeverityLowConfidenceHighStatusNote
SKILL.md
cat Chart.yaml 2>/dev/null
cat values.yaml 2>/dev/null | head -50
ls templates/ 2>/dev/null
helm lint . 2>&1

The skill instructs the agent to read local Helm chart files and run Helm linting. These actions are purpose-aligned and scoped, but users should notice that the skill can inspect local project contents.

User impactThe agent may read files in the chart directory and run a local Helm validation command as part of the audit.
RecommendationRun it only in the intended chart directory and review any chart files that may contain sensitive values before asking for an audit.
Agentic Supply Chain Vulnerabilities
SeverityInfoConfidenceHighStatusNote
metadata
Required binaries (all must exist): none

The SKILL.md workflow references `helm lint`, but the registry requirements do not declare Helm as a required binary. This is a minor setup metadata gap rather than hidden code or an unsafe installer.

User impactThe linting step may not work unless Helm is already installed locally.
RecommendationTreat Helm as an expected local tool for full functionality, and prefer skills that declare such dependencies explicitly.
Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Memory and Context Poisoning
SeverityLowConfidenceHighStatusNote
SKILL.md
cat values.yaml 2>/dev/null | head -50

values.yaml can contain secrets or environment-specific configuration. Inspecting it is expected for a Helm security audit, but it may place sensitive chart data into the agent's working context.

User impactSecrets or private deployment settings in Helm values could be included in the conversation or analysis.
RecommendationRedact real passwords, tokens, and production-only secrets from chart values before sharing them with the agent.