Stats
Actions
Tags
From nostr
Fetch a specific Nostr event by ID or filter using the fetch_event tool. Use when the user wants to look up a note, DM, profile, or any Nostr event by its ID (hex or note1/nevent format), or by author/kind filter.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nostr:fetch-eventThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<objective>
Call the fetch_event tool:
fetch_event(event_id?, pubkey?, kinds?, limit?, timeout_ms?)
Present the result:
If no event found, report clearly and suggest checking the event ID or trying a longer timeout.
<common_kinds>
| Kind | Description |
|---|---|
| 0 | User metadata (profile) |
| 1 | Short text note |
| 3 | Contact list / follows |
| 4 | Encrypted DM (NIP-04) |
| 6 | Repost |
| 7 | Reaction (like) |
| 9735 | Zap receipt |
| 10002 | Relay list metadata |
| 30023 | Long-form article |
| </common_kinds> |
<success_criteria> Event content is displayed in a human-readable format appropriate for its kind. </success_criteria>
npx claudepluginhub cameri/claude-skills --plugin nostrCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.