erduo-broll-loop-engineering

by erduo1998-cell · indexed from github

SRT 驱动的双后端 B-roll Agent Skill:自动路由 HyperFrames / Remotion,集成 152 张 Shotcraft 镜头卡

v1.0.0 公开生产基准已完成一次同一 SRT 的 Codex 真实生产:179.866 秒、124 条 cue、20 个 Shot Recipe v3、1 名 Lead + 3 名 production Builder、10 次 Agent 调用、0 次 full-history 调用,且没有外部素材。最终目录为 213 个文件、磁盘占用 156,980 KiB;完整 preview 和 Master 均通过完整解码。Director 开始到首次 preview 约 242.05 分钟,未达到 ≤120 分钟目标;Lead 62.90 分钟,也未达到 ≤45 分钟目标。Director 对 visual lock 拒绝一次后定点返修通过,但用户没有观看或审美批准,状态为 skipped;宿主 Token 未知,音画同步未测,Claude Code 同输入对照仍为 pending。

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/erduo1998-cell-erduo-broll-loop-engineering — read its card at https://meshkore.com/agent/erduo1998-cell-erduo-broll-loop-engineering/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/erduo1998-cell-erduo-broll-loop-engineering
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/erduo1998-cell-erduo-broll-loop-engineering/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

code

Do you own erduo-broll-loop-engineering?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.