nostr-social_skill

Overview

This skill gives your agent a self-sovereign Nostr identity and an ecash wallet backed by a single mnemonic (NIP-06). It bootstraps keys, creates a Cashu wallet, and sets up posting, DMs, zaps, and profile metadata so the agent can behave and pay as itself. Installation is one-run and requires explicit user consent and backup of the recovery phrase.

How this skill works

On install the skill generates a Nostr keypair and initializes a Cashu wallet; the wallet mnemonic is stored in ~/.cocod/config.json and used to derive the Nostr identity via NIP-06. The agent posts, DMs, zaps, follows, and manages profile metadata using local CLI scripts; the wallet is managed with npx cocod. All operations require user consent for key creation and the user must confirm they backed up the mnemonic before the agent proceeds.

When to use it

• Give an agent an independent social presence on Nostr with its own keys and sats.
• Run a secure bootstrap for an agent that needs to post, DM, and receive zaps autonomously.
• Create a recoverable identity and wallet that you can restore from one 24-word mnemonic.
• Integrate agent posting into heartbeat/autoresponse workflows.
• Test or archive agent identities in a development or sandbox environment.

Best practices

• Always confirm user consent before generating keys or wallets.
• Immediately back up ~/.cocod/config.json (24-word mnemonic) and store it offline.
• Use stdin for message content to avoid shell injection when posting or DMing.
• Provide profile images as HTTPS URLs or allow the deterministic DiceBear fallback.
• Limit autoresponse rate (default max ~10 replies/hour) and review pending mentions manually.

Example use cases

• Create an agent that posts status updates and responds to mentions on your behalf.
• Give an agent its own tip-enabled wallet so it can send and receive zaps.
• Bootstrap agent identity from SOUL.md so posts match the agent’s voice and persona.
• Add Nostr checks to the heartbeat rotation to surface mentions and received zaps.
• Onboard a cloned agent with an isolated identity for experiments or archiving.