docs-workflow
Audited by Socket on Feb 15, 2026
1 alert found:
Security[Skill Scanner] Credential file access detected All findings: [HIGH] data_exfiltration: Credential file access detected (DE002) [AITech 8.2.3] [HIGH] data_exfiltration: Credential file access detected (DE002) [AITech 8.2.3] No evidence of malicious behavior in the provided skill description. The capabilities (reading project files, inspecting git history, creating/updating markdown files) are coherent with a documentation workflow tool. Main security consideration: this skill requires repository read/write and git access — ensure it performs non-destructive operations (show diffs, open PRs) and does not request unrelated credentials before granting repository write access. If the actual implementation later includes remote calls, credential collection, or automatic commits without review, re-evaluate for suspicious behavior. LLM verification: A well-defined documentation workflow tool that is consistent with its stated purpose. The primary risk is potential misinterpretation of config reads as credential access; this should be validated against the actual executable code/files in the repository. Overall, the footprint is BENIGN with a recommended focus on ensuring templates do not inadvertently embed secrets and that placeholder substitution is sanitized.