nostr sdks update
- Repo stars 0
- Author repo skills-registry
- Domain
- Design
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Python
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- External requests
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
## Knowledge Refresh Task
You are running a knowledge refresh for the Nostr SDK knowledge base. This
is a maintenance task — do NOT answer user questions, only update your
agent memory.
**Important:** Write all findings to your agent memory directory ONLY. Never
modify files in the plugin/skill directory — those are read-only artifacts
managed by the plugin update mechanism.
If arguments were provided, focus on: $ARGUMENTS
Otherwise, perform a full refresh.
## Refresh Procedure
### 1. Fetch Latest from Library Repositories
Fetch README and recent release notes for each SDK:
| SDK | URL to fetch |
|---|---|
| nostr-tools | https://github.com/nbd-wtf/nostr-tools/releases |
| NDK | https://github.com/nostr-dev-kit/ndk/releases |
| rust-nostr | https://github.com/rust-nostr/nostr/blob/master/CHANGELOG.md |
| nostr-sdk-jvm (Maven) | https://central.sonatype.com/artifact/io.github.rust-nostr/nostr-sdk |
| nostr-sdk-swift (UniFFI) | https://github.com/rust-nostr/nostr-sdk-swift/releases |
| nostr-sdk-ios (native) | https://github.com/nostr-sdk/nostr-sdk-ios/releases |
| fiatjaf.com/nostr (Go) | https://pkg.go.dev/fiatjaf.com/nostr |
| go-nostr (archived legacy) | https://github.com/nbd-wtf/go-nostr |
| nostr-java | https://github.com/tcheeric/nostr-java/releases |
| nostr4j | https://github.com/NostrGameEngine/nostr4j |
| pynostr | https://pypi.org/project/pynostr/ |
| python-nostr (legacy) | https://github.com/jeffthibault/python-nostr |
| Rhodium | https://github.com/KotlinGeekDev/Rhodium |
| NostrKit | https://github.com/cnixbtc/NostrKit |
**For each source, capture:**
- Current version numbers (npm, JSR, crates.io, Maven Central, PyPI, SwiftPM)
- New or modified API surfaces
- Newly supported NIPs / dropped NIPs
- Breaking changes or deprecation notices
- Last commit timestamp; flag stale projects (>180 days inactive)
- Archive status changes
### 2. Search for Recent Developments
Use WebSearch for:
- "rust-nostr release" — version bumps, new bindings
- "nostr SDK new library" — emerging libraries to consider tracking
- "nostr-tools" / "NDK" major release notes
- "nostr go library" / "fiatjaf.com/nostr" — Go ecosystem updates
- "nostr Kotlin Swift" — JVM/Apple binding updates
### 3. Verify Project Status
For each tracked SDK:
- Is it still active? (commits in last 90 days)
- Has it been archived, renamed, or moved?
- Have new forks or successors emerged?
- Have new bindings appeared (UniFFI, FFI, JNI)?
If a new SDK is observed in the ecosystem, add it to the matrix in agent
memory (not the shipped supporting docs) for inclusion in a future update
release.
### 4. Update Agent Memory
Write all findings to your agent memory directory. Never modify plugin files.
**MEMORY.md** — update with:
- `last_fetch_date: <unix-timestamp>`
- Current version numbers for each tracked SDK
- Summary of what changed since last fetch
- Any newly archived / renamed / forked projects
**Topic files** — update or create as needed:
| File | What to record |
|---|---|
| `library-matrix.md` | Updated maturity / activity / NIP-support data per SDK |
| `new-libraries.md` | Newly observed Nostr SDKs not yet in shipped docs |
| `gotchas.md` | API quirks, name collisions, binding pitfalls discovered |
| `changelog.md` | Version bumps, breaking changes, archive notices |
| `corrections.md` | Anything that differs from shipped supporting documents — these corrections take precedence when answering |
### 5. Report
Output a concise summary of what was found:
- Key changes since last refresh
- New version numbers
- New or archived libraries
- Any corrections to the shipped supporting documents
- Issues encountered (404s, missing data, etc.)
---
> Source: [941design/claude-plugins](https://github.com/941design/claude-plugins) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->
Sections and files
Listed in source order.
sections -> Knowledge Refresh Task → Refresh Procedure → 1. Fetch Latest from Library Repositories → 2. Search for Recent Developments → 3. Verify Project Status → 4. Update Agent Memory
terms -> Important · For each source, capture · MEMORY.md · Topic files
files/cmd -> last_fetch_date: <unix-timestamp> · library-matrix.md · new-libraries.md · gotchas.md · changelog.md · corrections.md
body sha256 -> 40521a4c7e62
Knowledge Refresh Task
You are running a knowledge refresh for the Nostr SDK knowledge base. This is a maintenance task — do NOT answer user questions, only update your agent memory. Important: Write all findings to your agent memory directory ONLY. Never modify files in the plugin/skill directory — those are read-only artifacts
1. Fetch Latest from Library Repositories
Fetch README and recent release notes for each SDK: SDK · URL to fetch nostr-tools · https://github.com/nbd-wtf/nostr-tools/releases NDK · https://github.com/nostr-dev-kit/ndk/releases rust-nostr · https://github.com/rust-nostr/nostr/blob/master/CHANGELOG.md
2. Search for Recent Developments
Use WebSearch for: "rust-nostr release" — version bumps, new bindings "nostr SDK new library" — emerging libraries to consider tracking "nostr-tools" / "NDK" major release notes "nostr go library" / "fiatjaf.com/nostr" — Go ecosystem updates
3. Verify Project Status
For each tracked SDK: Is it still active? (commits in last 90 days) Has it been archived, renamed, or moved? Have new forks or successors emerged? Have new bindings appeared (UniFFI, FFI, JNI)?
4. Update Agent Memory
Write all findings to your agent memory directory. Never modify plugin files. MEMORY.md — update with:
last_fetch_date: <unix-timestamp>Current version numbers for each tracked SDK Summary of what changed since last fetch