| name | highlight-expansion |
| description | Use when Daniel wants to identify the strongest, most unique, or most interesting episodes of My Weird Prompts so far and propose updates, expansions, or spin-offs that build on them. Triggers on phrases like "best episodes", "highlight reel", "standouts", "what worked", "what should we build on", "most unique", "what's our best stuff". |
Highlight identification + expansion
A two-phase skill: first identify the library's highlights, then propose ideation that builds on them.
Phase 1 — Identify highlights
Query the Pinecone MCP server (pinecone in .mcp.json) against the MWP episode index. Score candidates for:
- Uniqueness — is this premise unlike anything else in the library? (Use vector distance from nearest neighbors as a rough signal.)
- Specificity — weirdly specific premises age better than generic ones
- Strong hook — the title/premise works on its own in one sentence
- Rewatch/relisten signal — if Daniel has notes, ratings, or callbacks referencing it, weight it up
- Replay potential in the format — premises that obviously support more episodes in the same world
Surface 5–10 episodes as "highlights" with a one-line note on why each one stood out. If Pinecone data isn't available, ask Daniel to name the 3–5 episodes he considers standouts and work from there.
Phase 2 — Expansion ideation
For each highlight, generate 1–3 suggestions of any of the following that have a logical position to exist. Skip types that don't fit — don't force a suggestion just to fill a slot.
- Update / re-record — the premise has aged or a better version is now possible
- Expansion — the premise has more in it than the first episode mined
- Spin-off — a character, world, or format element deserves its own show
- Recurring-segment candidate — this could become a returning bit across future episodes
- Cross-over — pair with another highlight in a single episode
- Format port — take the premise and port it into an offbeat format (see
offbeat-formats skill)
Output
Follow .claude/skills/OUTPUT_PROTOCOL.md. Save to:
outputs/YYYY-MM-DD/highlights-expansion.md
Structure the file in two sections:
# Highlights + expansion — YYYY-MM-DD
## Identified highlights
1. **<episode title>** — <one-line why it stood out>
2. ...
## Expansion suggestions
### 1. <hook>
**Source highlight:** <title>
**Expansion type:** update | expansion | spin-off | recurring-segment | cross-over | format-port
**Prompt:**
> ...
**Host guidance:** *(optional)*
> ...
**Rationale:** *(optional)*
Notes
- Don't propose expansions to every highlight. Some episodes are best left alone — being a standout doesn't mean being extensible.
- If a highlight is being proposed for update, say explicitly what's better about the new version vs. the original.
- Cross-overs should only pair highlights whose worlds/tones can actually coexist without diluting both.
