roblox-in-this-town
Free Claude skill for viral Roblox story shorts ("In this town, ..."): the foundation, measured rules, a style menu and ~75 solved pitfalls.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/lasenu--roblox-in-this-town)HTML
<a href="/listings/lasenu--roblox-in-this-town"><img src="/api/listings/lasenu--roblox-in-this-town/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Copy this folder to `~/.claude/skills/roblox-in-this-town/` (or into your project's `.claude/skills/`). Then tell Claude: *"Help me make Roblox story shorts"*, or paste your story: *"Make an In This Town short: In this town, ..."*.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 98 lines
- ---
- name: roblox-in-this-town
- description: Know-how and workflow for making viral-quality vertical (9:16) narrated Roblox story shorts ("In this town, ..." and similar) with Claude driving Roblox Studio over MCP - what goes viral and what does not (measured), how to build places, characters, faces, acting, camera moves, effects, voice, captions and quality checks, and the known pitfalls with their fixes. Use when the user wants to make Roblox story videos, an "In this town" short, a Roblox TikTok/YouTube Short with narration, or asks how such videos are made. The user brings the story and their style; this skill gives the technical foundation and measured defaults so the production does not hold the story back.
- ---
- # Roblox story shorts ("In this town, ...")
- This skill is knowledge and a workflow, not a template. It tells you what viral Roblox story shorts have in common, what to avoid,
- how to build every piece, and where things silently go wrong. You build the user's own tools, places, characters and faces with them,
- in their style. Nothing here should make two users' videos look the same.
- ## Principles
- 1. **The story is king.** Hits share a production baseline (`references/viral_patterns.md`); the story decides. Protect the baseline, help
- sharpen the story, never replace the user's idea with your own.
- 2. **The voice is the clock.** Script -> voice -> word times -> every event anchored to a spoken word.
- 3. **Places, not shots, and places full of their people.** Few places, revisited; each place has the people who belong there; cut only for a
- reason. The tested default camera travels through a place like a player camera (wide lens, above head height); other camera styles are
- in `references/styles.md`.
- 4. **Look before you show.** Stills of every camera position, the first 3 s as a 0.25 s strip, faces at full size. The camera inside a tree,
- a wall or a person, and faces turned away from the camera (profile, backs of heads), are the most common failures.
- 5. **One place first.** Build and render place 1 (5-15 s), get the user's yes, then the rest. Change one thing at a time.
- 6. **Readable beats busy, and surprising beats flat.** In every style the viewer must see at once who, where and what happens. Within that,
- stage each sentence as boldly as it allows: bigger, funnier, stranger (`references/directing.md`). Never add story the script does not
- have. Random extras, effects and cuts that serve nothing made the author's test videos worse.
- 7. **Never upload images to Roblox without the user's consent, never use other creators' images, characters, scripts or videos.**
- ## What is fixed and what is free
- Keep these three layers apart, also when you talk to the user:
- 1. **Technical foundation - always.** How Roblox Studio, rendering, voice and assembly break, and the fixes (`troubleshooting.md`, `pipeline.md`).
- This is not taste: a flickering body, a camera inside a wall or captions out of sync are broken in every style.
- 2. **Measured baseline - the default.** What viral shorts of this kind had in common in November 2026 (`viral_patterns.md`): a readable face
- early, few places, captions, a clear voice. Formats move; break a point on purpose if the user wants to, and look at the result.
- 3. **Style - the user's.** World, body type, faces, camera style, captions, voice, tone, graphics, music. The numbers in this skill describe
- the tested defaults, not the only way. Offer the options in `styles.md`, build one sample in the chosen style, let the user judge it.
- ## Workflow
- **Once per user (setup)** - if the user's tools already exist, read their `TOOLS.md` and go straight to the per-video steps:
- 1. Check the environment: Roblox Studio with its built-in MCP server connected to Claude (Studio's Assistant settings, "MCP Servers";
- Roblox's guide: create.roblox.com/docs/studio/mcp), a place file saved under a clear name, Python 3.10+, ffmpeg.
- In that place set `StarterPlayer.AvatarJointUpgrade = Disabled` by hand (code poses need classic joints).
- 2. Build the user's tools in their project folder, small and testable (`references/pipeline.md` describes one proven way and its traps;
- adapt it freely): Studio client, Luau modules, plan resolver,
- stills tool, render loop, assembly, voice, quality report. Run a two-sentence story through the whole chain once, then write `TOOLS.md`.
- Reuse them for every video.
- 3. Agree on their style (`references/styles.md`): first the colour look as a picture choice (one sample corner rendered in three looks),
- then at most 2-3 questions about feeling and taste and links to creators they like. Change the sample until they say yes.
- Unchosen areas stay on the defaults.
- 4. Build their cast: if they want a recurring hero, 2-3 options in their style, shown as a sheet; the user picks; save it. Draw their face set (`references/characters_and_faces.md`).
- 5. Build the places their stories need (`references/world_and_light.md`). New stories add places over time.
- **Per video:**
- | # | Step | Read |
- |---|---|---|
- | 1 | Story: idea -> script. Rule stories: rule, hero, planted details, escalation, twist; other stories keep their own shape. **User approves.** | `story.md`, `viral_patterns.md` |
- | 2 | Voice and word times (local text-to-speech or the user's recording) | `pipeline.md` 7 |
- | 3 | Places and cast needed by this story (reuse, add what is missing), each place with its own people and the story's props | `world_and_light.md`, `characters_and_faces.md` |
- | 4 | Plan **place 1 only**: per sentence what the viewer sees and the idea that makes it worth watching, camera route, beats per character, effects | `directing.md`, `camera_and_shots.md`, `animation_and_effects.md`, `pipeline.md` 6 |
- | 5 | Measure composition (people in frame, close-up share, field of view), one stills sheet; fix in one pass | `troubleshooting.md`, `pipeline.md` 9 |
- | 6 | Render place 1 + assemble, look at it yourself -> **user approves**. While they watch, build and check place 2 (do not render it yet) | `pipeline.md` 2, 8 |
- | 7 | Plan the other places the same way (measure, one sheet each), render all in the background, assemble, quality report, fix, show | `pipeline.md` 9 |
- ## Token and time budget
- In the author's runs (toolkit already built) most of the time went into the model reading and writing, not into the scripts: the first
- video took 48 minutes to the approved first place. With the rules below, the next one (74 s, 4 places, 46 shots) took 30 minutes to that
- point and 76 minutes in total, 32 of them rendering.
- - **One video = one fresh chat.** Never continue a long conversation or fork one: every step re-reads the whole history.
- - **Keep a one-page command sheet** (`TOOLS.md`) next to the user's tools: commands, measured times, existing places and anchors, cast
- options. Read it instead of the source code (reading the whole source once cost about 15 minutes, and it stays in context).
- - **Plan place by place.** Write the plan for place 1 only, take stills, render it, get the user's yes, then plan the rest. A whole
- 50-shot plan in one message was the biggest single cost, and every fix after the stills rewrote it.
- - **Short plans through good defaults:** the scene code's default framing is the player camera; write sizes only for accents.
- Fix plans with small edits, not with scripts that rewrite the file.
- - **Measure before you render:** the composition check (people in frame, close-up share, field of view) runs in seconds from the plan and
- finds "too close, only one person" before a 15-minute render does.
- - **Stills: one sheet per place** (8-12 frames), fix everything you see on it in one pass, then confirm only the frames you changed.
- Looked-at pictures are the biggest token cost of a video; keep sheets small (about 1400 px wide is enough to judge).
- - Read a reference when you reach its step, not all at once. `craft.md` (film craft with sources, long) only for specific questions: search it.
- - Never pose and capture frames one tool call at a time: the render loop is a script running in the background (~0.3-0.9 s per frame;
- a 60-75 s video takes ~15-35 minutes). Wait for it to finish; do not poll.
- - Read the quality report as text first. Things made once per user (tools, hero, face set, places in the saved place file) are reused, never rebuilt.
- ## Talking to the user
- - Talk in their language. Ask once which language the video's voice and on-screen text should be in, and keep it.
- - Ask about feelings and choices they can judge ("should the shock feel bigger?", "which hero?"), never about technique; give one recommendation.
- - After criticism: measure and look first, then change one thing, then show the same moment again. Keep every version; never overwrite an approved one.
- ## References
- - `references/styles.md` - the style menu: options per area (world, body, faces, camera, captions, voice, tone, graphics, music) and how to choose
- - `references/directing.md` - staging each sentence so it is funny, exciting, mysterious, eerie or warm, without adding story
- - `references/viral_patterns.md` - what hits do and weak videos do not (story, hook, places, camera, look, cast, faces, captions, sound)
- - `references/story.md` - structure, writing rules, hook check
- - `references/camera_and_shots.md` - shot size per sentence, move or cut, routes, distances, 9:16 framing, keeping the camera out of things
- - `references/world_and_light.md` - finding and loading kits safely, building places, life, mood light, colour
- - `references/characters_and_faces.md` - dressing R6 by code, the cast system, drawing a face set, sharp faces in Studio, dosing
- - `references/animation_and_effects.md` - stepping animations, poses, acting timing, flicker-free effects
- - `references/pipeline.md` - what to build and how it fits together, with code for the traps (Studio MCP, rendering, camera, faces, light, voice, assembly, QA)
- - `references/craft.md` - film craft research with sources (cutting, moves, framing math, acting, light)
- - `references/troubleshooting.md` - every known bug and its fix
README.md · README · 79 lines
- # Roblox story shorts with Claude Code
- A free Claude Code skill for making vertical Roblox story shorts in the style of the viral "In this town, ..." videos:
- a narrator tells a strange little story, and real Roblox characters act it out in real Roblox places.
- Claude drives Roblox Studio itself. It builds the places, dresses the characters, plans every camera move to the spoken words, renders the
- video frame by frame and adds voice and captions. No AI video generator is involved: everything you see is real Roblox, made by code you own.
- The skill is a foundation, not a template. Your story, your characters and your style stay your own.
- ## What you get instead of starting from zero
- - **The traps, already solved.** About 75 problems that cost hours to find: flickering bodies, blurry characters, the camera inside a tree,
- captions out of sync, hidden scripts in free models, faces that render blocky, hair that silently disappears. Each with the fix.
- - **Measured numbers instead of guesses.** What viral shorts of this kind had in common and what weak ones got wrong, measured frame by frame:
- the first 1.5 seconds, how many places, how the camera moves, how long a shot lasts, how loud, how fast the narrator talks.
- - **A workflow that does not waste your time.** Story, voice, first place, your yes, then the rest. Built-in checks find problems before a
- 30-minute render does, and token rules keep chats fast.
- - **A style menu instead of one look.** Options for tone, world, faces, camera, captions, voice, graphics and sound. Pick what you like;
- everything you do not choose stays on tested defaults.
- What it does **not** give you: ready-made code, characters or maps. It is knowledge: Claude writes your toolkit with you in the first
- session (see below), guided step by step, with code for the spots where things silently go wrong.
- ## What you need
- - [Claude Code](https://claude.com/claude-code)
- - Roblox Studio with its built-in MCP server connected to Claude Code
- (Studio's Assistant settings, "MCP Servers"; see [Roblox's guide](https://create.roblox.com/docs/studio/mcp))
- - Python 3.10+ and ffmpeg
- - Tested on Windows.
- ## Install
- Copy this folder to `~/.claude/skills/roblox-in-this-town/` (or into your project's `.claude/skills/`). Then tell Claude:
- *"Help me make Roblox story shorts"*, or paste your story: *"Make an In This Town short: In this town, ..."*.
- ## What happens
- **The first time (once):** Claude checks your setup and builds your own small toolkit in your project folder: the Studio connection,
- place builders, characters, a face set, the camera, the render loop, voice, assembly and a quality report. You choose your style from the
- menu and your channel's hero from a few options. This first session is long (expect several hours), but you only do it once.
- **Every video:**
- 1. You bring the story. Claude shapes it into a script with the structure of the hits and changes nothing without your yes.
- 2. Voice: a free local text-to-speech voice, or your own recording. The spoken words become the clock of the whole video.
- 3. Claude plans and renders the **first place only** (5-15 s) and shows it to you.
- 4. After your yes, it does the rest, checks the finished video against measured numbers and shows it to you.
- In the author's runs, once the toolkit existed, a 74 s video with 4 places took 30 minutes to the first approval and 76 minutes in total
- (32 of them rendering). Use one fresh chat per video; long chats get slow and expensive.
- ## Good to know
- - While frames render (15-35 minutes per video), Roblox Studio has to stay visible on screen; a covered window gives empty frames.
- - The first session uses a lot of Claude usage; plan it for a day with room in your plan's limits.
- - The free local voice and the word timing download their models on first use (a few hundred MB).
- - In your place file, set `StarterPlayer > AvatarJointUpgrade` to Disabled once by hand (in the Properties window); code poses need it.
- ## What's inside
- | File | What it is |
- |---|---|
- | `SKILL.md` | Principles, what is fixed and what is free, the workflow step by step, the time and token budget |
- | `references/styles.md` | The style menu: options per area, marked tested / seen in hits / possible |
- | `references/viral_patterns.md` | What viral shorts do and weak ones do not (story, hook, places, camera, look, cast, faces, captions, sound) |
- | `references/story.md` | Story structure, writing rules, the hook check |
- | `references/directing.md` | Staging: how to show each sentence so it is funny, exciting, mysterious, eerie or warm, without changing the story |
- | `references/camera_and_shots.md` | Shot size per sentence, when to move and when to cut, distances, 9:16 framing, staging for the camera |
- | `references/world_and_light.md` | Building places from Creator Store kits safely, filling them with life, light per mood, colour |
- | `references/characters_and_faces.md` | Dressing characters by code, the hero and side characters, drawing your own face set, using faces well |
- | `references/animation_and_effects.md` | Animation, acting, props, flicker-free effects, comic stickers |
- | `references/pipeline.md` | How the toolkit fits together, with code for the spots where things silently go wrong |
- | `references/troubleshooting.md` | Every bug hit so far: what you see, why, what to do |
- | `references/craft.md` | Film craft research with sources (cutting, moves, framing math, acting, light) |
- ## Fair play
- - Use your own stories and characters. Never copy another channel's characters, videos or look one to one.
- - Creator Store models often contain scripts: the skill strips them before use.
- - Nothing is uploaded to Roblox without your consent; never upload images you do not own.
- - Add only music and sounds you have the rights to.
- ## License
- MIT (see `LICENSE`). Roblox and Roblox Studio are trademarks of Roblox Corporation; this project is not affiliated with Roblox.
- Roblox allows creators to make and monetize videos of Roblox content (check its current terms).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.