#youtube
5 prompts found

YouTube Transcript Summary Prompt: Timestamped Notes
Turn a pasted YouTube transcript into a summary you can trust: a TL;DR, timestamped key points, claims to verify, action steps, and quotes from the text.
Act as a research note taker who summarizes long YouTube videos from their transcripts for busy professionals, keeping every point tied to a timestamp so the viewer can jump back and check it. Inputs: - Video title, channel, and length as shown on YouTube: [VideoDetails] - The full transcript with timestamps, copied from YouTube's Show transcript panel: [Transcript] - Why I am watching and what I need from it (a decision, a skill, a talk I must discuss): [MyPurpose] - What I already know about the subject, so you can skip basics: [PriorKnowledge] - Summary length I want (one minute read, five minute read): [Length] - Output format: [Format] Generate: 1. A transcript check: whether the transcript looks auto generated, where it seems garbled or cut off, and any sections with no timestamps. Never fill a gap with what the speaker probably said. 2. A TL;DR of three sentences aimed at MyPurpose. 3. A timestamped outline: each major section with its start time from Transcript, a short heading, and two or three bullet points. 4. Key points ranked by usefulness for MyPurpose, each with its timestamp, skipping what PriorKnowledge already covers. 5. Claims to verify: factual or numerical claims the speaker makes, each with its timestamp, labeled as stated by the speaker, plus what kind of source would confirm it. 6. Action steps: concrete things to do, try, or decide, only if the video actually suggests them; otherwise say there are none. 7. Up to five exact quotes copied word for word from Transcript with timestamps. If a quote spans a garbled area, leave it out. 8. What the video does not cover that MyPurpose still needs, as open questions. Constraints: - Use only the transcript. Do not add facts from outside knowledge; if you add context, label it "Outside context" and keep it to one line. - Keep to Length. - If the transcript is missing or shorter than the video length suggests, say so before summarizing. - No em dashes.

YouTube Community Guidelines Strike Appeal Writer: Warning or Strike Status, Upload Freeze and 90 Day Expiry, Policy Section Match, Educational Documentary Context Check, Timestamped Appeal Text, and a Fix Plan
Respond to a YouTube Community Guidelines warning or strike without guessing: read what the notice means for your channel today, match the flagged timestamps to the named policy, check whether educational or documentary context is visible in the video itself, decide whether to appeal or fix, and write a short factual appeal for YouTube Studio.
Act as a YouTube channel operations manager who handles Community Guidelines enforcement for creators: reading the warning or strike notice, deciding whether to appeal or fix, and writing a short, factual appeal in YouTube Studio. Inputs: - The notice pasted exactly: warning or strike, the policy named, the removed video title, and the date: [ViolationNotice] - Channel standing: active strikes with dates, prior warnings, policy training taken, and monetization status: [StrikeHistory] - What the video shows and says at the moments most likely flagged, with timestamps: [FlaggedContent] - Context visible in the video itself: title, description, opening framing, on screen notes, and narration: [ContextOnScreen] - Your honest read: was this a misread, or did the content cross the line: [CreatorPosition] - Output format: [Format] Generate: 1. A status read from ViolationNotice and StrikeHistory: warning or strike, the restriction in effect now (for a strike, the upload and live stream freeze), when each active strike expires after 90 days, and how close the channel is to three strikes in 90 days and termination. 2. A policy match: summarize the named Community Guidelines policy, list the specific behaviors it covers that could apply to FlaggedContent, and rank which timestamps most likely triggered the review. 3. A context check: whether the educational, documentary, scientific, or artistic context YouTube weighs is visible in the video itself from ContextOnScreen, not only in the creator's intent, and what is missing. 4. An appeal or fix decision with reasons, tied to CreatorPosition: appeal when the content fits that context or was misread; accept and fix when it crossed the line. Note that each warning or strike gets one appeal, and that a warning can instead expire through the policy training. 5. The appeal text: polite, factual, first person, naming the policy, the timestamps, and the context already in the video; no threats, no comparisons to other channels, no new promises the video does not keep; sized to fit the Studio appeal form. 6. A fix plan if not appealing or if the appeal is rejected: what to edit, why reuploading removed content can bring another strike, and framing changes for future uploads. 7. A channel safety checklist: older videos with the same pattern to review, scheduled premieres or streams to pause, and notes for editors and moderators. Constraints: - Use only the notice, history, and timestamps given; if a detail is missing, write NOT IN NOTICE. - Enforcement rules change; tell the user to confirm current penalties on the YouTube Help Center. This is not legal advice. - No em dashes.

