Production Docker Compose

• Outcome: Pass
• Latest audit: May 29, 2026, 8:36 PM
• Version:
  1.0.0

Overview

This is a markdown-only skill for generating Docker Compose production files, with some broad activation and secret-handling caveats but no hidden execution or exfiltration behavior.

Install this if you want an agent to help create production Docker Compose files. Use it only on repositories where scanning configuration files is acceptable, avoid exposing real secrets when possible, and carefully review any generated docker-compose.yml and .env.example before running them.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access

Findings (3)

Intent-Code Divergence

Medium

• Confidence: 95% confidence
• Finding: The skill's narrative says to prefer env_file and avoid inline secrets, but the database examples still place secret-bearing variables directly under environment in the Compose file. Even when values are sourced from host environment interpolation, this normalizes secret material in the Compose spec and can lead users to commit sensitive configuration patterns or misunderstand what 'never inline secrets' means.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The trigger phrases are broad enough to match many ordinary Docker-related requests, increasing the chance this skill activates when a narrower or safer skill would be more appropriate. Overbroad activation can cause unintended file scanning, generation of deployment configs, and security-sensitive recommendations in contexts the user did not explicitly request.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The 'When to Use' section is ambiguous and overlaps with general Docker assistance, making accidental invocation more likely. In an agent setting, ambiguous routing can lead to the wrong automation running on a repository, which may expose configuration details or produce inappropriate deployment artifacts.

VirusTotal

64/64 vendors flagged this skill as clean.