From example-skills
Analyzes narrative structures, character arcs, genre conventions, editing patterns, and producer techniques in reality TV for academic research and content analysis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/example-skills:reality-tv-narrative-analyzerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Framework for rigorous analysis of reality television narrative construction.
Framework for rigorous analysis of reality television narrative construction.
Reality TV is constructed, not captured. Analysis should examine:
| Format | Structure | Key Tension |
|---|---|---|
| Elimination | Weekly votes/cuts | Survival pressure |
| Talent | Performance judging | Skill vs. personality |
| Dating | Rose ceremonies/couples | Romantic stakes |
| Adventure | Physical challenges | Endurance/teamwork |
| Makeover | Transformation arc | Before/after reveal |
| Format | Focus | Narrative Engine |
|---|---|---|
| Docusoap | Ensemble cast daily life | Interpersonal conflict |
| Follow-doc | Single subject/family | Personal journey |
| Workplace | Professional environment | Drama + competence |
| Real crime | Investigation/justice | Mystery resolution |
Standard competition episode:
1. COLD OPEN (1-2 min)
- Dramatic moment from later in episode
- Hook viewer attention
2. RECAP (1-2 min)
- Previous episode highlights
- Set up ongoing storylines
3. ACT 1: Setup (10-15 min)
- Challenge introduction
- Strategy discussions (confessionals)
- Alliance/conflict development
4. ACT 2: Competition (15-20 min)
- Challenge execution
- Reaction shots, confessional commentary
- Winner/loser determination
5. ACT 3: Aftermath (10-15 min)
- Post-challenge strategy
- Target selection
- Relationship dynamics
6. ACT 4: Climax (10-15 min)
- Tribal council/elimination ceremony
- Tension building
- Revelation and exit
7. NEXT TIME (30 sec)
- Tease future conflict
Episodes 1-3: ESTABLISHMENT
- Introduce cast (hero, villain, underdog archetypes)
- Establish alliances and conflicts
- Set up season-long storylines
Episodes 4-7: DEVELOPMENT
- Deepen character complexity
- Shift alliances
- Build toward mid-season climax
Episodes 8-10: TURNING POINT
- Major blindside or upset
- New power dynamics
- Reset for endgame
Episodes 11-13: ENDGAME
- Final alliances solidify
- Underdog vs. frontrunner tension
- Elimination of major characters
Finale: RESOLUTION
- Final challenge/vote
- Winner crowned
- Reunion/reflection
| Archetype | Characteristics | Narrative Function |
|---|---|---|
| Hero | Likeable, competent, moral | Audience identification |
| Villain | Strategic, ruthless, entertaining | Create conflict |
| Underdog | Overlooked, struggles, growth | Root-for narrative |
| Showmance | Romantic pairing | Emotional investment |
| Wildcard | Unpredictable, chaotic | Disrupt dynamics |
| Mentor | Experienced, guiding | Wisdom/tragedy |
| Comic Relief | Entertaining, harmless | Lighten tension |
| Type | Purpose | Signals |
|---|---|---|
| Strategy | Explain gameplay | "My plan is..." |
| Reaction | Emotional response | Eye rolls, laughter |
| Foreshadowing | Hint at outcome | Ominous statements |
| Character | Define personality | Backstory, values |
| Narrator | Guide viewer | Explain events |
Frankenbiting: Splicing audio from different contexts to create new meaning.
Reaction Shot Manipulation: Placing reactions out of context.
Selective Emphasis: Choosing which moments to highlight.
Music/Sound Design: Creating emotional tone.
Track alliances across episodes:
Episode 1: A-B-C vs D-E-F, G floating
Episode 2: A-B vs C-D-E, F-G aligned
Episode 3: ...
Track contestant edit quality across season:
Contestant A: + + + 0 - - - [eliminated]
(positive → negative = villain arc)
Contestant B: 0 0 0 + + + + [winner]
(invisible → positive = winner edit)
references/show-formats.md - Detailed format breakdownsreferences/analytical-terms.md - Glossary of industry and academic termsnpx claudepluginhub a-organvm/a-i--skills --plugin document-skillsProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.