Volcengine Compute Ecs

v1.0.0

Manage Volcengine ECS instances and related resources. Use when users need instance inventory, lifecycle operations, troubleshooting, or automation templates for ECS.

⭐ 0· 966·1 current·1 all-time

by@cinience

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for cinience/volcengine-compute-ecs.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Volcengine Compute Ecs" (cinience/volcengine-compute-ecs) from ClawHub.
Skill page: https://clawhub.ai/cinience/volcengine-compute-ecs
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install volcengine-compute-ecs

ClawHub CLI

Package manager switcher

npx clawhub@latest install volcengine-compute-ecs

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Suspicious

medium confidence

Purpose & Capability

The skill claims to manage Volcengine ECS (inventory, lifecycle, troubleshooting) but the package declares no authentication method, no required credentials, and no homepage/source. Real ECS operations require API keys/credentials or an explicit platform connector; the absence of any declared credential or explanation is inconsistent with the stated purpose.

ℹ

Instruction Scope

SKILL.md is concise and stays within a limited, safe scope (confirm region, prefer read-only, require explicit target IDs). It does not instruct reading unrelated files or exfiltrating data. However, it also omits any concrete commands, API endpoints, or authentication steps — leaving essential behavior unspecified.

✓

Install Mechanism

No install spec and no code files — instruction-only. This minimizes risk from arbitrary downloads or disk modifications.

Credentials

No required environment variables or primary credential are declared despite the skill's need to operate on cloud resources. Either the skill expects a platform-provided Volcengine connector (not documented here) or it omits required credentials — both are problematic from a trust/provenance perspective.

✓

Persistence & Privilege

always:false and no install actions; the skill does not request persistent elevated privileges or modifications to other skills' configs.

What to consider before installing

This skill's surface looks safe but incomplete. Before installing, ask the publisher to explain how it authenticates to Volcengine (which env vars, platform connector, or credential store), provide a source or homepage for provenance, and list the exact API/CLI calls it will make and any endpoints it contacts. If you proceed without that information, treat it as untrusted: run in a restricted environment, do not give platform-wide credentials, and require explicit confirmation before any mutating operations. If your platform already supplies a vetted Volcengine connector, verify that connector's name and permissions match what this skill expects.

Like a lobster shell, security has layers — review code before you run it.

latestvk97d0frs6xxmwrs9x7dq800xd180ze51

966downloads

0stars

1versions

Updated 1mo ago

v1.0.0

MIT-0

volcengine-compute-ecs

Operate ECS resources safely with clear scope, dry-run style checks, and auditable output.

Execution Checklist

Confirm region, account scope, and instance filters.
Query inventory before mutating operations.
Execute lifecycle actions (start/stop/reboot) only with explicit target IDs.
Return action summary with instance IDs and status.

Safety Rules

Prefer read-only commands first.
Batch operations by region and tag.
Record pre/post status for rollback.

References

references/sources.md

Comments

Loading comments...