nostr-expert

Implement Nostr event construction, signing, and Bech32 encoding with Quartz.

1.6k|218|Updated Jan 11, 2023
One-click install
npx skills add https://github.com/vitorpamplona/amethyst --skill nostr-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nostr-expert
Source: https://github.com/vitorpamplona/amethyst/tree/main
Command: npx skills add https://github.com/vitorpamplona/amethyst --skill nostr-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Nostr protocol implementation patterns in Quartz are provided to help developers build, sign, and verify events, manage NIP mappings, and implement Bech32 encoding and relay flows across Android and JVM/Desktop in a cohesive KMP library.

Core Features & Use Cases

  • Event construction, signing, and verification using TagArrayBuilder DSL
  • NIP mappings for 57 NIPs organized within quartz with clear package structure
  • Bech32 encoding/decoding for npub, nsec, note, nevent
  • Cross-platform relay interaction patterns and data flows using Kotlin Multiplatform

Quick Start

Create a TextNote event template, sign it with a local key, and publish it to relays using Quartz patterns.

Frequently Asked Questions about nostr-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement Nostr event construction and signing in a Kotlin Multiplatform project?

Nostr event construction and signing in Kotlin Multiplatform uses the TagArrayBuilder DSL to build event templates and local keys to sign them. This provides cohesive event creation and verification patterns across Android and JVM Desktop environments.

Does Quartz support Bech32 encoding for Nostr identifiers like npub and nsec?

Quartz supports Bech32 encoding and decoding for Nostr identifiers including npub, nsec, note, and nevent. These patterns handle cross-platform data encoding using Kotlin Multiplatform expect/actual abstractions for Android and Desktop JVM.

How do I map Nostr Implementation Possibilities (NIPs) into my Kotlin project structure?

Mapping NIPs into your Kotlin project involves organizing the 57 supported Nostr Implementation Possibilities within clear Quartz package structures. This provides standardized protocol feature integration and consistent implementation patterns.

What's the best way to handle Nostr relay interactions across Android and Desktop JVM?

Handling Nostr relay interactions across Android and Desktop JVM uses cross-platform relay interaction patterns and data flows built with Kotlin Multiplatform. These templates provide consistent relay communication using expect/actual abstractions.

Can I use expect/actual abstractions to build Nostr protocol features for multiple platforms?

Expect/actual abstractions enable building Nostr protocol features for multiple platforms by providing shared event construction, signing, and validation logic. This approach allows a single cohesive KMP library to target both Android and Desktop JVM environments.