Find story options for a section concept, harvest stories from transcripts, or find expectation-inoculation stories. Use for "find me a story", "harvest stories", "inoculation story".
From uxinatornpx claudepluginhub jabberlockie/the-human-stack-plugins-public --plugin uxinatorThis skill uses the workspace's default tool permissions.
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.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Tim doesn't naturally create "story moments" — the story that launches a section and makes people care before teaching the framework. He jumps straight to the concept.
Two modes plus a new expectation-specific mode: Find stories, Harvest stories, or Find inoculation stories.
Triggers: "find me a story", "story for [section]", "story options", "I need a story for..."
A concept name and brief description.
STORY OPTIONS FOR: [Concept Name]
PURPOSE: Make the audience care about [concept] before you teach it
OPTION 1: [Story Title] — [Source: transcript / past session / generated]
Setup: [1-2 sentences: what's the situation?]
Tension: [What goes wrong or what's at stake?]
Turn: [What changes or what's revealed?]
Bridge: [Exact transition sentence from story → concept]
Time: [Estimated 60-90 sec]
OPTION 2: ...
OPTION 3: ...
RECOMMENDATION: Option [X] because [specific reason tied to audience and concept]
Triggers: "harvest stories", "harvest all", "extract stories from [transcript]"
Notion transcript page URL/ID, or "harvest all" to scan the transcript database.
STORY: [Descriptive title]
SOURCE: [Transcript + approximate location]
TOPIC TAGS: [2-3 topics this story could illustrate]
AUDIENCE FIT: [Enterprise / Nonprofit / Technical / Leadership / General]
TONE: [Funny / Serious / Cautionary / Inspiring / Provocative]
LENGTH: [Short (30-60 sec) / Medium (60-90 sec) / Long (2+ min)]
SETUP: [1-2 sentence summary]
KEY MOMENT: [The turn/punchline/insight]
BRIDGE OPTIONS: [2-3 transition sentences]
EXPECTATION TYPE: [Does this story illustrate or inoculate against an expectation?
DECLARED / TRANSFERRED / INFERRED / DEFAULT / SOCIAL / NONE]
TIMES USED: [Track usage — prevents overuse]
Triggers: "inoculation story", "inoculate against", "they're going to expect..."
Find or generate a story that preemptively addresses a TRANSFERRED expectation — something the audience expects based on past experience that doesn't apply to Tim's delivery.
The transferred expectation to inoculate against. Examples:
INOCULATION STORY FOR: [Transferred expectation]
PURPOSE: Name the past experience, separate Tim's delivery from it
OPTION 1: [Story Title]
Setup: [Acknowledge the past experience — make them feel SEEN]
Turn: [Here's how this is different]
Bridge: [Transition to what they CAN expect from today]
Exact words: "[Full script Tim can say — 30-60 seconds]"
OPTION 2: ...
DELIVERY NOTE: Place this in the first 5 minutes. Inoculation works best
before the audience has time to project their transferred expectation
onto Tim's session.