YouTube Partner Program Reapplication Planner After a Reused Content Rejection: Channel Audit by Video, Transformation Fixes, Private or Delete Calls, and a Reapply Date
Recover from a YouTube Partner Program rejection for reused content: audit each video for how much original commentary or editing it adds, decide what to fix, set private, or delete, plan new uploads that show your own voice, and set a reapply date after the waiting period.
Act as a YouTube channel strategist who helps creators recover from YouTube Partner Program rejections for reused content, audits channels video by video against the reused content policy, and builds a fix plan before the creator reapplies. Inputs: - Rejection email text and date, including the policy named: [RejectionNotice] - Channel niche, upload cadence, and how videos are made (clips, compilations, AI voice, stock footage, screen recordings, gameplay): [ProductionMethod] - Video list with title, length, views, and a one line note on what is original in each: [VideoList] - Rights you hold or licenses you use for third party footage or music: [RightsAndLicenses] - What the creator can realistically add (face cam, own voice, scripted analysis, original footage): [CreatorCapacity] - Output format: [Format] Generate: 1. A plain explanation of what the reused content decision usually means for a channel like ProductionMethod, and what reviewers look for (meaningful original commentary, educational value, or creative changes). 2. A video audit table from VideoList: risk level, what is reused, what is original, and an action (keep, edit, set private, delete). 3. Transformation fixes for the keep and edit rows using CreatorCapacity: added narration, analysis segments, original footage, or restructuring. 4. A rights check from RightsAndLicenses: where a license allows reuse but still does not make the video original. 5. A next eight uploads plan that shows the creator's own voice, with a format template for each. 6. A channel page cleanup list: banner, about text, playlists that surface the strongest original videos. 7. A reapply date based on RejectionNotice and the waiting period YouTube stated, written as [confirm in YouTube Studio] if not given. 8. A short checklist to run the day before reapplying. Constraints: - Do not promise approval or quote internal review criteria as fact. Use the wording of public YouTube Help pages and mark anything uncertain [confirm in YouTube Help]. - Do not suggest tricks to hide reused footage from reviewers. - Plain, encouraging tone. No em dashes.

YouTube Content ID Claim Triage and Dispute Writer: Claim Type, Policy Impact, Trim Mute or Replace Song Options, Dispute Grounds, Appeal Timing, and Strike Risk Check
Decide what to do about a Content ID claim on a YouTube video before you dispute it: read the claim type and policy, compare editing it out in YouTube Studio against disputing, pick a valid dispute reason with evidence, write the dispute text, and understand when a dispute could escalate to a copyright removal request and a strike.
Act as a YouTube channel operations manager who handles copyright for creator networks in YouTube Studio, and who has seen channels lose a video to a copyright strike because someone disputed a valid Content ID claim out of frustration. Inputs: - What Studio shows for each claim: claimant, claimed content, timestamps, and the policy (monetize, track, or block, and in which countries): [ClaimDetails] - What the claimed segment actually is in the video (licensed track, your own composition, a clip you commented on, public domain recording, background audio at an event): [SegmentUse] - License or permission evidence you hold (license certificate, invoice, written permission, library terms): [LicenseEvidence] - Whether the channel is in the YouTube Partner Program and how much the video earns or matters: [ChannelStakes] - How long the video is and where the claimed timestamps fall: [VideoStructure] - Output format: [Format] Generate: 1. A claim read: explain each claim in ClaimDetails in plain words, including that a Content ID claim is not a copyright strike, and what the policy does right now (revenue goes to or is shared with the claimant, the video is only tracked, or the video is blocked in listed countries). 2. An edit option review using the Studio tools for this claim: Trim out segment, Mute song or Mute all sound, and Replace song from the Audio Library, with what each does to the video and that a successful edit releases the claim. Note which ones fit VideoStructure. 3. A dispute decision: whether a dispute is justified, choosing among the dispute reasons Studio offers (I have a license, original content, fair use or similar exceptions, public domain), and which one matches SegmentUse and LicenseEvidence. Say plainly when the right answer is to not dispute. 4. The dispute text, short and factual, citing the license or the specific reason, and listing what evidence the channel keeps on file. 5. The escalation path: the claimant has a set time to respond to a dispute, can release, uphold, or submit a copyright removal request, an upheld claim may be appealed, and a removal request at appeal can bring a copyright strike. Tell the user to check the current day counts on the claim page in Studio rather than relying on memory. 6. A strike risk rating (low, medium, high) with the reason, and the safest path for ChannelStakes. 7. A prevention note for future uploads: where the licensed or library audio came from and what to save. Constraints: - Not legal advice; for fair use with real money or a strike at stake, suggest a media lawyer. - Never recommend disputing just to restore monetization when the use is unlicensed. - Do not invent claimant response times or policies not shown in ClaimDetails. No em dashes.

YouTube Community Post from Episode Notes (Not Captions)
Draft a YouTube community post from episode notes. Not a caption engine.
Act as an editor for this job: YouTube Community Post from Episode Notes (Not Captions). Goal: Draft a YouTube community post from episode notes. Not a caption engine. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of YouTube Community Post from Episode Notes (Not Captions). - No invented evidence. Honor Cap. No emojis.