soapbox-pub/nostr-skills

Overview

This skill provides up-to-date knowledge of the Nostr protocol, its NIPs (Nostr Implementation Possibilities), and how to implement Nostr features correctly. Use it to discover documented event kinds, standard tags, client/relay messaging, and to avoid duplicating existing protocol work. It helps you locate authoritative NIP sources and interpret the protocol landscape for design and implementation decisions.

How this skill works

It inspects the NIPs repository and the NIPs README to surface current protocol specifications, event kind mappings, and recommended tags and messages. The skill maps which NIPs document specific features and points you to the canonical NIP documents for deeper reading. It highlights existing capabilities so you can decide whether to adopt, extend, or propose new NIPs.

When to use it

• Designing or implementing a Nostr client, relay, or extension and needing authoritative protocol references.
• Looking up which NIP(s) document a particular event kind or tag.
• Validating implementation choices against existing NIPs to avoid duplication.
• Preparing a proposal or draft NIP and checking prior art and conventions.
• Troubleshooting interoperability issues between clients and relays.

Best practices

• Always start with the NIPs README to understand the current protocol state and event-kind mappings.
• Cross-reference any feature with existing NIPs before designing custom behaviors.
• Follow the canonical NIP documents for message formats, tags, and signature rules.
• Document any protocol extensions clearly and consider proposing a NIP if broadly useful.
• Test implementations against multiple relays and clients to ensure interoperability.

Example use cases

• Find which NIP(s) define a specific event kind before implementing an event handler.
• Discover standardized tags to annotate events correctly for client compatibility.
• Locate the NIP that describes client-to-relay subscription and response formats.
• Check the latest NIP text to implement signature verification and event creation rules.
• Assess whether a proposed feature already exists or needs a new NIP proposal.