Agentcast

This skill appears to implement exactly what it claims (registering a Farcaster username/profile and an ERC‑8004 identity), but there are a few things to consider before using it: - Metadata mismatch: the registry entry claims no required env vars, but the scripts require PRIVATE_KEY (Ethereum custody key) and SIGNER_KEY (Farcaster Ed25519 signer). Expect to provide those when running the scripts locally. - Trust the AgentCast proxy: by default the scripts post signed messages and signatures to https://ac.800.works endpoints to bypass payment steps. The scripts do not send your raw private keys, but they do send signed artifacts — you must trust AgentCast not to misuse or replay them. If you prefer not to rely on the proxy, supply your own NEYNAR_API_KEY or run against the upstream endpoints described in the scripts. - Minimize exposure: run these scripts locally on a machine you control. Preferably use an ephemeral or low-value wallet for initial testing (so you don’t risk major funds if keys are exposed). Never paste private keys into chat or other logging channels. - Ask the maintainer to update registry metadata: the skill should declare required env vars (PRIVATE_KEY, SIGNER_KEY, optional NEYNAR_API_KEY) so installers are not surprised. If you need higher assurance, request the maintainer to provide an independent audit of the proxy endpoints or run the flows against the upstream APIs (Neynar/farcaster endpoints) with your own API keys instead of the default proxy.