Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Manage Nostr posting and engagement via the nak CLI. Use for creating notes, replying in threads, tagging npubs, checking replies/mentions, monitoring a rela...
Manage Nostr posting and engagement via the nak CLI. Use for creating notes, replying in threads, tagging npubs, checking replies/mentions, monitoring a rela...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use nak for all Nostr actions: publish notes, reply in threads, and query relays for replies/mentions. Default relay: wss://relay.primal.net unless the user specifies another.
Repo: https://github.com/fiatjaf/nak Install (script): curl -sSL https://raw.githubusercontent.com/fiatjaf/nak/master/install.sh | sh Update: re-run the install script above (it installs latest) Tip: review the script before running if you want to audit what it does.
Generate a new key: nak key generate (prints nsec + npub) Save the secret: store NOSTR_SECRET_KEY in a shell profile or a local .env with restricted permissions. Example: export NOSTR_SECRET_KEY="nsec1..." Optional: chmod 600 .env if you store it locally. Prefer env vars over inline --sec in commands.
Post a note: nak event -k 1 --sec $NOSTR_SECRET_KEY -c "..." <relay> Reply to a note: include root and reply tags (see below) Check replies: nak req -k 1 -e <event_id> -l <N> <relay> Check mentions: nak req -k 1 -p <your_pubkey_hex> -l <N> <relay>
Build content. Publish: nak event -k 1 --sec $NOSTR_SECRET_KEY -c "<content>" wss://relay.primal.net
Always include both root and reply tags so clients display it as a reply: root = original topβlevel note id reply = the specific note youβre replying to Use -t e="<id>;<relay>;root" and -t e="<id>;<relay>;reply". Example: nak event -k 1 --sec $NOSTR_SECRET_KEY \ -t e="<root_id>;wss://relay.primal.net;root" \ -t e="<reply_id>;wss://relay.primal.net;reply" \ -p <other_pubkey_hex> \ -c "<reply content>" \ wss://relay.primal.net
nak req -k 1 -e <root_id> -l 20 wss://relay.primal.net
nak req -k 1 -p <your_pubkey_hex> -l 20 wss://relay.primal.net
Default relay: wss://relay.primal.net Prefer NOSTR_SECRET_KEY env var instead of inline --sec. When tagging users, include -p <npub/hex>. For human-facing links, encode with nak encode nevent ... and format as https://primal.net/e/<nevent>.
Use nak event --help and nak req --help for flag details.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.