nostrstack-nostr

Nostr-specific workflows in nostrstack: identifier parsing, event/profile landing pages, relay fetch/caching rules, NIP-05 identity resolution, and reference rendering. Use when working on Nostr event handling, NIP-05 lookups, or /nostr/:id UI/API behavior.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 9, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill streamlines Nostr protocol development by providing specialized workflows for identifier parsing, NIP-05 identity resolution, and relay management. It ensures consistent API behavior and optimized event handling for decentralized social media applications and Nostr-integrated tools.

Use Cases

  • Parsing and resolving complex Nostr identifiers (bech32) and bech32-prefixed strings into actionable event or profile data.
  • Implementing NIP-05 identity resolution flows to verify user handles and enhance trust within Nostr-based applications.
  • Managing relay communication rules, including fetch caps, timeouts, and cache TTL configurations to optimize network performance.
  • Developing UI components for event landing pages and rendering safe references for tags and mentions within the /nostr/:id path structure.
namenostrstack-nostr
description"Nostr-specific workflows in nostrstack: identifier parsing, event/profile landing pages, relay fetch/caching rules, NIP-05 identity resolution, and reference rendering. Use when working on Nostr event handling, NIP-05 lookups, or /nostr/:id UI/API behavior."

Nostr workflows

Use this skill for Nostr identifiers, events, and reference resolution.

Workflow

  • Read references/ids-and-api.md for identifier and API contract rules.
  • Read references/references.md for tag/mention resolution behavior.
  • Consult references/identity-resolution.md for NIP-05 flows.

Guardrails

  • Accept nostr:-prefixed identifiers and multiple bech32 types.
  • Enforce relay caps, timeouts, and cache TTLs from config.
  • Keep all rendered content safe and link references to /nostr/<id>.