Skylv Deployment Automation

PassAudited by VirusTotal on May 3, 2026.

Overview

Type: OpenClaw Skill Name: skylv-deployment-automation Version: 1.0.1 The skill bundle contains only metadata and documentation for a deployment automation tool. No executable code (such as the referenced 'deploy.js') is included in the provided files. The documentation in SKILL.md describes standard DevOps practices like canary and blue-green deployments and lacks any indicators of malicious intent, prompt injection, or unauthorized data access.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If followed too freely, the agent could promote or change a production deployment before the user has reviewed the exact target and impact.

Why it was flagged

This is a high-impact production promotion command that includes an approval flag, but the skill does not state that the agent must get explicit user confirmation or validate the target before running it.

Skill content
node deploy.js promote --from staging --to production --approve
Recommendation

Only use this skill with explicit per-deployment approval, known targets, dry-run or diff review, and least-privilege deployment credentials.

What this means

The agent may try to run an unknown local deployment script, which could perform actions outside what this skill document describes.

Why it was flagged

The skill depends on a local deploy.js runner, but the provided artifacts include no code file or install spec for that runner, making the executor's provenance and behavior unreviewed.

Skill content
node deploy.js deploy --strategy canary --service api --canary-percent 10
Recommendation

Before use, verify the exact deploy.js file, its source, permissions, and expected behavior; do not run it from an untrusted workspace.

What this means

Using this skill in a privileged deployment environment could let the agent affect production systems.

Why it was flagged

Production deployment and promotion normally require privileged access, although the skill does not declare any credential handling.

Skill content
Multi-env — Dev → staging → production promotion
Recommendation

Use narrowly scoped deployment credentials and require human approval for production changes.