Back to skill

Security audit

workflow-setup

Security checks across malware telemetry and agentic risk

Overview

This skill is a plain-text GitHub Actions setup guide whose repository-changing behavior is expected for its CI/CD purpose, with no evidence of hidden execution or data theft.

Install only if you want assistance creating GitHub Actions workflows. Review generated .github/workflows files before committing them, especially publish or deploy workflows that could run on releases or access repository secrets.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Vague Triggers

Medium
Confidence
92% confidence
Finding
The trigger list contains very broad terms such as "automation" and "testing" that can match many unrelated requests, causing the skill to activate outside its intended scope. Because this skill creates or modifies GitHub Actions workflows, unintended invocation could lead to repository configuration changes or deployment-related files being generated when the user did not explicitly request that level of automation.

Vague Triggers

Medium
Confidence
89% confidence
Finding
The multi-line trigger phrase split across entries ("setting up automation for a Python", "Rust", "or TypeScript project") is ambiguous and may be interpreted far more broadly than intended. In context, this can route general project-setup or automation requests to a skill that writes CI/CD workflows, increasing the chance of unauthorized or surprising repository changes.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The skill description explains that it sets up CI/CD workflows but does not clearly warn that it will create or modify files under .github/workflows and may enable deployment or publishing automation. That omission matters because workflow files can execute code in CI, use repository secrets, and trigger release or deployment actions, so users may approve changes without understanding the operational and security consequences.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.