show iGaming: a player tutorial video from a website link
Make a tutorial video for a website without recording the screen by hand or editing: give Claude a link to the site and write in plain words what to tap. The skill walks the steps on the mobile version of the site and builds a vertical video with captions. You check it and send it to the player.
How to make a tutorial video for a website in three steps
An example video, about 30 seconds. The account is made up and fully drawn, including the card entry, the payment and the bank reply. On an operator site the skill never presses the payment button: the video ends with a highlight on it.
Write the steps in plain words
A link to the site and what to tap in order, for example: "at the top tap Deposit, choose Bank card, then the amount €50". Plus the video languages and how to address the player: formal or informal.
Claude walks the site like a phone
A browser on your computer opens the mobile version on an iPhone 15 screen, closes ad banners, scrolls to the right section and taps the buttons. After every tap the script checks that the screen changed.
Check and render
Before rendering, Claude reviews a proof sheet: highlights, tap points, screen edges, blur. The video is rendered only after a clean check. Recording takes about a minute, rendering about a minute and a half per language.
Every tap is checked, page loads are cut
The whole iPhone 15 screen
The mobile version of the site at 2x. The status bar, bottom menu and screen edges are visible, nothing is cropped.
Highlights from the page
The step highlight comes from the page itself: the exact button bounds and corner radius. It never slides onto neighbouring elements.
Verified taps
If a button is missing or a tap changes nothing, the recording stops with a screenshot. When two buttons look the same, Claude asks which one you mean.
No waiting for loads
Page loads are cut and long scrolls are sped up. If a section is below the screen, the skill scrolls to it as a separate captioned step.
What you get: video, poster, step text and a support reply
Each interface language gets its own recording, so the caption names the button exactly as it reads on screen. All files land in one folder.
- A 1080x1920 video at 60 frames per second, one file per language
- A poster and the steps as text for a chat reply or a knowledge base article
- A card: the player questions the video answers, a ready support reply and the recording date
- Your style: brand colours, logo and fonts in the intro, captions and ending. Claude can take them from your site
The demo video folder: this is what you get in three languages.
Logged-in scenarios with a regular or VIP test account
How to sign in
- Claude opens a separate Chrome window with the site in mobile view.
- You sign in to the test account yourself and close the window. Only you see the password and codes: the script never types or stores them.
- The login is kept in a separate profile folder, and the next recordings run in that account. If the site session expires, sign in again.
Regular and VIP accounts
Each account gets its own profile folder. That way the same scenario is recorded for a regular player and for a VIP program level.
Your main Chrome profile is never used: since version 136 Chrome does not let scripts drive it. Your cookies and tabs stay as they were. Use a test account only, never a real player account.
Personal data and payment buttons
Money buttons are never pressed
The script never presses payment, withdrawal or bet buttons. The video ends with a highlight on that button: the player sees where to tap, and no money leaves the test account.
Blur before capture
In a test account, emails, phone numbers, card numbers and the **** 1234 mask, IBANs, player IDs and email, phone and password fields are blurred in the page itself. Anything else to hide, such as a name or the balance, goes in a list.
A proof sheet before rendering
Blur is a safety net. The sheet holds the key frames: the moment before each tap, the result and the ending. Claude checks it before rendering, and you look at the sheet and the finished video before sending. Payment forms inside another site's frame get blur zones that Claude places by hand, and you see them on the sheet.
Everything stays on your computer
Recordings, videos and logged-in profiles stay with you, and nothing is uploaded. The skill never signs up, never accepts terms or age gates, and only ever declines cookies.
Who it is for: support, CRM and retention, product
Support
Answer questions about deposits, withdrawals and verification with one video in the chat, plus a ready reply text. When a payment fails, support sends a video on how to deposit another way. Who writes to the player and when is in the support playbook for declined deposits.
CRM and retention
A video in the onboarding flow before the first deposit, in a reactivation message and in the knowledge base. Another skill shows why newcomers do not come back after the first deposit: why FTDs skip the second deposit.
Product
A short video on a new release: how the new cashier works, where to set a limit, where a profile section moved. A tester's walkthrough recording is reviewed by the watch skill: check a walkthrough recording and build a QA table.
Install the skill from GitHub
Option 1. Let Claude install it
Open Claude Code and paste this text:
Install the show skill from https://github.com/igamingsychov/show-igaming : 1. Clone the repository into ~/.claude/skills/show. If that folder already exists, ask me what to do. 2. Check python3, ffmpeg and Chrome with python3 ~/.claude/skills/show/scripts/show.py check. If anything is missing, show me the install commands and ask for permission. 3. Tell me when you are done and what to type to test it.
Option 2. One terminal command
Puts the skill where Claude Code looks for it:
git clone https://github.com/igamingsychov/show-igaming.git ~/.claude/skills/show
Option 3. The plugin catalog
Two commands inside Claude Code:
/plugin marketplace add igamingsychov/sychov-igaming-skills /plugin install show-igaming@sychov-igaming-skills
How to use it
Example requests
- make a tutorial video: how to deposit with a card on https://your-site, informal
- a video for support: how to withdraw, VIP test account, Ukrainian and English
- show the player where to upload verification documents, brand style from the site
- a video for a newsletter: where to set a deposit limit, formal
Limits
- The site needs a mobile version.
- The script does not pass bot checks. You pass them in the sign-in window, and the recording runs in the same profile.
- If the site is closed in your country, run the recording from a country where it opens.
- Payment forms inside another site's frame are blurred only by zones that Claude places by hand.
- Windows is not supported yet.
Questions and answers
Can Claude Code make videos?
With this skill, yes. You give Claude Code a website link and the steps in plain words. It opens the mobile version of the site on an iPhone 15 screen, taps through the steps, checks each one and renders a 1080x1920 video at 60 fps with ffmpeg on your computer.
How do I install Claude Code skills from GitHub?
Clone the repository into the skills folder: git clone https://github.com/igamingsychov/show-igaming.git ~/.claude/skills/show. Or use the plugin catalog: /plugin marketplace add igamingsychov/sychov-igaming-skills, then /plugin install show-igaming@sychov-igaming-skills. To test it, open a new session and type: make a demo video with the show skill.
How long does one video take?
Recording takes about a minute and rendering about a minute and a half per language. Each language gets its own recording, so the caption names the button exactly as it reads on that screen.
How do I blur sensitive information in a tutorial video?
In a test account the skill does it for you. Emails, phone numbers, card numbers and the **** 1234 mask, IBANs, player IDs and email, phone and password fields are blurred in the page before a frame is captured. You can add more items by text or CSS selector. Payment forms inside another site's frame get manual blur zones, and you see them on the proof sheet.
Does it press the payment button?
No. Payment, withdrawal and bet buttons are never pressed. The video ends with a highlight on that button, so the player sees where to tap and no money leaves the test account.
Does it work on Windows?
Not yet. You need Claude Code on macOS or Linux, python3, ffmpeg and Chrome. Everything runs on your computer and nothing is uploaded.
More skills for your team
watch iGaming watches a screen recording and builds a QA table. second deposit finds in your exports why FTDs skip the second deposit.
License
MIT license: use it and adapt it. Author: Yevhen Sychov.

