ClawHub

WeryAI Task Inspector

v0.1.1

Inspect, query, summarize, and debug WeryAI task IDs and batch IDs through the official task query endpoints. Use when you need to query WeryAI task status,...

⭐ 0· 99·0 current·0 all-time
by@weryai-developer
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the code and files: the scripts only query task, batch, and balance endpoints and normalize results. Required artifacts (node, WERYAI_API_KEY) are appropriate for a client that calls the WeryAI API.
✓
Instruction Scope
SKILL.md instructs only read-only lookups. The runtime code follows that boundary: client.get is used for GET endpoints (/v1/generation/* and /v1/generation/batch/* and /v1/generation/balance). There are no file reads/writes beyond normal logging and no network endpoints other than the configured WERYAI_BASE_URL (defaults to api.weryai.com).
✓
Install Mechanism
No install spec (instruction-only) and included code is plain JavaScript. Runtime dependency is Node >=18 which is reasonable. Nothing is being downloaded from arbitrary URLs or installed into unusual system locations.
ℹ
Credentials
The declared required env var is only WERYAI_API_KEY (primary credential), which is proportionate. The code also reads optional WERYAI_BASE_URL and WERYAI_REQUEST_TIMEOUT_MS if present; those are sensible optional overrides but are not documented in requires.env. No unrelated secrets or additional credentials are requested.
✓
Persistence & Privilege
Skill is not always-enabled and does not request permanent privileges. It does not modify other skills or global agent settings. Autonomous invocation is allowed (platform default) but the skill's actions are read-only and limited to the WeryAI API.
Assessment
This skill appears to do exactly what it says: read-only inspection of WeryAI tasks and batches. Before installing: 1) Only provide a WERYAI_API_KEY you trust (the key is sent as a Bearer token to the WeryAI API). 2) If you want to be extra cautious, review or run the scripts locally so you can see outgoing requests (WERYAI_BASE_URL can be overridden). 3) Revoke or rotate the API key if you later suspect misuse. 4) Note that optional env vars (WERYAI_BASE_URL, WERYAI_REQUEST_TIMEOUT_MS) are supported but not required; do not set them to untrusted endpoints.

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

latestvk971c08jqww1ybgynje3eay0g583hsgf

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🔍 Clawdis
Binsnode
EnvWERYAI_API_KEY
Primary envWERYAI_API_KEY

Comments