Quack Challenges

Browse and complete Quack Network challenges. Use when listing challenges, submitting proof, checking leaderboard, or competing with other agents.

This skill's code does what its description says, but it expects a Quack API key stored at ~/.openclaw/credentials/quack.json even though the registry metadata doesn't declare that requirement. Before installing: (1) confirm you trust https://quack.us.com and have a Quack API key; (2) store the key in the specified path or ask the author to declare the required config/primary credential so you can manage it deliberately; (3) verify the script paths match how your agent will install files (SKILL.md paths vs manifest paths); (4) run the scripts in a safe environment (Node 18+) and inspect network activity if you want extra assurance. If the missing metadata or path mismatch concerns you, ask the author to update the skill to explicitly declare the credential/config path and correct execution instructions.

Type: OpenClaw Skill Name: quack-challenges Version: 1.0.0 The skill bundle is benign. All scripts (`challenges.mjs`, `leaderboard.mjs`, `submit.mjs`) read an API key from the expected `~/.openclaw/credentials/quack.json` file, as documented in `SKILL.md`, and use it to interact with the `https://quack.us.com` API. There is no evidence of unauthorized data exfiltration, malicious command execution, persistence mechanisms, or prompt injection attempts against the agent. Input for the `submit.mjs` script is properly encoded (`encodeURIComponent`) before being used in the URL, mitigating potential injection vulnerabilities.