vss-deploy-profile

The instructions explicitly provide a mechanism to bypass human confirmation for deployment if the user includes keywords like 'autonomously' or 'non-interactive', which can be exploited to perform unauthorized infrastructure changes. [ensemble: confirmed by 3/3 passes; severity set to the agreed median (ADR-0067).]

If the user's request already asks you to run autonomously (e.g. 'deploy X autonomously', 'run without confirmation', 'non-interactive'), skip the confirmation prompt and proceed straight to Step 5.

The skill handles multiple sensitive API keys (NGC, NVIDIA, HF) and writes them into a generated environment file, which may be logged or persisted in insecure locations.

Validate every credential... before Step 1c copies .env to generated.env

Skill executes commands, writes files, or accesses the network but declares no allowed-tools, so its tool surface cannot be reviewed or constrained.

SKILL.md links to "references/alerts.md" but the file is not part of the skill package — the workflow silently degrades or the content is sourced elsewhere at runtime

[`references/alerts.md`](references/alerts.md)

SKILL.md links to "references/base.md" but the file is not part of the skill package — the workflow silently degrades or the content is sourced elsewhere at runtime

[`references/base.md`](references/base.md)

SKILL.md links to "references/lvs-profile.md" but the file is not part of the skill package — the workflow silently degrades or the content is sourced elsewhere at runtime

[`references/lvs-profile.md`](references/lvs-profile.md)

SKILL.md links to "references/search.md" but the file is not part of the skill package — the workflow silently degrades or the content is sourced elsewhere at runtime

[`references/search.md`](references/search.md)