ClawAudit verdict

spec-driven-dev

🟢 Trusted

Low risk — reviewed by ClawAudit, behavior matches stated purpose

Accesses credentials AND writes files

Spec-driven development lifecycle workflow using a Git token for cloning and pushing to a user-specified repository — the token is used for its stated purpose of authenticated repository access.

Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

security

transparency

maintenance

What it does

These are capability combinations: each listed behavior occurs in the skill, but ClawAudit detects co-occurrence — it does not verify that one flows into another. Read the code to confirm a live chain.

Capability combination high

Accesses credentials AND writes files — may persist stolen credentials locally

LLM02 · LLM06 · ASI03

Permission integrity

Performs file operations but does not declare file-accessing binaries

file_read+write

Findings (3)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · TOKEN="${SPEC_DEV_GIT_TOKEN}

Pattern match high

Pipe to python — executes piped content as Python code

SKILL.md · prose · downgraded · | Python

Pattern match medium

Python os.getenv — reads environment variable

sub-skills/cr-code-gate/SKILL.md · code · os.getenv(

Permissions & capabilities

Requires 1 environment variable. (1 sensitive: SPEC_DEV_GIT_TOKEN). Requires 1 system binary. (1 elevated: git).

file_writecredential_access

I installed anyway

Check another skill Browse the registry Auditing your own skills or configs? Use the API