Azion Deploy
v0.1.1Deploy applications, static sites, and edge functions to Azion using Azion CLI. Use when the user asks to deploy/publish to Azion, configure link/build/deplo...
⭐ 0· 373·2 current·2 all-time
byAdriano Krauthein@askrauthein
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description, included helper script, and required binaries (bash, azion) all match the stated purpose of wrapping the Azion CLI for link/build/deploy flows.
Instruction Scope
Runtime instructions and the script keep to Azion-related actions (azion link/build/deploy, whoami, check .edge/manifest.json). However, the script and SKILL.md reference the AZION_TOKEN env var and allow passing `--token` even though no env var is declared in the skill metadata; the platform guidance flags references to env vars not declared in requires.env.
Install Mechanism
No install spec — instruction-only with a helper script included. This minimizes install-time risk (nothing is downloaded or extracted by the skill itself).
Credentials
The only credential referenced is AZION_TOKEN (appropriate for Azion CLI auth). But the skill's declared requirements list no environment variables or primary credential; the script uses AZION_TOKEN implicitly. That mismatch (undeclared but referenced token) reduces clarity about what secrets are needed and expected.
Persistence & Privilege
always is false, the skill is user-invocable and not forced always-on, and it does not attempt to modify other skills or system-wide config. It runs CLI commands only when invoked.
What to consider before installing
This skill is coherent with its stated purpose (wrapping the official Azion CLI) but exercise caution because: 1) the skill source/homepage is unknown — prefer skills from known publishers; 2) the script accepts AZION_TOKEN (or --token) but the skill metadata doesn't declare that env var, which makes it unclear when and how you'll be asked to provide credentials; 3) review the included scripts (scripts/azion-deploy.sh) yourself before running and confirm the azion CLI is installed from Azion's official distribution (see references/azion-cli.md). If you need to provide a token, create a scoped token with minimal permissions and avoid using long-lived high-privilege credentials. Run first in an isolated/test environment and verify deployments and domain behavior manually (curl the domain) after any deploy.Like a lobster shell, security has layers — review code before you run it.
latestvk97fwjp4c0jy9tdenqmjcr7dyh81wqv9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🚀 Clawdis
Binsbash, azion