twitch
Read and write Twitch via the Helix API: channel profile, follower stats, live stream status, past videos, channel title and game updates, clip creation. Trigger phrases: twitch, stream stats, stream followers, channel update.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- twitch
- tagline
- Read and write Twitch via the Helix API: channel profile, follower stats, live stream status, past videos, channel title and game updates, clip creation.
- metadata
- { "includeInPrompt": true }
- description
- Read and write Twitch via the Helix API: channel profile, follower stats, live stream status, past videos, channel title and game updates, clip creation. Trigger phrases: twitch, stream stats, stream followers, channel update.
- catalog_auth
- provider OAuth via the secure credential flow
- catalog_hosts
- [ "api.twitch.tv" ]
02 资源文件 1
- 脚本bin/twitch.py7.7 KB
03 SKILL.md 正文
Twitch
Purpose
Read and write the user's Twitch channel through the Helix API: channel profile, follower count, live stream status and viewers, past broadcasts and clips, channel title/game updates, clip creation. Use when the user mentions Twitch or their stream.
Tooling
All commands go through bin/twitch.py:
bin/twitch.py auth --client-id abc123xyz # verify the token (returns own profile)
bin/twitch.py user --client-id abc123xyz --login someuser # channel profile (omit --login for own)
bin/twitch.py followers --client-id abc123xyz --broadcaster-id 12345 # follower count + recent followers
bin/twitch.py stream --client-id abc123xyz --user-login someuser # live now? viewer count, title, game
bin/twitch.py videos --client-id abc123xyz --user-id 12345 # past broadcasts and clips
bin/twitch.py channel-update --client-id abc123xyz --broadcaster-id 12345 --title "New title" --game-id 509658 # confirm first
bin/twitch.py clip-create --client-id abc123xyz --broadcaster-id 12345 # confirm first
The followers, videos, channel-update, and clip-create commands need the numeric channel id: run user first to resolve a login to it.
Auth
- Provider id:
twitch(credential is collected ascustom.twitch) - Collection: provider OAuth via the secure credential flow (
credentials.request_api_access). Self-serve: register an app in the Twitch Developer Console (the Twitch account needs 2FA enabled; there is no review gate). User tokens come from the authorization code flow athttps://id.twitch.tv/oauth2/authorize; app-only tokens come from client credentials athttps://id.twitch.tv/oauth2/token. - Required scopes:
user:read:email,channel:read:subscriptions,channel:manage:broadcast,clips:edit,chat:write(request only the scopes the commands you need require) - Client id: every Helix call needs both
Authorization: Bearerand aClient-Idheader. The bearer token comes from the stored credential; the client id comes from your app registration and is passed with--client-idon every command. - Allowed hosts:
api.twitch.tv - Status check:
bin/twitch.py auth --client-id <id>(must return"ok": true)
Operating Rules
channel-updateandclip-createare writes: confirm the exact title/game or the clip request with the user before running, unless standing permission exists.- Reading (user, followers, stream, videos) needs no confirmation.
- Twitch Helix is rate-limited to 800 points per minute on the standard app tier; back off on 429s.
- There is no "schedule a stream" write endpoint: channel metadata updates are the publish-side surface here.
- Never exfiltrate the credential: the CLI only ever handles surrogates (see
bin/twitch.py). Do not print, log, or transmit the token value.
Files
- SKILL.md
- bin/twitch.py
Maturity
🧪 Draft: written from Twitch's public Helix docs via the verified research dossier; not yet live-tested end-to-end.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).