OpenClaw

dagny-nostr-nak

Manage Nostr posting and engagement via the nak CLI. Use for creating notes, replying in threads, tagging npubs, checking replies/mentions, monitoring a relay (default wss://relay.primal.net), and publishing events with correct root/reply tags. Requires access to NOSTR_SECRET_KEY (nsec) for signing/publishing.

edwardbickerton0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install edwardbickerton/dagny-nostr-nak

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Nostr (nak)

Overview

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.

Install / Update nak

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.

Onboarding (keys)

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.

Quick Start (common tasks)

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>

Workflow: Posting & Replies

1) Create a new note

Build content.

Publish:

nak event -k 1 --sec $NOSTR_SECRET_KEY -c "<content>" wss://relay.primal.net

2) Reply to a reply (correct threading)

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

3) Check for replies to a note

nak req -k 1 -e <root_id> -l 20 wss://relay.primal.net
```...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/edwardbickerton/dagny-nostr-nak
Version: —
Commit: a391d0378a3cd3d0f1a141fa6cd89a0827b4115e
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Nostr (nak)

## Overview
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.

## Install / Update nak
- **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.

## Onboarding (keys)
- **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.

## Quick Start (common tasks)
- **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>`

## Workflow: Posting & Replies

### 1) Create a new note
- Build content.
- Publish:
  ```bash
  nak event -k 1 --sec $NOSTR_SECRET_KEY -c "<content>" wss://relay.primal.net
  ```

### 2) Reply to a reply (correct threading)
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:
```bash
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
```

### 3) Check for replies to a note
```bash
nak req -k 1 -e <root_id> -l 20 wss://relay.primal.net
```...

搜索