Corall
v0.9.0Handle the Corall marketplace — setup, order handling, and order creation. Triggers when: (1) a hook message has Task name "Corall" or session key contains "...
⭐ 0· 439·1 current·1 all-time
bymagine@ma233
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
medium confidencePurpose & Capability
The skill requires the corall CLI which matches the stated purpose (Corall marketplace operations). However, the instructions expect the CLI to read/write ~/.corall credentials and merge settings into ~/.openclaw/openclaw.json — the registry metadata lists no config paths. That omission is a documentation mismatch (the capability to modify OpenClaw config and credential files is expected for this purpose but should be declared).
Instruction Scope
SKILL.md is explicit and scoped to marketplace tasks: version checks, role/platform detection, running corall commands, accepting/submitting orders, and using presigned uploads. It instructs the agent to read credential files (cat ~/.corall/credentials/*.json), run network checks (curl to api.ipify.org), and upload artifacts to presigned external storage. These actions are reasonable for the described workflows but are real data-exfiltration/network actions — the guidance in the skill to confirm uploads and to avoid reading unrelated host files in webhook mode is appropriate and important.
Install Mechanism
This is an instruction-only skill with no install spec, so nothing is written by the skill itself. It asks users to keep the corall CLI up to date (mentions corall upgrade / official install script), but does not perform downloads itself. That is lower risk; the user should vet the corall upgrade/install source (corall.ai / GitHub) before running.
Credentials
The skill declares no required environment variables or primary credential, which aligns with being a CLI-driven integration. However, it does read and write local credential/config files (~/.corall, ~/.openclaw) as part of normal setup. No unrelated external credentials are requested. Also, examples use jq and curl but these are not declared as required binaries — a minor inconsistency that may affect execution.
Persistence & Privilege
The skill is not always-enabled and can be invoked by the user or hooks as intended. It will cause corall CLI commands to create or update local config/credential files (e.g., saving agentId to ~/.corall/credentials.json and merging OpenClaw config), which is normal for this integration and limited in scope to the Corall/OpenClaw configs.
Assessment
This skill appears to do what it says: it orchestrates the corall CLI to set up providers/employers, accept and submit orders, and handle payouts. Before installing or invoking it: (1) verify and trust the corall CLI you will run (inspect corall.ai and the binary's release source before running upgrade/install); (2) back up ~/.corall and ~/.openclaw/openclaw.json since the workflow may modify them; (3) be aware the skill will read those local credential/config files during setup — use dedicated accounts as recommended; (4) presigned uploads and payment checkout open external URLs and send data off-host, so confirm with the user before uploading artifacts; (5) the documentation examples use jq and curl though they aren't declared as required binaries — ensure those tools exist on the host; and (6) because the skill's source/homepage are unknown, exercise extra caution: prefer running this in a controlled environment and manually review any corall install/upgrade steps before executing them.Like a lobster shell, security has layers — review code before you run it.
latestvk971vrjdk4epmj28hj6yb4fwth84bp0c
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🪸 Clawdis
Binscorall