Agent skill

Nip46 Nostrconnect URL Params

by divinevideo in divinevideo/divine-mobile

Fix NIP-46 nostrconnect:// URLs not being recognized by signer apps (Amber, nsec.app, nsecBunker).

MPL-2.0Auto-check passed

Install Nip46 Nostrconnect URL Params

skills CLI
$ npx skills add divinevideo/divine-mobile --skill nip46-nostrconnect-url-params -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install divinevideo/divine-mobile nip46-nostrconnect-url-params --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/nip46-nostrconnect-url-params .claude/skills/nip46-nostrconnect-url-params && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nip46-nostrconnect-url-params
GitHub stars
266
Token cost
~812 tokens
SKILL.md length
238 words
Files
1
Skills in repo
103
Repo updated
First seen
Licence
MPL-2.0

At a glance

Fix NIP-46 nostrconnect:// URLs not being recognized by signer apps (Amber, nsec.app, nsecBunker).

  • Works in 4 steps: Generate a nostrconnect:// URL → Verify URL contains name=, url=, image=… → Test with signer app (Amber Android,… → …
  • URL paste fails in signer app despite valid-looking URL
  • SKILL.md covers Problem, Context / Trigger Conditions, Solution and Verification, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Nip46 Nostrconnect URL Params is an agent skill from divinevideo/divine-mobile. Fix NIP-46 nostrconnect:// URLs not being recognized by signer apps (Amber, nsec.app, nsecBunker). Use when: (1) QR code or URL paste fails in signer app despite valid-looking URL, (2) Using metadata JSON object instead of separate query params, (3) Implementing client-initiated NIP-46 connections. The NIP-46 spec requires name/url/image as separate query parameters, not a metadata JSON object.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The licence is MPL-2.0.

When your agent uses it

  • URL paste fails in signer app despite valid-looking URL
  • Using metadata JSON object instead of separate query params
  • Implementing client-initiated NIP-46 connections

Example prompts

  • “/nip46-nostrconnect-url-params”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Generate a nostrconnect:// URL
  2. Verify URL contains name=, url=, image= as separate params (not metadata=)
  3. Test with signer app (Amber Android, nsec.app web, or nsecBunker)
  4. Signer should show app name and prompt for approval

What it can do on your machine

Read from SKILL.md and the folder at commit c3d6f7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are dart).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nip46 Nostrconnect URL Params loads about 812 tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 238 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~812

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from divinevideo/divine-mobile at commit c3d6f7e, republished under its MPL-2.0 licence (© divinevideo). 238 words, ~812 tokens.

