nostr
Skill1 starsChanged 3 months agoMITView on GitHub
koteitan's Nostr hub — relay discovery (bootstrap → kind:10002 → kind:3 → fallback), NIP-19 bech32 encode/decode (naddr/nevent/npub, DIY, no nostr-tools), CLI relay debugging with websocat/nak, the standard web-app stack (TypeScript + Vite + rx-nostr + React), and a pointer to the ~/code/nostr-research survey of how real clients/relays behave (bootstrap relays, limit/rate-limit, NIP-11 limits). Use for any nostr task — building/fixing a nostr web client, making an naddr URL, checking which relay holds an event, or asking what other implementations do.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- aibtcdev/skillstheir own version, first seen Oct 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- aibtcdev/skills★ 11same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- autonomy-statSkill
- check-usageSkill
- compact-unfreezeSkill
- edit-statuslineSkill
- formalization-statement-fidelity-auditSkill
- get-contextSkill
- github-math-checkSkill
- heart-beatSkill
- manim-ttsSkill
- mermaidSkill
- my-github-md-ruleSkill
- sessiondbSkill
- use-bmsSkill
- use-fandomSkill
- webapp-defaultsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Match the surrounding file's existing method: If a bech32 helper or a relay-fetch pattern already exists in the file, reuse/extend it.
- Distinctive: line 26
Only use kind:10002 for the relay list.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
nostr
Everything for koteitan's nostr work. Read the reference file for the task at hand; each is self-contained.
| Task | Reference |
| New/existing nostr web app: stack, NIP-07, follow list, note fetching | references/project-stack.md |
| Which relays to read/write for a pubkey; incremental rendering rule | references/relay-discovery.md |
Build/parse naddr / nevent / npub / note / nprofile | references/nip19.md |
| "Does relay X have event/tag Y for pubkey Z?" (CLI debugging) | references/relay-query.md |
How do other clients/relays actually do it? — bootstrap-relay choices per client, relay-software limit/rate-limit behavior, per-instance NIP-11 limits | references/research-repo.md → ~/code/nostr-research/ |
Standing rules (apply to all nostr work)
- Do NOT use
nostr-tools(or other bech32 libs) for NIP-19 in project code — DIY the bech32, and keep decode symmetric with encode. - Match the surrounding file's existing method. If a bech32 helper or a relay-fetch pattern already exists in the file, reuse/extend it.
- Render as data arrives — never block on EOSE.
- Only use kind:10002 for the relay list; kind:3 is fallback only.
- Don't guess how other clients/relays behave, or what a relay's limits are —
look it up in
~/code/nostr-research/(seereferences/research-repo.md).
Relay sets (shared by all references)
Bootstrap / indexer relays:
wss://directory.yabu.me
wss://purplepag.es
wss://relay.nostr.band
wss://indexer.coracle.socialFallback relays — if browser locale is ja:
wss://yabu.me wss://nostr.compile-error.net
wss://r.kojira.io wss://relay-jp.nostr.wirednet.jp
wss://nrelay-jp.c-stellar.net wss://nostream.ocha.one
wss://snowflare.ccotherwise:
wss://relay.damus.io wss://nostr-pub.wellorder.net
wss://offchain.pub wss://relay.snort.socialCommon kinds: 0 metadata, 1 note, 3 contacts, 10002 relay list,
30030 emoji sets.
Related (not part of this skill)
nostter-upstream-pr— the PR workflow for contributing to SnowCait/nostter.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.