Skill Detail

Bats Testing Patterns

This skill provides guidance on writing unit tests for shell scripts using Bats, including test patterns and best practices.

GitHub:sickn33/antigravity-awesome-skills bats-testing-patterns
version 6702adc9644f
static analysis only
no human review yet
Needs Review

Current public label

Needs Review

The skill includes a destructive shell pattern, so it needs review to ensure it is used safely.

This label is currently coming from the automated scorecard.

Automated result

Needs Review

Driftloom found a destructive shell pattern and determined that the skill is mostly documentation. No runtime evidence was available.

1 high, 1 low Final label: needs review.

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
72
Quality
94
Transparency
100
Operational
92
Maintenance
72

1 high, 1 low Final label: needs review.

Severity mix: 1 high, 1 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.
  • Looked for external URLs and network behavior.
  • Looked for secrets and credential handling clues.
  • Checked whether the skill structure and references looked internally consistent.

Findings

Destructive shell pattern detected
shell.rm_rf · safety
High

Found a hard-delete shell pattern. That deserves human eyes, not optimism.

File: resources/implementation-playbook.md
Evidence: rm -rf
Documentation-only skill structure
structure.docs_only · quality
Low

The source looks almost entirely documentation-based, with no obvious code or config files to inspect. That does not make it bad, but it limits how much automation can meaningfully verify.

File: SKILL.md
Driftloom is following the boring, correct architecture: Django control plane first, isolated runner later. Miraculously, restraint survives.