T09 · Insecure Skill Coding Practices
- Location
scripts/validate-collab-payload.py:16- Finding
Sensitive credential values are exposed in validation and CI logs
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is purpose-aligned but should be reviewed because its bundled CI and approval templates can weaken the secrecy and approval safeguards it is meant to provide.
Review and harden this skill before using it in a shared repository: redact secret-scan output before running it in CI, change decision templates to pending or draft by default, pin GitHub Actions to reviewed SHAs, set explicit read-only workflow permissions, disable checkout credential persistence, and only scan user-selected collaboration paths.
scripts/validate-collab-payload.py:16Sensitive credential values are exposed in validation and CI logs
assets/github-workflows/clawcolab-validate.yml:3Pull requests execute contributor-controlled repository scripts
assets/github-workflows/clawcolab-validate.yml:11GitHub Actions dependencies are referenced through mutable version tags
assets/decision-template.md:6Approval record templates default to an already-approved state
The skill claims to coordinate secure collaboration, but it also references local file-content scanning and validation behavior that reads local files directly without clearly advertising that capability. In this context, hidden read behavior is especially sensitive because the skill's own mission involves secrecy boundaries and private local context; undisclosed reads undermine those assurances and may expose confidential material during validation or summarization.
The skill claims to coordinate secure collaboration, but it also references local file-content scanning and validation behavior that reads local files directly without clearly advertising that capability. In this context, hidden read behavior is especially sensitive because the skill's own mission involves secrecy boundaries and private local context; undisclosed reads undermine those assurances and may expose confidential material during validation or summarization.
The skill text instructs the agent to read and write local repository artifacts and to invoke bundled scripts, but it does not declare any explicit tool scope or permissions boundary. In a half-trust collaboration setting, undeclared file access is risky because users may not realize the skill can touch local files or repository state, increasing the chance of unintended disclosure or modification.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
2. **Default to non-sharing**
3. **Share the minimum necessary**
4. **Treat local memory and secrets as private by default**
5. **Do not promote visibility levels without approval**
6. **Record decisions and approvals explicitly**
7. **Prefer structured artifacts over freeform chat**
No suspicious patterns detected.