Skip to content

ANALYSIS_PROMPT.md

Latest commit

 

History

History
77 lines (60 loc) · 5.21 KB

ANALYSIS_PROMPT.md

File metadata and controls

77 lines (60 loc) · 5.21 KB

Transcript Summary Prompt Template

Summarize this transcript entitled: [TITLE]

  • Analyze this transcript based solely on its content. Do not incorporate prior knowledge about the channel, speaker, or their typical positions.
  • If domain-specific terminology requires explanation, define it based on context within the transcript.

CONTENT INGESTION REQUIREMENTS:

  • Before writing any summary, read the ENTIRE transcript using the Read tool.
  • If the transcript is large, use the offset and limit parameters of the Read tool to fetch remaining content in chunks.
  • Continue fetching until you have read every line. Do not begin summarizing until the full text has been ingested.

TRANSCRIPT FORMAT:

  • The transcript is provided in WebVTT (.vtt) format, which includes timestamps for each segment.
  • Use these timestamps to anchor your analysis to specific moments in the video.
  • When citing timestamps, use [HH:MM:SS] format (second resolution, no sub-seconds). For ranges, use [HH:MM:SS--HH:MM:SS] with double hyphens (--) as the separator, not an en-dash.
  • When a concept, claim, or fallacy spans multiple consecutive segments, cite the full range covering the relevant passage.
  • In markdown headings (#, ##, ###), timestamps appear without backticks. In all other text (bullet points, prose), wrap each timestamp in backticks for readability.

OUTPUT FORMAT: Maintain neutral, descriptive tone; do not endorse or criticize the speaker's views. Provide a structured summary with the following sections:

Overview

A 3-5 sentence high-level summary of the video's thesis and scope.

Source Material

  • Source: [SOURCE]

Formatting rules for this section:

  • If the source is a URL, render it as a markdown link: [URL](URL) (the link text and href are identical).
  • If the source is a local file path, render it as inline code: `filename`.
  • Always use exactly one bullet point with the bold label Source: followed by the value.
  • Do not add any additional commentary, description, or metadata to this section.

Key Terms and Concepts

A list of important terms, concepts, or frameworks introduced by the speaker, each with a definition or explanation based on what the speaker said or what can be directly inferred from context. Include the timestamp of the first mention. Use the format:

  • Term [HH:MM:SS]: Definition

Detailed Summary

A comprehensive section-by-section summary of the content, using subheadings to organize major topics or shifts in the discussion. Include a timestamp range for each subheading indicating the span of that section. Aim for thoroughness over brevity. Use the format:

Section Title [HH:MM:SS--HH:MM:SS]

Scripture References

(Include this section only if the content is theological) List any Bible verses or passages mentioned, with brief context on how the speaker used them. Include all timestamps where each verse is referenced (not just the first mention), as speakers often introduce a verse in one context and revisit it later. Use the format:

  • Verse [HH:MM:SS], [HH:MM:SS], ...: Context of how the speaker used it.

Evidentiary Notes

Flag notable claims and categorize the type of support the speaker provides. Include a timestamp or timestamp range indicating where the claim and its supporting evidence appear. A claim and its evidence may span multiple segments; cite the full range. Use the format:

  • Category [HH:MM:SS--HH:MM:SS]: Description of the claim and evidence.

Categories:

  • Anecdotal: Personal experience or observation ("In my experience...")
  • Appeal to authority: References another person's opinion without a direct source ("DHH believes...")
  • Logical argument: Reasoned case without external data
  • Cited source: Specific study, article, data point, or verifiable reference

Logical Fallacies

Identify any logical fallacies present in the speaker's reasoning. If none are detected, state "No significant logical fallacies detected." IMPORTANT: Only flag fallacies that significantly weaken the argument; rhetorical flourishes are not necessarily fallacies.

For each fallacy found, include a timestamp or range covering the relevant passage (premise through conclusion). A fallacy may involve a premise stated at one point and a conclusion drawn later; cite the full span. Use the format:

  • Fallacy type [HH:MM:SS--HH:MM:SS]: Brief description of where/how it appears in the argument and why it weakens the reasoning.

Common fallacies to watch for:

  • Ad Hominem (attacking the person rather than the argument)
  • Straw Man (misrepresenting an opposing view to make it easier to attack)
  • False Dichotomy (presenting only two options when more exist)
  • Appeal to Emotion (relying on feelings rather than logic)
  • Whataboutism/Tu Quoque (deflecting criticism by pointing to others' behavior)
  • Slippery Slope (assuming one thing will inevitably lead to extreme consequences)
  • Hasty Generalization (drawing broad conclusions from limited examples)
  • False Authority (citing unqualified sources as experts)

Questions and Underdeveloped Areas

List any points that seemed ambiguous, underdeveloped, or warrant further exploration. Include a timestamp or range indicating where the ambiguity or gap occurs. Explicitly state when interpretations are uncertain.