Most static findings are false positives from Markdown examples, inline code, and documented configuration paths. The bundled Graphviz helper uses hardcoded commands and visible file writes, with no evidence of command injection, exfiltration, persistence, or prompt-injection text. A semantic concern remains because the skill teaches dual-use persuasion techniques for increasing agent compliance.
The skill teaches authors to use persuasion principles, strong authority language, and commitment framing to increase AI agent compliance. It includes ethical cautions, but the guidance could be adapted to override agent judgment outside user-approved quality workflows.
The cited files explicitly describe compliance-increasing persuasion techniques and also provide ethical boundaries. Confidence is high for dual-use content but lower than malicious because the stated purpose is quality enforcement.
Most static findings are false positives from Markdown examples, inline code, and documented configuration paths. The bundled Graphviz helper uses hardcoded commands and visible file writes, with no evidence of command injection, exfiltration, persistence, or prompt-injection text. A semantic concern remains because the skill teaches dual-use persuasion techniques for increasing agent compliance.
The skill teaches authors to use persuasion principles, strong authority language, and commitment framing to increase AI agent compliance. It includes ethical cautions, but the guidance could be adapted to override agent judgment outside user-approved quality workflows.
The cited files explicitly describe compliance-increasing persuasion techniques and also provide ethical boundaries. Confidence is high for dual-use content but lower than malicious because the stated purpose is quality enforcement.
Static analysis reported many high-risk patterns, but most occur in markdown examples, documentation links, or terminology and are false positives. The confirmed runtime risk is a bundled Node.js helper that reads files, writes generated diagram files, and invokes Graphviz with a hardcoded command. No evidence found of credential exfiltration, malicious network calls, persistence, or prompt-injection text that tries to override this audit.
Many external-command findings are markdown examples, shell snippets, or inline code used to teach skill creation. They are not automatically executed by the skill.
The cited locations are documentation snippets inside markdown files. They show examples for users and are not executable code paths.
Hidden home-directory paths are used to explain where users may install OpenCode skills. The markdown examples do not read or write those paths automatically.
The paths appear in fenced documentation examples for skill placement. They are not connected to runtime code in the skill body.
Capability review items (3)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The Node.js helper imports child_process and invokes the external Graphviz dot command. The command is hardcoded and receives DOT content through stdin, so command injection was not confirmed, but external tool execution requires user awareness.
The script clearly executes an external binary with execSync. The command string is fixed, which lowers injection risk but still creates runtime dependency and execution risk.
The diagram renderer accepts a skill directory, reads SKILL.md, creates a diagrams directory, and writes SVG and DOT output files. This is legitimate diagram-generation behavior, but it can modify the filesystem where the script is pointed.
The filesystem writes are explicit and tied to documented output generation. No evidence found that it targets sensitive paths unless the user supplies such a directory.
Hardcoded URLs in the documentation point to Anthropic documentation assets and images. No runtime network request code was found in the inspected files.
The URLs are embedded in markdown documentation. They do not constitute automatic data exfiltration or active network code.
Static false positives ignored (1)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
Weak Crypto and C2 Keyword Alerts Are Semantic False Positives
The high-severity keyword alerts appear to match ordinary documentation words, examples, and names inside writing guidance. No cryptographic implementation, beaconing behavior, or command-and-control logic was found.
Inspected context shows skill-authoring prose, not crypto code or malware infrastructure. The finding remains low because it comes from broad keyword matching.
Static analysis reported many high-risk patterns, but most occur in markdown examples, documentation links, or terminology and are false positives. The confirmed runtime risk is a bundled Node.js helper that reads files, writes generated diagram files, and invokes Graphviz with a hardcoded command. No evidence found of credential exfiltration, malicious network calls, persistence, or prompt-injection text that tries to override this audit.
Many external-command findings are markdown examples, shell snippets, or inline code used to teach skill creation. They are not automatically executed by the skill.
The cited locations are documentation snippets inside markdown files. They show examples for users and are not executable code paths.
Hidden home-directory paths are used to explain where users may install OpenCode skills. The markdown examples do not read or write those paths automatically.
The paths appear in fenced documentation examples for skill placement. They are not connected to runtime code in the skill body.
Capability review items (3)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The Node.js helper imports child_process and invokes the external Graphviz dot command. The command is hardcoded and receives DOT content through stdin, so command injection was not confirmed, but external tool execution requires user awareness.
The script clearly executes an external binary with execSync. The command string is fixed, which lowers injection risk but still creates runtime dependency and execution risk.
The diagram renderer accepts a skill directory, reads SKILL.md, creates a diagrams directory, and writes SVG and DOT output files. This is legitimate diagram-generation behavior, but it can modify the filesystem where the script is pointed.
The filesystem writes are explicit and tied to documented output generation. No evidence found that it targets sensitive paths unless the user supplies such a directory.
Hardcoded URLs in the documentation point to Anthropic documentation assets and images. No runtime network request code was found in the inspected files.
The URLs are embedded in markdown documentation. They do not constitute automatic data exfiltration or active network code.
Static false positives ignored (1)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
Weak Crypto and C2 Keyword Alerts Are Semantic False Positives
The high-severity keyword alerts appear to match ordinary documentation words, examples, and names inside writing guidance. No cryptographic implementation, beaconing behavior, or command-and-control logic was found.
Inspected context shows skill-authoring prose, not crypto code or malware infrastructure. The finding remains low because it comes from broad keyword matching.
This is a documentation and reference skill providing guidance on writing AI agent skills. All static findings are false positives - the scanner detected patterns in markdown documentation (code formatting with backticks, mentions of cryptographic terms, URLs in documentation) rather than actual executable code. The render-graphs.js is a build script for documentation generation, not runtime functionality.
21
Files scanned
4,088
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.