Volcengine Compute Function
v1.0.0Build and operate Volcengine Function Compute workloads. Use when users need function deployment, event triggers, runtime configuration, or serverless troubleshooting.
⭐ 0· 956·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description promise (deploying and operating Volcengine Function Compute workloads) matches the SKILL.md content: a high-level checklist and reliability rules for packaging, deployment, and testing. The skill does not attempt to do unrelated things. Note: actual deployment in practice normally requires Volcengine credentials and tooling, but this skill is purely instructive and therefore does not request them.
Instruction Scope
SKILL.md contains only high-level steps (confirm runtime/region, build package, deploy, invoke test event, return logs) and general reliability rules. It does not instruct the agent to read system files, access environment variables, transmit data to external endpoints, or perform unexpected actions.
Install Mechanism
No install spec and no code files are present. Being instruction-only means nothing is written to disk or fetched at install time, which minimizes risk.
Credentials
The skill declares no required environment variables or credentials (consistent with being instruction-only). Keep in mind that a real deployment would need Volcengine API credentials and possibly tooling; absence of such requirements is reasonable here but would be concerning if a later version added broad credential requests.
Persistence & Privilege
always is false and the skill does not request persistent system presence or modify other skills. Autonomous invocation is allowed by default on the platform but the skill itself has no executable components to run autonomously.
Assessment
This skill is a lightweight, instruction-only checklist for Volcengine Function Compute and contains no code, installers, or credential requests — it will not itself deploy or access your systems. Because the publisher/source is unknown, consider these points before trusting or relying on it: (1) If you expect the agent to perform deployments, you will need to supply Volcengine credentials and tooling separately — verify any future version that requests keys or installs packages. (2) Prefer skills from known sources or official docs when giving agents access to cloud resources. (3) If a future update adds install scripts, downloads, or environment variable requirements, review them closely for unexpected network endpoints, archived downloads, or requests for unrelated credentials. If you only need guidance or a checklist, this skill is appropriate; do not assume it will perform live deployments without additional configuration.Like a lobster shell, security has layers — review code before you run it.
latestvk97fhac9szy5rxs8sy61h22as980yhqn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.