Cicd Templates Generator

• Outcome: Pass
• Latest audit: May 29, 2026 at 8:36 PM UTC
• Version:
  1.0.1

Overview

This skill is a straightforward CI/CD template generator, but generated workflow files should be reviewed before being committed or enabled.

Use this as a template generator, not as an automatic deployment authority. Prefer print-only or review mode first, then inspect any generated workflow for triggers, publish/deploy jobs, third-party actions, curl-to-bash steps, and referenced secrets before committing it to a repository.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (3)

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The design explicitly promises generation of 'directly committable' CI/CD workflow files in repository-controlled locations such as .github/workflows/. That can cause users or downstream agents to introduce executable automation into a repo without an explicit warning, review gate, or safe-output convention, increasing the risk of accidental creation of privileged pipelines that run on push or pull request events.

Vague Triggers

Medium

• Confidence: 87% confidence
• Finding: The trigger examples include broad natural-language phrases such as asking for help creating a CI/CD workflow, which can match ordinary user requests and cause the skill to activate unexpectedly. In a tool that can generate repository workflow files, overbroad activation increases the chance of unintended file generation or steering the agent into modifying CI/CD configuration without clear user consent.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The documentation states that the tool writes workflow files to repository paths by default, but it does not clearly foreground that behavior as a potentially modifying action. Because CI/CD files directly affect build, test, deployment, and secret-handling behavior, silent or poorly disclosed default writes can lead to unintended changes in sensitive automation paths.

VirusTotal

65/65 vendors flagged this skill as clean.