#youtube
2 prompts found
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.