Audit History

Static findings are predominantly false positives caused by Markdown code fences, inline backticks, research links, and documentation of local paths. The bundled hook scripts only log event metadata and output lengths; they do not perform network requests, command interpolation, or memory writes. The documented automatic memory workflow still needs privacy controls because it can retain context from many skill events.

Static findings are predominantly false positives caused by Markdown code fences, inline backticks, research links, and documentation of local paths. The bundled hook scripts only log event metadata and output lengths; they do not perform network requests, command interpolation, or memory writes. The documented automatic memory workflow still needs privacy controls because it can retain context from many skill events.

Static findings are predominantly false positives caused by Markdown code fences, inline backticks, research links, and documentation of local paths. The bundled hook scripts only log event metadata and output lengths; they do not perform network requests, command interpolation, or memory writes. The documented automatic memory workflow still needs privacy controls because it can retain context from many skill events.

Static findings are predominantly false positives caused by Markdown code fences, inline backticks, research links, and documentation of local paths. The bundled hook scripts only log event metadata and output lengths; they do not perform network requests, command interpolation, or memory writes. The documented automatic memory workflow still needs privacy controls because it can retain context from many skill events.

Most static external command and network alerts are false positives from Markdown examples, diagrams, and research links. Confirmed risks remain because the community skill uses hidden Claude configuration paths, symlink installation, optional Bash hooks, and broad self-modifying workflows that can persist sensitive session context.

Most static external command and network alerts are false positives from Markdown examples, diagrams, and research links. Confirmed risks remain because the community skill uses hidden Claude configuration paths, symlink installation, optional Bash hooks, and broad self-modifying workflows that can persist sensitive session context.

Static analysis produced many alerts, but most blocker-level items are false positives from markdown examples, diagrams, and research links. The confirmed risk is high because this community skill requests broad file-editing and Bash capabilities, teaches self-modification of skills, and documents hooks that can log tool input and command output.

This is a legitimate Claude Code skill for self-improvement. The static scanner flagged 121 potential issues, but after semantic evaluation, all are false positives. External command detections are markdown backticks in documentation. Network detections are academic reference URLs. Filesystem detections are standard Claude Code config paths. No actual security risks present.