Most static findings are false positives caused by Markdown formatting, documentation examples, benign citations, and mislabeled text. The executable template has medium-risk path traversal, HTML injection, and indirect prompt injection weaknesses. These issues should be fixed before marketplace publication.
Batch and item identifiers are joined without validation. Absolute or traversal paths can redirect writes and cleanup deletions outside intended directories.
The CLI value reaches Path joins without confinement checks, and cleanup unlinks files beneath the resulting path.
Untrusted Source Content Can Manipulate Model Instructions
Acquired title and content are inserted directly into the model prompt. Malicious source text can alter requested behavior or corrupt structured output.
The template interpolates source fields without trust-boundary controls, then passes the complete prompt to the configured LLM call.
Capability review items (6)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
This executable write uses a path derived from an unvalidated batch identifier. Absolute or traversal values can redirect pipeline output outside the intended directory.
This executable write uses a path derived from an unvalidated batch identifier. Absolute or traversal values can redirect pipeline output outside the intended directory.
This executable write uses a path derived from an unvalidated batch identifier. Absolute or traversal values can redirect pipeline output outside the intended directory.
This executable write uses a path derived from an unvalidated batch identifier. Absolute or traversal values can redirect pipeline output outside the intended directory.
This executable write uses a path derived from an unvalidated batch identifier. Absolute or traversal values can redirect pipeline output outside the intended directory.
This executable write uses a path derived from an unvalidated batch identifier. Absolute or traversal values can redirect pipeline output outside the intended directory.
Most static findings are false positives caused by Markdown code fences, reference links, CSS text, or benign words. The executable pipeline template does perform local file writes, and AI review found unvalidated path construction that could let writes or clean operations escape intended directories. No evidence of prompt injection, credential exfiltration, network calls, or malicious command execution was found.
The executable template accepts batch identifiers from the CLI and combines them directly with data and output directories. Parent directory segments in batch or item identifiers could redirect writes or clean-stage deletions outside the intended project folders.
The path helpers concatenate CLI-controlled batch_id and item identifiers into filesystem paths, and the clean stage unlinks files below that computed path. The script is user-run and intended for local use, so this is high confidence but not critical.
Capability review items (6)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
This executable template writes pipeline artifacts to local paths derived from batch and item identifiers. The writes are intended, but unvalidated path components can create or overwrite files outside expected directories.
This executable template writes pipeline artifacts to local paths derived from batch and item identifiers. The writes are intended, but unvalidated path components can create or overwrite files outside expected directories.
This executable template writes pipeline artifacts to local paths derived from batch and item identifiers. The writes are intended, but unvalidated path components can create or overwrite files outside expected directories.
This executable template writes pipeline artifacts to local paths derived from batch and item identifiers. The writes are intended, but unvalidated path components can create or overwrite files outside expected directories.
This executable template writes pipeline artifacts to local paths derived from batch and item identifiers. The writes are intended, but unvalidated path components can create or overwrite files outside expected directories.
This executable template writes pipeline artifacts to local paths derived from batch and item identifiers. The writes are intended, but unvalidated path components can create or overwrite files outside expected directories.
Most static findings are false positives caused by Markdown code fences, reference links, CSS text, or benign words. The executable pipeline template does perform local file writes, and AI review found unvalidated path construction that could let writes or clean operations escape intended directories. No evidence of prompt injection, credential exfiltration, network calls, or malicious command execution was found.
The executable template accepts batch identifiers from the CLI and combines them directly with data and output directories. Parent directory segments in batch or item identifiers could redirect writes or clean-stage deletions outside the intended project folders.
The path helpers concatenate CLI-controlled batch_id and item identifiers into filesystem paths, and the clean stage unlinks files below that computed path. The script is user-run and intended for local use, so this is high confidence but not critical.
Capability review items (6)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
This executable template writes pipeline artifacts to local paths derived from batch and item identifiers. The writes are intended, but unvalidated path components can create or overwrite files outside expected directories.
This executable template writes pipeline artifacts to local paths derived from batch and item identifiers. The writes are intended, but unvalidated path components can create or overwrite files outside expected directories.
This executable template writes pipeline artifacts to local paths derived from batch and item identifiers. The writes are intended, but unvalidated path components can create or overwrite files outside expected directories.
This executable template writes pipeline artifacts to local paths derived from batch and item identifiers. The writes are intended, but unvalidated path components can create or overwrite files outside expected directories.
This executable template writes pipeline artifacts to local paths derived from batch and item identifiers. The writes are intended, but unvalidated path components can create or overwrite files outside expected directories.
This executable template writes pipeline artifacts to local paths derived from batch and item identifiers. The writes are intended, but unvalidated path components can create or overwrite files outside expected directories.
AI review did not find malicious intent or prompt injection attempts in the skill content. Most high and critical static alerts are false positives caused by Markdown code fences, file names, model names, and documentation examples. The skill includes a runnable Python pipeline template that writes and deletes local files and can be customized to call LLM APIs, so publication should include a clear operational warning.
4
Files scanned
2,021
Lines analyzed
5
Review items
3
False positives ignored
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Runnable Template Performs Local File Writes and Deletes
The included Python template creates batch directories, writes raw prompts, parsed results, and rendered HTML, and its clean stage deletes generated stage outputs. This is legitimate pipeline behavior, but users should review paths and run it only inside an intended project directory.
The code directly writes files and deletes selected stage outputs through pathlib. The behavior is explicit and scoped to configured data and output directories, so it is an operational risk rather than evidence of malware.
The template formats item title and content directly into the LLM prompt. If users adapt the template for untrusted web or document inputs, those inputs can influence downstream model output unless they add prompt-injection handling and validation.
The content insertion path is clear, and the template is intended for LLM processing. There is no malicious payload in the skill files, but projects using untrusted inputs need defensive prompt design.
Static false positives ignored (3)
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.
Static Command-Execution Alerts Are Markdown False Positives
The Ruby or shell backtick findings correspond to fenced Markdown examples, inline code, or code blocks that describe pipeline structure. I did not find evidence that the skill secretly executes shell commands.
The cited locations are documentation code fences or inline examples, not executable Ruby backticks. The actual Python script does not call subprocess, os.system, eval, or exec.
The hardcoded URL findings point to cited external resources for case studies and references. They are not fetched automatically by the skill or script.
The URLs appear in Markdown source and reference sections. No code path was found that automatically sends data to these URLs.
Weak-Cryptography Alerts Are Non-Cryptographic Text Matches
The weak cryptography alerts map to Markdown syntax, file extensions, model names, or generic text rather than cryptographic functions. No evidence found of MD5, SHA1, DES, or similar weak algorithms being used for security.
Reviewed contexts show documentation headings, token estimation, and argparse configuration. They do not implement cryptographic operations.
This is a documentation and template skill for LLM project development methodology. All static findings are false positives: markdown files contain code examples for educational purposes, the Python script is a template requiring user customization for legitimate batch processing, and no actual credentials or malicious patterns exist. A previous AI audit also concluded 'safe' with no findings.
This is a documentation and template skill for LLM project development methodology. All static findings are false positives: markdown files contain code examples for educational purposes, the Python script is a template requiring user customization for legitimate batch processing, and no actual credentials or malicious patterns exist. A previous AI audit also concluded 'safe' with no findings.
This is a documentation-only skill with no executable code. The Python script provided is a template that users customize for their own LLM batch processing pipelines. No security concerns detected.
4
Files scanned
943
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.
This is a documentation-only skill with no executable code. The Python script provided is a template that users customize for their own LLM batch processing pipelines. No security concerns detected.
4
Files scanned
943
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.