Download SKILL.mdSave it as .claude/skills/nip46-nostrconnect-url-params/SKILL.md (or your agent's skills folder).
name
nip46-nostrconnect-url-params
description
Fix NIP-46 nostrconnect:// URLs not being recognized by signer apps (Amber, nsec.app, nsecBunker). Use when: (1) QR code or URL paste fails in signer app despite valid-looking URL, (2) Using metadata JSON object instead of separate query params, (3) Implementing client-initiated NIP-46 connections. The NIP-46 spec requires name/url/image as separate query parameters, not a metadata JSON object.
author
Claude Code
version
1.0.0
date
2026-02-01

NIP-46 nostrconnect:// URL Parameter Format

Problem

When implementing NIP-46 client-initiated connections (nostrconnect://), signer apps may fail to recognize the URL if app metadata is passed as a JSON object instead of separate query parameters.

Context / Trigger Conditions

  • Signer app (Amber, nsec.app, nsecBunker) shows error or fails silently when scanning/pasting URL
  • URL contains metadata={"name":"...","url":"..."} format
  • QR code generates successfully but signer doesn't connect
  • Other parameters (relay, secret, perms) appear correct

Solution

Wrong (metadata JSON object):
nostrconnect://<pubkey>?relay=wss://relay.example.com&secret=abc123&metadata={"name":"MyApp","url":"https://myapp.com","icon":"https://myapp.com/icon.png"}&perms=sign_event
Correct (separate parameters per NIP-46):
nostrconnect://<pubkey>?relay=wss://relay.example.com&secret=abc123&name=MyApp&url=https://myapp.com&image=https://myapp.com/icon.png&perms=sign_event
Code fix example (Dart):
dart
// WRONG - Don't bundle in metadata JSON
if (metadata.isNotEmpty) {
  final metadataJson = jsonEncode(metadata);
  params.add('metadata=${Uri.encodeComponent(metadataJson)}');
}

// CORRECT - Use separate params as specified in NIP-46
if (appName != null && appName.isNotEmpty) {
  params.add('name=${Uri.encodeComponent(appName)}');
}
if (appUrl != null && appUrl.isNotEmpty) {
  params.add('url=${Uri.encodeComponent(appUrl)}');
}
if (appIcon != null && appIcon.isNotEmpty) {
  params.add('image=${Uri.encodeComponent(appIcon)}');
}

Verification

  1. Generate a nostrconnect:// URL
  2. Verify URL contains name=, url=, image= as separate params (not metadata=)
  3. Test with signer app (Amber Android, nsec.app web, or nsecBunker)
  4. Signer should show app name and prompt for approval

NIP-46 Spec Reference

From NIP-46:

Additional information should be passed as query parameters:

  • name (optional) - the name of the client application
  • url (optional) - the canonical url of the client application
  • image (optional) - a small image representing the client application

The spec does NOT mention a metadata parameter - each field is a separate query param.

Notes

  • All query parameter values should be URL-encoded
  • The relay parameter can appear multiple times for multiple relays
  • The secret parameter is REQUIRED for nostrconnect:// (not optional like bunker://)
  • Some signer apps may be more lenient than others - always follow spec exactly
  • Note the param is image, not icon (easy to confuse with the metadata field name)

References

© divinevideo, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/nip46-nostrconnect-url-params of divinevideo/divine-mobile.

Open the folder on GitHubat commit c3d6f7e

Compare with similar skills

Nip46 Nostrconnect URL Params next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nip46 Nostrconnect URL Params compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nip46 Nostrconnect URL Params this skilldivinevideo/divine-mobile266—~812Automated safety check: PassMPL-2.0
Search Paramspromptfoo/promptfoo26k—~1.1kAutomated safety check: PassMIT
Canonical URLthedaviddias/Front-End-Checklist74k—~414Automated safety check: PassMIT
You Might Not Need URL Statesimstudioai/sim30k—~1.2kAutomated safety check: PassApache-2.0
URL To Markdownsickn33/agentic-awesome-skills47k—~599Automated safety check: PassMIT
URLaxoviq-ai/synthadoc1.6k—~371Automated safety check: PassAGPL-3.0-or-later

Similar skills

  • Search Params

    promptfoo/promptfoo

    URL search param and hash state management. An agent skill from promptfoo/promptfoo.

    26k GitHub stars~1.1k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Canonical URL

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Set canonical URLs for all pages.

    74k GitHub stars~414 tokensUpdated 4 days ago
    Marketing & SEOAuto-check passed
  • Analyze and fix URL/query-param state anti-patterns — manual useSearchParams reads, hand-built query mutations, view-state trapped in useState, and objects in the URL

    30k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • URL To Markdown

    sickn33/agentic-awesome-skills

    Fetch a public webpage as clean Markdown for an agent: read, summarize, quote, or cite the page while preserving its source URL.

    47k GitHub stars~599 tokensUpdated 2 days ago
    Knowledge ManagementAuto-check passed
  • URL

    axoviq-ai/synthadoc

    Fetch and extract text from web URLs

    1.6k GitHub stars~371 tokensUpdated today
    Knowledge ManagementAuto-check passed
  • Og URL Match

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing Open Graph tags or investigating why social share counts appear low.

    74k GitHub stars~543 tokensUpdated 4 days ago
    Auto-check passed

More from divinevideo/divine-mobile

All 103 skills in this repo
  • Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y".

    266 GitHub stars~931 tokensUpdated today
    Auto-check passed
  • Art Direct

    divinevideo/divine-mobile

    Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language.

    266 GitHub stars~4.8k tokensUpdated today
    Auto-check passed
  • Async Await Null Race Condition

    divinevideo/divine-mobile

    Fix "Null check operator used on a null value" errors when an object is set to null during an async await.

    266 GitHub stars~881 tokensUpdated today
    Auto-check passed
  • AWS V4 Signing Custom Headers Gcs

    divinevideo/divine-mobile

    Add custom metadata headers (x-amz-meta-) to AWS v4 signed requests for GCS S3-compatible API.

    266 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Bash Herestring Newline Secrets

    divinevideo/divine-mobile

    Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings.

    266 GitHub stars~791 tokensUpdated today
    Auto-check passed
  • Fix silent video/media processing failures caused by URL extraction code that filters on file extensions (.mp4, .webm, .webp).

    266 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Questions about Nip46 Nostrconnect URL Params

What does Nip46 Nostrconnect URL Params do?

Fix NIP-46 nostrconnect:// URLs not being recognized by signer apps (Amber, nsec.app, nsecBunker). Nip46 Nostrconnect URL Params is an agent skill from divinevideo/divine-mobile.app, nsecBunker).

When should I use Nip46 Nostrconnect URL Params?

Nip46 Nostrconnect URL Params fits situations like: URL paste fails in signer app despite valid-looking URL; using metadata JSON object instead of separate query params; implementing client-initiated NIP-46 connections.

How do I install Nip46 Nostrconnect URL Params in Claude Code?

Run `npx skills add divinevideo/divine-mobile --skill nip46-nostrconnect-url-params -a claude-code`. Or copy the skill folder (.agents/skills/nip46-nostrconnect-url-params in divinevideo/divine-mobile) into .claude/skills/nip46-nostrconnect-url-params in your project. Claude Code loads it when a task matches its description.

How do I install Nip46 Nostrconnect URL Params in Codex?

Run `npx skills add divinevideo/divine-mobile --skill nip46-nostrconnect-url-params -a codex`. Or copy the skill folder (.agents/skills/nip46-nostrconnect-url-params in divinevideo/divine-mobile) into .agents/skills/nip46-nostrconnect-url-params in your project. Codex loads it when a task matches its description.

Can I use Nip46 Nostrconnect URL Params in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add divinevideo/divine-mobile --skill nip46-nostrconnect-url-params -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nip46-nostrconnect-url-params, .gemini/skills/nip46-nostrconnect-url-params, .github/skills/nip46-nostrconnect-url-params and .opencode/skills/nip46-nostrconnect-url-params in your project.

What does Nip46 Nostrconnect URL Params need to run?

SKILL.md names no scripts, command-line tools or credentials: Nip46 Nostrconnect URL Params is instructions for the agent only.

Does Nip46 Nostrconnect URL Params access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Nip46 Nostrconnect URL Params safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Nip46 Nostrconnect URL Params use?

Nip46 Nostrconnect URL Params is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nip46 Nostrconnect URL Params use?

About 812 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nip46 Nostrconnect URL Params?

Skills that share tags, products or a category with Nip46 Nostrconnect URL Params: Search Params (promptfoo/promptfoo, 26k stars), Canonical URL (thedaviddias/Front-End-Checklist, 74k stars), You Might Not Need URL State (simstudioai/sim, 30k stars) and URL To Markdown (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nip46 Nostrconnect URL Params?

divinevideo (a GitHub organization) maintains it in divinevideo/divine-mobile, which has 266 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 10, 2026.

Source: divinevideo/divine-mobile on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.