Skip to content

DirectorySkills

Run 1Browser window chapter“Open the "What we tried" part of talk.mp4 with a chapter in a browser window.”
Runs in
  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI
  • GitHub Copilot
  • OpenCode
Generates with
Your agent's model
Tested with
Claude Code 2.1.322Claude Sonnet 5.51 real run, 9 Nov
Needs
Node 22+Chromeffmpeg
Licence
Recaply licence

Browser Window Chapter

A browser window rises with its address typing in and the chapter title set inside it.

$9.99once, yours to keep

Adds a chapter title inside a browser window on a talking-head video: the window rises, its address types in and the title lands on the page. Timed to the words they say, on their own footage, with their sound kept; 16:9, 9:16, 1:1 or 4:5. Renders locally with Chrome and ffmpeg: no video model, no key and no cost. Use when someone makes videos about websites, tools or online work and wants chapter titles that look like a page opening.

By RecaplyUpdated 11 Nov

Install Browser Window Chapter

After the download, ask your agent to add it, or run the line yourself.

Read https://recaply.co/skills/browser-chapter-overlay/install.md and follow it to install the browser-chapter-overlay skill from browser-chapter-overlay.zip.

Paste it into your agent. It reads our install steps, finds the ZIP you downloaded and adds the skill for you.

New to skills? How to install a skill

Similar skills

All 735 skills

Who Browser Window Chapter is for

What you get

  • Your video with the overlay timed to the words, sound kept
  • Each part lands as they say it, placed from the transcript
  • 16:9, 9:16, 1:1 or 4:5

Good fit

  • When someone makes videos about websites, tools or online work and wants chapter titles that look like a page opening

Not for

  • Footage with nobody speaking
  • Cutting or re-editing the video itself

About this skill

You say

Open the "What we tried" part of talk.mp4 with a chapter in a browser window.

It said back

The chapter is added: a browser window rises, types its address and lands the title "What we tried" on the page.

  • Video: talk-graphics.mp4 in the working folder, 1920x1080, 30 fps, 24.3 s. The sound is yours and unchanged.
  • Beat: it is tied to "So we tried three things" (about 9.66 s). The graphic runs from 9.5 s to 12.3 s and covers the frame while the speaker keeps talking.
  • Address: team.example/what-we-tried. It's a made-up plain path, not a real site.
  • Look: paper, with the face position set to [49, 30].
  • Checks: the check pass found no warnings or notes, and I looked at the settled frame, which reads cleanly.
  • Settings: overlay.json holds them if you want to change the title, address or look.
Show more

What it did in run 1

  1. browser-chapter-overlay
  2. ls -la
  3. S=.claude/skills/browser-chapter-overlay/scripts && node $S/check.mjs; echo '{"video":"talk.mp4","transcript":"talk.json","beats":[]}' > overlay.json; node $S/overlay.mjs overlay.json --words
  4. node .claude/skills/browser-chapter-overlay/scripts/check.mjs; echo '{"video":"talk.mp4","transcript":"talk.json","beats":[]}' > overlay.json; node .claude/skills/browser-chapter-overlay/scripts/overlay.mjs overlay.json --words
  5. cat > overlay.json <<'E' {"video":"talk.mp4","transcript":"talk.json","look":"paper","beats":[{"beat":"chapter","cue":"So we tried three things","style":"browser","title":"What we tried","url":"team.example/what-we-tried","for":2.8}]} E node .claude/skills/browser-chapter-overlay/scripts/overlay.mjs overlay.json --face; node .claude/skills/browser-chapter-overlay/scripts/overlay.mjs overlay.json --check
  6. ./overlay.json
  7. node .claude/skills/browser-chapter-overlay/scripts/overlay.mjs overlay.json --face 10
  8. ./face-check.png
  9. ./overlay.json
  10. node .claude/skills/browser-chapter-overlay/scripts/overlay.mjs overlay.json --check
  11. ./overlay-check.png
  12. node .claude/skills/browser-chapter-overlay/scripts/overlay.mjs overlay.json
  13. Done

9 Nov 2026 · Claude Code 2.1.322 with Claude Sonnet 5.5 · 1 min 36 s · $0.12 of API use

Questions

Is Browser Window Chapter free?

No. Browser Window Chapter costs $9.99 once and stays in your Recaply account, or it comes with the Recaply plan ($19.99 a month), which opens every premium skill and prompt.

Which agents can use Browser Window Chapter?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode.

What do I get when I buy Browser Window Chapter?

A ZIP of the whole skill folder (105 KB): the SKILL.md your agent follows and its 12 other files, the references, templates and scripts it uses. You download it from this page whenever you need it, and install it in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode. The Recaply plan opens it too, with every other premium skill and prompt.

How do I install Browser Window Chapter?

Buy it, then download the ZIP from this page. For Claude Code, unzip it into .claude/skills/ in your project. For Codex, Cursor and Gemini CLI, unzip it and run npx skills add ./browser-chapter-overlay with your agent's flag.

What do I get from Browser Window Chapter?

Your video with the overlay timed to the words, sound kept. Each part lands as they say it, placed from the transcript. 16:9, 9:16, 1:1 or 4:5.

What does Browser Window Chapter need?

Node 22+, Chrome and ffmpeg, and no API key. Each use costs nothing beyond your agent.

How big is Browser Window Chapter?

13 files, about 79,983 tokens in all. The SKILL.md is about 2,320 tokens, and your agent reads it only when the job fits.

What does a run cost?

Our 1 runs took 1 min 36 s to 1 min 36 s and $0.12 to $0.12 of API use each, in Claude Code with claude-sonnet-5-5. On a Claude plan, a run counts toward your usage instead.

Do I have to name Browser Window Chapter to use it?

Type /browser-chapter-overlay first to make sure it loads. Without it, Claude Code may judge a small job simple enough to do without the skill.