Skip to content
Back to skills

Twitch

ASecurity

Use when working on anything Twitch or live-streaming — channel setup, OBS and encoder settings, growth, chat, monetization, moderation, the Twitch API/EventSub, or DACH legal duties.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 4, 2026
developmentgoapi

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 20 files and shows the line behind each finding

Scanned October 4, 2026

npx -y skills add Getty/skills --skill twitch --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Twitch?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Twitch
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/getty-twitch/badge)](https://www.skillsdirectory.com/skills/getty-twitch)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: twitch
description: "Use when working on anything Twitch or live-streaming — channel setup, OBS and encoder settings, growth, chat, monetization, moderation, the Twitch API/EventSub, or DACH legal duties."
---

# Twitch

Working knowledge of Twitch as a platform: what exists, what changed recently, what the
numbers actually are, and what a streamer is legally required to do in DACH.

**Two things this skill exists to prevent**, because a model without it gets both wrong:

1. **Stale monetization facts.** In May–June 2026 Twitch opened subs, Bits, emotes, badges and
   Channel Points to *all* streamers and lowered the Affiliate bar. Almost every guide
   online predates that. Never answer monetization questions from memory —
   read `references/monetization.md`.
2. **US-default legal answers for German streamers.** A regular livestream is *Rundfunk* under
   German law, with a licence threshold, broadcast-grade youth-protection time slots, and ad
   labelling duties that have no US equivalent. See Jurisdiction below.

## Jurisdiction

Ask first: is the streamer, their company, or their audience in Germany, Austria or
Switzerland? If yes, read the relevant files below **before** advising on licensing,
advertising, taxes, music, data protection or minors. Do not answer from general knowledge —
these rules have no US equivalent and getting them wrong is expensive for the streamer.

| Topic | File |
|---|---|
| Broadcasting licence (MStV), legal notice / Impressum (§5 DDG, §18 MStV), GDPR on stream | `references/germany-legal.md` |
| Youth protection, age ratings, broadcast time slots (JMStV) | `references/germany-youth-protection.md` |
| Ad labelling, sponsorships, gambling (§22 MStV, UWG, GlüStV) | `references/germany-advertising-and-gambling.md` |
| Gewerbe, VAT/Kleinunternehmer, donations, W-8BEN, payouts | `references/germany-taxes-and-business.md` |
| Music rights, GEMA, GVL, DMCA | `references/germany-music-and-copyright.md` |
| Market size, scene, events, viewing habits, Du/Sie | `references/germany-market-and-culture.md` |

Austria and Switzerland differ from Germany on most of these; each file says where. None of it
is legal advice — the files state the law and the authorities' guidance, and flag where a
Steuerberater, Rechtsanwalt or Landesmedienanstalt has to be asked.

## Reference index

| Topic | File |
|---|---|
| Account, identity, metadata, roles, first stream | `references/channel-setup.md` |
| Encoder, bitrate, Enhanced Broadcasting, Dual Format, scenes, network | `references/broadcasting-and-obs.md` |
| Discovery Feed, clips, categories, tags, raids, the growth funnel | `references/discovery-and-growth.md` |
| Overlays, run of show, segments, failure drills | `references/stream-design-and-run-of-show.md` |
| Chat modes, Channel Points, Power-Ups, emotes, mods, guests | `references/community-and-chat.md` |
| Subs, Bits, Hype Trains, sponsorships, Drops, splits, payouts | `references/monetization.md` |
| AutoMod, Shield Mode, hate raids, policy strikes | `references/moderation-and-safety.md` |
| Helix, EventSub, PubSub deprecation, bots, tooling | `references/developer-and-tools.md` |
| Formats: gaming, coding, IRL, music, talk, subathons | `references/content-types.md` |
| Metrics, what they mean, the review loop | `references/analytics.md` |
| Terms | `references/glossary.md` |
| Every dated fact with its source | `references/sources.md` |

Templates: `templates/obs-scene-collection.md` · `templates/run-of-show.md` ·
`templates/stream-checklist.md`

## Core rules

- **Date every volatile fact.** Thresholds, splits, bitrates and feature availability move.
  State the verification date and the source, or say you are unsure. `references/sources.md`
  carries the dates.
- **Never invent numbers.** No made-up viewer counts, revenue figures, dates, or "typical"
  results. Use a placeholder and ask.
- **Distinguish platform policy from law.** A Twitch Content Classification Label is not a
  German youth-protection measure; Twitch's gambling policy is not the GlüStV; DMCA is not
  GEMA. Conflating them is the most common serious error.
- **Calibrate against the streamer's own data**, not published benchmarks. Twitch analytics
  from four comparable streams beat any blog's median.
- **Growth advice must name the funnel stage.** "Get more viewers" is not actionable; "your
  reach is fine and your retention is broken" is.

## Common workflows

**Auditing an existing channel**
1. Metadata: title, category, tags, CCL, schedule — `references/channel-setup.md`
2. Stream health: Twitch Inspector, bitrate, transcoding — `references/broadcasting-and-obs.md`
3. Funnel: which stage is broken — `references/discovery-and-growth.md` + `references/analytics.md`
4. Money left on the table: participation features not turned on — `references/monetization.md`
5. DACH: legal-notice, labelling, youth-protection slots — Jurisdiction files above

**Setting up a new channel**
`references/channel-setup.md` → `references/broadcasting-and-obs.md` →
`templates/obs-scene-collection.md` → `templates/stream-checklist.md` → Jurisdiction files
before the first monetized stream.

**Building a bot or integration**
`references/developer-and-tools.md` first — it lists what is deprecated. Do not start on
PubSub. If chat data leaves the machine, read the data-protection section of
`references/germany-legal.md`.

Files in this skill

  • SKILL.md5.5 KB
  • references/analytics.md3.2 KB
  • references/broadcasting-and-obs.md4.4 KB
  • references/channel-setup.md4 KB
  • references/community-and-chat.md3.3 KB
  • references/content-types.md2.5 KB
  • references/developer-and-tools.md3.6 KB
  • references/discovery-and-growth.md4.4 KB
  • references/germany-advertising-and-gambling.md4.6 KB
  • references/germany-legal.md6 KB
  • references/germany-market-and-culture.md3 KB
  • references/germany-music-and-copyright.md4.8 KB
  • references/germany-taxes-and-business.md5 KB
  • references/germany-youth-protection.md3.5 KB
  • references/glossary.md3 KB
  • references/moderation-and-safety.md3.6 KB
  • references/monetization.md7 KB
  • references/sources.md5.6 KB
  • references/stream-design-and-run-of-show.md2.8 KB
  • templates/obs-scene-collection.md3.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…