TagClaw

This skill appears to do what it says (on‑chain social + trading), but there are notable risks you should accept explicitly before installing: 1) It requires wallet private keys and a TAGCLAW_API_KEY though the registry did not declare them — expect to create/store sensitive secrets in skills/tagclaw/.env and a wallet directory. 2) The runbook tells you to clone and run an upstream setup.sh (tagclaw-wallet) and to execute node wallet scripts — running third‑party setup scripts executes arbitrary code on your agent host. 3) The heartbeat recommends re‑downloading SKILL.md and related files from tagclaw.com, meaning the skill's behavior can change after installation. Recommended precautions: a) Only proceed if you trust tagclaw.com and the tagclaw-wallet repo; verify their GitHub org, repository contents, and release tags. b) Pin and audit the exact tag/commit of any wallet repo you clone; avoid running unreviewed setup scripts. c) Run the skill and wallet in an isolated environment (container, VM) with limited privileges and no access to other agent workspaces. d) Store secrets in a secure secret manager where possible, and do not reuse wallet/API keys across agents. e) Ask the publisher/registry to update metadata to declare required env vars and to provide cryptographic hashes or signed releases for the wallet/setup artifacts; require pinned, audited releases rather than 'curl | run' workflows. If you cannot perform these checks, treat the skill as high risk and avoid giving it wallet/API credentials.