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.
npx claudepluginhub cameri/claude-skills --plugin nostrThis skill uses the workspace's default tool permissions.
<objective>
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Compresses source documents into lossless, LLM-optimized distillates preserving all facts and relationships. Use for 'distill documents' or 'create distillate' requests.
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.
</process><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>