Self-custody wallet setup for Simmer agents. Choose OWS (recommended — encrypted local vault, multi-chain, policy controls) or external raw key (existing set...
Security Analysis
medium confidenceThe skill's requirements and instructions are coherent for setting up a self-custody wallet for Simmer agents, but it instructs running a remote install script and handling private keys — both of which need careful manual review and safe operational practices.
Name/description, declared envs (SIMMER_API_KEY, optional OWS_WALLET, WALLET_PRIVATE_KEY), and the referenced SDK (simmer-sdk) align with a wallet-setup helper for agent signing on Polymarket/Kalshi. Nothing requested is unrelated to the stated purpose.
SKILL.md stays on-topic: it explains two legitimate flows (OWS vault or raw private key), how to register wallets with the Simmer SDK, and explicitly warns that registration requires a logged-in dashboard session. It instructs creating local OWS wallets under ~/.ows/wallets and using an env var for raw keys. The skill does not instruct reading unrelated system files or exfiltrating data, but it does tell the operator to put a raw private key into an environment variable (expected for this flow) — handle with care.
There is no built-in install spec, but the runtime instructions tell the operator to run a remote installer via curl -fsSL https://docs.openwallet.sh/install.sh | bash and to pip install packages (open-wallet-standard, simmer-sdk). Piping a remote shell script is a high-risk operation unless the script is inspected and from a trusted source; pip installs are common but should be verified. This is a procedural risk rather than a coherence issue.
Requested environment variables are proportional and expected: SIMMER_API_KEY is the primary credential, OWS_WALLET and WALLET_PRIVATE_KEY are optional and only relevant to the chosen path. No unrelated credentials or broad config paths are requested.
The skill is instruction-only, has no install spec, does not request always:true, and does not modify other skills or system-wide settings. Wallet files are stored under ~/.ows by OWS as expected; nothing in the skill asks for elevated or persistent platform privileges.
Guidance
This skill appears to do what it claims, but follow safe operational practices before using it: (1) Prefer the OWS path (recommended) to avoid placing raw private keys in environment variables. (2) Do not auto-run 'curl | bash' scripts — fetch and inspect https://docs.openwallet.sh/install.sh manually and confirm the source before executing. (3) Treat WALLET_PRIVATE_KEY like a secret: avoid storing it in plaintext environment files on shared or cloud hosts; use OS-level secret stores or OWS. (4) Verify the provenance of SIMMER_API_KEY and confirm the simmer-sdk package comes from the official project. (5) Because register_agent_wallet() and set_approvals() require a logged-in dashboard session, run those setup steps interactively from a secure machine. If you want a stricter assessment, provide the exact contents of the remote install script URL and the simmer-sdk package source (PyPI/project repo); that information would reduce uncertainty about install-time risk.
Latest Release
v0.1.0
Initial Tier A self-custody wallet setup skill — OWS recommended, external raw key supported. Managed users skip this skill (dashboard flow).
More by @adlai88
Published by @adlai88 on ClawHub
