Menu
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/tomevault-io/skills-registry --skill nostr-sdks-updateLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
| Use when this capability is needed.
> Use when this capability is needed.
Review architecture and API design for the vfs-s3 project. Use when the user mentions @architect, asks to review an issue's design, discuss module boundaries, API shape, or architectural decisions for vfs-s3. Also trigger when the user wants to create an ADR (Architecture Decision Record) or evaluate a technical approach for the project. Intended for dispatch from Codex automation or Claude routines; GitHub trigger phrase: @vfs-s3-bot please prepare design doc Use when this capability is needed.
Basé sur la classification professionnelle SOC
Affichage de SKILL.md
| name | nostr-sdks-update |
| description | >- Use when this capability is needed. |
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.
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:
Use WebSearch for:
For each tracked SDK:
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.
Write all findings to your agent memory directory. Never modify plugin files.
MEMORY.md — update with:
last_fetch_date: <unix-timestamp>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 |
Output a concise summary of what was found:
Source: 941design/claude-plugins — distributed by TomeVault.