The skill is a legitimate verging.ai face-swap workflow, but it performs real outbound network calls, external media processing commands, API-key handling, and temporary file storage. Many Markdown backtick findings are false positives, while the confirmed risks center on credential exposure in curl commands, third-party upload of biometric media, and arbitrary remote media inputs.
The skill accepts arbitrary video and face image inputs, then creates a face-swap job. It only reminds users to process media they have rights to, so misuse for impersonation or non-consensual synthetic media remains possible.
The documented options accept any video and face image path or URL, and the create-job step uploads the face image directly. The rights reminder is helpful but does not enforce consent.
The workflow uploads video and face images to verging.ai and storage URLs, then returns external result locations. This creates privacy exposure for biometric media beyond the local machine.
The upload and create-job steps explicitly transfer user media to remote API and storage endpoints. The response examples show externally hosted upload and result URLs.
Capability review items (29)
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 command expands $VERGING_API_KEY into an Authorization header for curl. This is expected API authentication, but a live secret is handled in command-line arguments.
This Markdown block instructs use of curl to call verging.ai authentication endpoints with an Authorization header. It is intended behavior, but it executes a network command and handles an API credential.
The workflow instructs ffprobe to parse a user-provided video file. External media parsers increase local attack surface when processing untrusted files.
The usage example accepts a YouTube URL and a remote face-image URL. This confirms the skill can fetch arbitrary remote resources, so network access is real.
The command calls the verging.ai auth endpoint with an API-key header. The URL is expected for the service, but it confirms outbound network activity with credentials.
The command calls the same verging.ai auth endpoint using a Bearer header. It confirms intentional outbound network access with a credential-bearing request.
The skill is a legitimate verging.ai face-swap workflow, but it performs real outbound network calls, external media processing commands, API-key handling, and temporary file storage. Many Markdown backtick findings are false positives, while the confirmed risks center on credential exposure in curl commands, third-party upload of biometric media, and arbitrary remote media inputs.
The skill accepts arbitrary video and face image inputs, then creates a face-swap job. It only reminds users to process media they have rights to, so misuse for impersonation or non-consensual synthetic media remains possible.
The documented options accept any video and face image path or URL, and the create-job step uploads the face image directly. The rights reminder is helpful but does not enforce consent.
The workflow uploads video and face images to verging.ai and storage URLs, then returns external result locations. This creates privacy exposure for biometric media beyond the local machine.
The upload and create-job steps explicitly transfer user media to remote API and storage endpoints. The response examples show externally hosted upload and result URLs.
Capability review items (29)
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 command expands $VERGING_API_KEY into an Authorization header for curl. This is expected API authentication, but a live secret is handled in command-line arguments.
This Markdown block instructs use of curl to call verging.ai authentication endpoints with an Authorization header. It is intended behavior, but it executes a network command and handles an API credential.
The workflow instructs ffprobe to parse a user-provided video file. External media parsers increase local attack surface when processing untrusted files.
The usage example accepts a YouTube URL and a remote face-image URL. This confirms the skill can fetch arbitrary remote resources, so network access is real.
The command calls the verging.ai auth endpoint with an API-key header. The URL is expected for the service, but it confirms outbound network activity with credentials.
The command calls the same verging.ai auth endpoint using a Bearer header. It confirms intentional outbound network access with a credential-bearing request.
Static analysis flagged command execution, network access, API key handling, temporary file use, and weak-crypto matches. Review confirmed the command, network, credential, and filesystem risks as intended but security-sensitive behavior for a media upload workflow. No prompt injection or malicious intent was found, and the weak cryptography alerts are false positives.
2
Files scanned
225
Lines analyzed
8
Review items
1
False positives ignored
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
External Tool Execution With User-Supplied Media Inputs
The skill instructs the agent to run npx, yt-dlp, curl, ffprobe, and ffmpeg commands using user-provided paths and URLs. This is required for the workflow, but it creates command execution and input handling risk if arguments are not quoted or validated.
The files directly document shell commands that process user-controlled video and image inputs. The commands are normal for this skill, so the risk is operational rather than evidence of malicious intent.
External API Uploads Include Sensitive Media and Credentials
The workflow sends an API key in Authorization headers and uploads video and face image data to verging.ai and a presigned storage URL. This behavior is disclosed and central to the service, but users must understand that personal media leaves the local machine.
The API key header and multipart upload instructions are explicit. The endpoints appear aligned with the claimed face swap service, which reduces concern about malicious exfiltration.
The instructions place downloaded, trimmed, and uploaded media under /tmp/verging-faceswap. Temporary storage is practical, but face images and videos may remain readable until cleanup is performed.
Multiple instructions reference the same temporary directory and media filenames. The skill also tells users to clean up, so the issue is a privacy hygiene concern.
Hardcoded Service URLs Are Expected API Documentation
The static analyzer flagged verging.ai, YouTube, and example URL references. These links document the intended external service and example inputs, with no evidence of hidden endpoints.
The URLs are visible user-facing documentation for the advertised service. I did not find evidence that they are concealed or unrelated to the skill.
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.
Static analysis reported weak cryptographic algorithm matches, but the referenced lines describe face swap metadata or a Markdown table. No evidence of cryptographic code was found.
The cited lines contain natural language or Markdown formatting, not hash or cipher usage. This makes the weak-crypto finding highly likely to be a scanner false positive.
Static analysis flagged command execution, network access, API key handling, temporary file use, and weak-crypto matches. Review confirmed the command, network, credential, and filesystem risks as intended but security-sensitive behavior for a media upload workflow. No prompt injection or malicious intent was found, and the weak cryptography alerts are false positives.
2
Files scanned
225
Lines analyzed
8
Review items
1
False positives ignored
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
External Tool Execution With User-Supplied Media Inputs
The skill instructs the agent to run npx, yt-dlp, curl, ffprobe, and ffmpeg commands using user-provided paths and URLs. This is required for the workflow, but it creates command execution and input handling risk if arguments are not quoted or validated.
The files directly document shell commands that process user-controlled video and image inputs. The commands are normal for this skill, so the risk is operational rather than evidence of malicious intent.
External API Uploads Include Sensitive Media and Credentials
The workflow sends an API key in Authorization headers and uploads video and face image data to verging.ai and a presigned storage URL. This behavior is disclosed and central to the service, but users must understand that personal media leaves the local machine.
The API key header and multipart upload instructions are explicit. The endpoints appear aligned with the claimed face swap service, which reduces concern about malicious exfiltration.
The instructions place downloaded, trimmed, and uploaded media under /tmp/verging-faceswap. Temporary storage is practical, but face images and videos may remain readable until cleanup is performed.
Multiple instructions reference the same temporary directory and media filenames. The skill also tells users to clean up, so the issue is a privacy hygiene concern.
Hardcoded Service URLs Are Expected API Documentation
The static analyzer flagged verging.ai, YouTube, and example URL references. These links document the intended external service and example inputs, with no evidence of hidden endpoints.
The URLs are visible user-facing documentation for the advertised service. I did not find evidence that they are concealed or unrelated to the skill.
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.
Static analysis reported weak cryptographic algorithm matches, but the referenced lines describe face swap metadata or a Markdown table. No evidence of cryptographic code was found.
The cited lines contain natural language or Markdown formatting, not hash or cipher usage. This makes the weak-crypto finding highly likely to be a scanner false positive.
The skill is a documentation/instruction file (no executable code) that guides an AI assistant to run shell commands (yt-dlp, ffmpeg, curl) and make API calls to verging.ai. All 82 static findings are false positives in context: backtick patterns are markdown code examples, URLs are legitimate API endpoints, API key references are standard authentication documentation, and temp directory access is standard media processing. The combination of network + credentials + external commands is expected for this use case. No malicious intent detected. Risk level is medium due to the breadth of system access required.
2
Files scanned
225
Lines analyzed
6
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.
The skill requires yt-dlp, ffmpeg, ffprobe, and curl binaries plus the VERGING_API_KEY environment variable. While all usages are documented and legitimate for face-swap workflows, the combination of network access, external command execution, credential handling, and filesystem write access represents a significant attack surface if the skill were modified maliciously. This is a known characteristic of media-processing skills, not a current vulnerability.
The skill uses /tmp/verging-faceswap/ for intermediate video and image files. This is standard practice for media processing but files may persist if not cleaned up. The documentation recommends cleanup. Low risk.
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.
The static scanner flagged 44 instances of 'Ruby/shell backtick execution' in markdown files. These are all code-block examples in documentation showing curl, ffmpeg, and yt-dlp commands. They are not executable code in the skill itself. False positive.
The 'weak cryptographic algorithm' findings at SKILL.md:3 and SKILL.md:33 are likely false positives triggered by the term 'key' in API key context or video codec references (libx264). No actual cryptographic operations are performed by the skill.
This is a legitimate face swap API client skill. The static findings reflect expected behavior: network calls to the verging.ai API service, environment variable access for API key authentication, and external command execution for video processing tools (yt-dlp, ffmpeg, curl). These are all necessary for the skill's core functionality. No malicious intent detected.
Static analysis flagged 77 patterns but all are false positives. Network URLs point to documented verging.ai API endpoints. Environment variable access is for user-provided API key authentication. Shell commands in SKILL.md are markdown documentation examples, not executable code. Temp directory usage is documented with cleanup. Skill is a legitimate CLI wrapper for a paid AI service.
4
Files scanned
341
Lines analyzed
5
Review items
0
False positives ignored
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Skill uses /tmp/verging-faceswap/ directory for temporary video and image files during processing. Files are documented to be cleaned up after processing but temporary storage of user media could pose privacy risks if cleanup fails.