github-video-embed skill
Make a video, screen recording or demo clip play inline inside a GitHub Markdown file, pull request or release. Use when a video must play in the README or a PR, when asked to embed a video or add an inline player, or when a committed video renders blank.
- GitHubスター
- 5
- ファイル
- 1
- 最終コミット
- 2026年11月10日
- ライセンス
- GPL-3.0
- 許可されたツール
- —
github-video-embed skillは何をしますか
Make a video, screen recording or demo clip play inline inside a GitHub Markdown file, pull request or release. Use when a video must play in the README or a PR, when asked to embed a video or add an inline player, or when a committed video renders blank.
github-video-embed skillのインストール方法
各コマンドはskillフォルダをクライアントのskillsディレクトリにコピーします。読み込むには、クライアントを再起動するか新しいセッションを開始してください。プラグインにgithub-video-embed skillをインストールする
/plugin marketplace add GeiserX/sstack /plugin install sstack@sstack
Claude Codeにgithub-video-embed skillをインストールする
~/.claude/skills/github-video-embed/SKILL.md
$ npx degit GeiserX/sstack/skills/github-video-embed ~/.claude/skills/github-video-embedClaude Code (project)にgithub-video-embed skillをインストールする
.claude/skills/github-video-embed/SKILL.md
$ npx degit GeiserX/sstack/skills/github-video-embed .claude/skills/github-video-embedCodexにgithub-video-embed skillをインストールする
~/.agents/skills/github-video-embed/SKILL.md
$ npx degit GeiserX/sstack/skills/github-video-embed ~/.agents/skills/github-video-embedGemini CLIにgithub-video-embed skillをインストールする
~/.gemini/skills/github-video-embed/SKILL.md
$ npx degit GeiserX/sstack/skills/github-video-embed ~/.gemini/skills/github-video-embedClaude.aiにgithub-video-embed skillをインストールする
npx degit GeiserX/sstack/skills/github-video-embed github-video-embed && zip -r github-video-embed.zip github-video-embed # claude.ai → Customize → Skills → + → Create skill → Upload a skill → github-video-embed.zip
SKILL.md
GitHubで表示github-video-embed
The reader should press play inside the same .md file, without leaving the page, and anyone with access
to the repository should see the player. GitHub renders an inline <video> player only for a
GitHub-hosted attachment URL.
The rule
Put a bare https://github.com/user-attachments/assets/<uuid> on its own line in the .md. GitHub turns
it into a <video> player.
These render blank or get stripped:
- a raw committed-file URL (
.../raw/...) - a release asset URL (
releases/download/...) - a
<video src="...">tag pointing at either of them
Committing the .mp4 under docs/ is still worth doing as the source of truth, but it is not what the
page shows.
Getting the attachment URL
The upload needs a signed-in browser session. A personal access token cannot do it: the upload policy
endpoint (/upload/policies/assets) answers 422.
- Export your own signed-in browser session's GitHub cookies, used once for this upload and shredded
afterwards. Include
_gh_sess: it is a session cookie held only in browser memory, never in the cookie database on disk, so take it from the live browser, not from the profile folder. - Start a Chromium browser headless with
--remote-debugging-portand a temporary--user-data-dir, and drive it over the DevTools protocol (Node 22 and later have a globalWebSocket, so no extra package is needed). - Call
Network.setCookiefor every cookie, keeping its domain, path, secure, httpOnly and sameSite values, then navigate to GitHub. Check thatmeta[name=user-login]shows the expected account. - Open a classic Markdown editor page: the release notes editor (
/releases/edit/<tag>), a wiki page, or a commit comment. Not/issues/new: that page mounts its editor late and exposes no file input headless. The release editor has a plaintextarea[name="release[body]"]and aninput[type=file]. - Call
DOM.setFileInputFileswith every file on thatinput[type=file], then poll the textarea until theuser-attachments/assets/<uuid>URLs appear. The upload happens at once. Do not save or submit the form: the release stays unchanged, but the file is already uploaded, and in a public repository its URL works without signing in. Do not use this for a video that must stay private until a later date. - Put each bare URL on its own line in the doc, then commit and push.
There is no bundled uploader; the steps above are the recipe.
Verify, then scrub
Fetch the rendered page with the same session and count the players:
curl -s -b "$COOKIE_JAR" "https://github.com/$OWNER/$REPO/blob/$BRANCH/$DOC_PATH" | grep -o '<video' | wc -l
The count must equal the number of videos. Then delete the cookie export with shred -u (or your
platform's secure delete) and remove the temporary --user-data-dir: both hold a live session.
Alternative
A self-contained HTML page with the videos inlined as data: URIs plays anywhere with no upload. It only
reaches the people you send it to, so it does not suit docs that a whole team reads in the repository.
このスキルのファイル
1github-video-embed skillに関する質問
Claude Codeにgithub-video-embed skillをインストールするには
npx degit GeiserX/sstack/skills/github-video-embed ~/.claude/skills/github-video-embedを実行してください。Claude Codeは~/.claude/skills(すべてのプロジェクト)または.claude/skills(単一プロジェクト)からskillsを読み込み、説明がタスクに一致する場合にskillを使用します。
github-video-embed skillはどのクライアントで使用できますか
Agent Skills形式を読み込むすべてのクライアントで使用できます: Claude Code、Codex、Gemini CLI、claude.ai(ZIPとしてアップロード)。skill内のスクリプトは、クライアントがコード実行を許可した場合にのみ実行されます。