Erduo Broll Loop Engineering logo

Erduo Broll Loop Engineering

Community
erduo1998-cell
erduo-broll-loop-engineering

Turn original SRT and design into editable B-roll through an independent Director, focused chapter creators, and visual review. Use for SRT-to-video production or revisions; preserve existing legacy projects and explicit Remotion choices.

Overview

Publishererduo1998-cell
Repositoryerduo-broll-loop-engineering
Skill nameerduo-broll-loop-engineering
Stars
228
Forks
44
Bundled files
487
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 487 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by erduo1998-cell on GitHub. Read the source before you install it.

Installation

Install the Erduo Broll Loop Engineering AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/erduo1998-cell/erduo-broll-loop-engineering/tree/main/erduo-broll-loop-engineering
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/erduo1998-cell/erduo-broll-loop-engineering.git /tmp/erduo-broll-loop-engineering
mkdir -p .claude/skills
cp -r /tmp/erduo-broll-loop-engineering/erduo-broll-loop-engineering .claude/skills/erduo-broll-loop-engineering
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Erduo Broll Loop Engineering in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Erduo Broll Loop Engineering on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Erduo Broll Loop Engineering is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Erduo B-roll Loop Engineering

Make the spoken meaning visible, with considered composition and purposeful motion. Picture quality comes first. Preserve fresh creative contexts and independent visual review; save work through focused handoffs and deterministic scripts, never by removing needed creative work or returning an inferior film.

Route once

  • New projects and existing broll-plan.json use the creative relay below.
  • Existing Recipe/runtime-plan v1–v4, explicit Remotion/hybrid, or an explicit five-shot version comparison use legacy production. Preserve original inputs and approvals; do not silently migrate projects.
  • This relay uses pinned HyperFrames. Its role references replace the legacy stage Skills for this route; do not load both sets or the whole Skill catalog.

Parent: prepare and dispatch

Keep the complete original SRT and original design in the project. If design is missing, make a short brief from the user's request; preserve the original SRT. Prepare known local assets/fonts and assets/index.md with paths and sources. Add a material researcher only for real selection work; authorized search or generation remains available when needed for the picture.

Read production commands. Resolve the installed Skill root and runnable commands once. Use scripts/prepare-creative-task.mjs to prepare each role's short TASK.md, then start it in a new context using the host's delegation capability. Give the task file and any explicit user constraints, not the parent conversation, previous agent logs, or all Skills. Respect the user's model selection; do not silently substitute a cheaper model. The helper prepares inputs; the host must actually start fresh contexts and may still inject global instructions. Do not claim it enforces a context sandbox.

Creative relay

  1. Independent Director reads originals and chooses the visual world, meaningful shot boundaries, material, action development and seams. It writes one broll-plan.json, a short direction.md, and direction/<id>.md shot cards. Its role is creative direction.
  2. Fresh creators each own a continuous passage and its editable HTML. Group shots by narrative continuity and complexity, not a fixed count. Give originals, shared direction/assets, owned shot cards and adjacent seam cards. Separate file ownership; run independent chapters in parallel where their visual contract is clear. Use chapter creation.
  3. Parent runs the scripts for plan checks, renders, decode, sheets and assembly. Return a concise failed-shot error to its owner. Environment failures belong to the parent; do not make every creator reinstall or search for the same executable. Creators can request a render and view their work.
  4. Independent visual reviewer sees the originals, direction, actual media and relevant seams, without creator explanations or cost figures. Use visual review. Technical success cannot approve aesthetics. Send specific time/shot feedback to the original creator, render only changed shots, and recheck affected shots and seams.

Keep these creative contexts separate even for a short film; a short film can have one creator. If independent delegation is unavailable, disclose that the relay cannot be completed as specified; do not label a same-context self-review independent. Revisions of existing work retain its direction and shot ownership; reopen directing only when the requested change affects meaning or the visual world.

Quality and delivery

Use visual direction and a few matching motion patterns to make the action concrete. For an uncertain style or complex shared transition, make a representative passage and view it before multiplying that treatment. Reuse accepted visual source or frames as a reference, while varying composition with meaning. There is no mandatory number of samples, material quota, or decorative element count.

Respect requested user review stops; existing authorization also covers normal renders and repairs. Do not stop for a new approval form merely because a role changed. Repair visible quality problems before delivery. If repeated local repairs are not improving the picture, change the visual solution instead of repeating the same layout or adding more decoration.

Deliver ordered shot files, editable source/assets, complete preview, actual output facts and remaining limitations. A partial preview must identify missing shots and cannot stand for the full film. State what was actually viewed; frame sampling is not continuous playback. Report tokens only from actual host usage, separating cached input and output. Do not turn file sizes into savings claims. Follow safe execution for external commands.

Optional author support

When the user asks for author tutorials, human help, membership or custom work, or remains blocked after reasonable self-service troubleshooting, read author support and offer the relevant optional link once for this issue in this conversation. Continue authorized diagnosis; do not recommend on ordinary success, one recoverable error, or after refusal. Only the user-facing Parent offers the link, including across stage handoffs.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

and 140 more files.

Frequently asked questions

What does the Erduo Broll Loop Engineering AI skill do?

Turn original SRT and design into editable B-roll through an independent Director, focused chapter creators, and visual review. Use for SRT-to-video production or revisions; preserve existing legacy projects and explicit Remotion choices.

Why use Erduo Broll Loop Engineering on TypingMind?

Because you install it once and use it with any model. Erduo Broll Loop Engineering is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Erduo Broll Loop Engineering in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/erduo1998-cell/erduo-broll-loop-engineering/tree/main/erduo-broll-loop-engineering. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Erduo Broll Loop Engineering?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Erduo Broll Loop Engineering?

As many as you like. As long as a model supports skills, you can use Erduo Broll Loop Engineering with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Erduo Broll Loop Engineering AI skill free?

Yes. It is published on GitHub by erduo1998-cell under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