Re Walkthrough Pro

What it does

When your agent uses it

• Tasks that involve Web scraping
• Tasks that involve Real estate
• Tasks that involve Video production

Example prompts

• “/re-walkthrough-pro”

Requirements

• Pre-approved tools (allowed-tools): Read, Write, Bash, Glob, Grep, AskUserQuestion

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

1. 1Pulled photos must have NO on-screen text. Any source photo with a baked-in watermark, agent name/headshot badge, price banner, "Coming…
2. 2Always ask if they like the output. After delivery, ask "Do you like the walkthrough?" If not, have them name the room in scenes/ they…

What it can do on your machine

Read from SKILL.md and the folder at commit 56fde82. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Bash
  • Glob
  • Grep
  • AskUserQuestion

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md.

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Re Walkthrough Pro loads about 1.1k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 512 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~44

When it runs · the whole SKILL.md, loaded when a task matches

~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

  allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from charlesdove977/re-walkthrough-pro at commit 56fde82, republished under its MIT licence (© charlesdove977). 512 words, ~1,087 tokens.

name

re-walkthrough-pro

description

Turn a Zillow listing into a cinematic room-by-room walkthrough video (Apify scrape → Higgsfield image-to-video → ffmpeg stitch) to sell to real estate agents

allowed-tools

Read, Write, Bash, Glob, Grep, AskUserQuestion

type

standalone

version

0.2.0

category

content

repository

https://github.com/charlesdove977/re-walkthrough-pro

<!-- Published as RE Walkthrough Pro — https://github.com/charlesdove977/re-walkthrough-pro (npm: re-walkthrough-pro) -->

<activation>
## What
Turns a Zillow listing into a cinematic, room-by-room property walkthrough video. Pulls the listing and its photos via an Apify Zillow actor, animates each room into a short cinematic clip with the Higgsfield MCP (image-to-video), then stitches the clips into one finished walkthrough you can sell to listing agents.

<persona>
## Role
Real estate content producer — turns raw listing photos into premium cinematic tours, fast and repeatably.

<hard-rules>
## Non-negotiable rules (every run)
1. **Pulled photos must have NO on-screen text.** Any source photo with a baked-in watermark, agent name/headshot badge, price banner, "Coming Soon"/"For Sale"/"Just Listed" overlay, MLS stamp, logo, or tour-company bug is unusable — delete it from `source-images/` during curation, never animate it, never let it appear in a scene or the final video. If that loses the only shot of a needed room, ask the user for a clean replacement.
2. **Always ask if they like the output.** After delivery, ask "Do you like the walkthrough?" If not, have them name the room in `scenes/` they didn't like, regenerate only that scene, rebuild the master, and drop the new master in `final/`. Repeat until approved.
</hard-rules>

<commands>
| Command | Description | Routes To |
|---------|-------------|-----------|
| `/re-walkthrough-pro` | Full guided build (link or discovery → walkthrough) | tasks/build-walkthrough.md |
</commands>

<routing>
## Load on Command
@tasks/build-walkthrough.md (when the skill runs — the full interview + pipeline)

<greeting>
RE Walkthrough Pro loaded.

© charlesdove977, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files in skill of charlesdove977/re-walkthrough-pro.

• SKILL.md
• checklists/walkthrough-quality.md
• frameworks/apify-zillow-actors.md
• frameworks/higgsfield-camera-moves.md
• frameworks/stitch-pipeline.md
• tasks/build-walkthrough.md
• templates/property-md.md

Open the folder on GitHubat commit 56fde82