Skill Detail

Helm Chart Scaffolding

This skill provides guidance for creating and managing Helm charts to deploy Kubernetes applications.

GitHub:sickn33/antigravity-awesome-skills helm-chart-scaffolding
version 108374c4c4e2
static analysis only
no human review yet
Trusted

Current public label

Trusted

The skill's documentation mentions secrets, which is why it is labeled as trusted.

This label is currently coming from the automated scorecard.

Automated result

Trusted

Driftloom found low-severity documentation references to credentials or secrets.

2 low Final label: trusted.

Human review

No human review has been recorded yet.

The current public label is still relying on automation. A human has not weighed in yet.

What happened

Driftloom completed a static scan. It inspected the skill files, recorded findings, and generated a scorecard.

Runtime evidence

No sandbox runtime result has been recorded yet.

What did not happen

  • Driftloom did not run this skill in an isolated sandbox yet.
  • This label is not a guarantee that the skill is safe, bug-free, or appropriate for every environment.
  • A good score does not replace human judgment when a skill touches secrets, shell access, or external systems.

Source provenance

Source: Workspace import

Originally ingested from a local workspace copy.

Scorecard

Safety
88
Quality
100
Transparency
100
Operational
92
Maintenance
82

2 low Final label: trusted.

Severity mix: 2 low

What Driftloom checked

  • Read the skill files and metadata to understand what the skill claims to do.
  • Looked for shell commands and risky command patterns, even if none stood out strongly.
  • Looked for external URLs and network behavior.
  • Looked for secret, token, password, and credential references.
  • Checked whether the skill structure and references looked internally consistent.

Findings

Secret or credential reference detected
secret.reference · safety
Low

The docs mention credentials or secrets. That may be normal, but it still tells you the skill expects sensitive material somewhere in the workflow.

File: references/chart-structure.md
Evidence: secret
Secret or credential reference detected
secret.reference · safety
Low

The docs mention credentials or secrets. That may be normal, but it still tells you the skill expects sensitive material somewhere in the workflow.

File: resources/implementation-playbook.md
Evidence: password
Driftloom is following the boring, correct architecture: Django control plane first, isolated runner later. Miraculously, restraint survives.