Checklist the per-video bar — engine/sim
76.1/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-the-stack-W29-Tue good|bad)⚠ 8 flag(s) — not yet ship-ready: copy_genericlow_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 6 scenes · 32.7s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  first render · fix pending shared field signature-3ddead_air | hook | 0–5.0s | kinetic-build | icon·liquid-chrome | ♪ node_lock | The tool is Calendly, fine for booking. Its limit is simple: it sets the time, but it never reads who is on the other end. on-screen: Calendly can't read your inbox |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape knotground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→Calendly can't read your inbox | |||||||
| 2 |  first render · fix pending NumberedList templatedead_air | teach | 5.0–10.0s | kinetic-build | icon·white-knockout | ♪ node_lock | So we hang a webhook off the booking. The moment someone picks a slot, it fires their name and email to a small script we wrote. on-screen: Webhook to an LLM brief |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape knotground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Webhook to an LLM briefcurate items, nodes | |||||||
| 3 |  matches intent LogStream template | build | 10.0–16.6s | type-on | icon·liquid-chrome | ♪ node_lock | Now every call starts with you already knowing their stack, their news, their likely ask. You sound psychic. on-screen: Walk in already prepared |
expected on screen: red ground · a LogStream panel over a dimmed Signal Field · Magister leads · code · type-on · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id LogStreamvisual codeshape knotground redtreatment liquid-chromemotion type-onpower summoninstrument draw-on→Walk in already preparedcurate codeLines, rows | |||||||
| 4 |  matches intent KpiGrid template | proof | 16.6–22.700000000000003s | receipts-count | icon·white-knockout | ♪ node_lock | So add one webhook to your scheduler and pipe it to a research prompt. Your next meeting writes its own brief. on-screen: Add a booking webhook |
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape knotground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Add a booking webhookcurate kpis, statsLabels | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | futurist | 22.7–27.7s | spatial-parallax | icon·liquid-chrome | ♪ bed | The Stack |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldshape knotground redtreatment liquid-chromemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→The Stack | |||||||
| 6 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 27.7–32.7s | coalescence | icon·white-knockout | ♪ bed_out | The Stack |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→The Stack | |||||||
Format stack 3 aspects · same scenes[], re-cropped
9:16
1080×1920
Stories · TikTok · YouTube Shorts · Reels
1:1
1080×1080
LinkedIn · Facebook · Instagram
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video
Channels 9 destinations
LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky
Social captions supplemental published copy · per channel (comp_id level)
tiktokThe stack: Calendly is fine for booking, but it never reads who's on the other end. So hang a webhook off the booking, pipe it to a research prompt, and walk in already knowing their stack and their likely ask. Your next meeting writes its own brief. (AI-assisted)
instagramThe stack: Calendly.
Fine for booking. Can't read your inbox.
The move:
webhook off the booking
pipe it to a research prompt
walk in already prepared
Your next meeting writes its own brief.
#calendly #automation #webhooks #aitools #thestack
linkedinThe stack this week: Calendly, which is fine for booking and nothing more. Its limit is simple: it sets the time, but it never reads who is on the other end.
The method: hang a webhook off the booking. The moment someone picks a slot, it fires their name and email to a small script that researches them. Now every call starts with you already knowing their stack, their news, and their likely ask.
Add one webhook to your scheduler and pipe it to a research prompt. Your next meeting writes its own brief.
xThe stack: Calendly is fine for booking, but never reads who's on the other end. Fix: hang a webhook off the booking, pipe it to a research prompt. Walk in already knowing their stack and their ask. Your meeting writes its own brief.
facebookThis week's stack: Calendly. It's fine for booking, but it never reads who's on the other end. So we hang a webhook off the booking, pipe it to a research prompt, and walk into every call already knowing their stack, their news, and their likely ask. Add one webhook to your scheduler and your next meeting writes its own brief.
threadsThe stack: Calendly.
Fine for booking. Its limit: it sets the time but never reads who's on the other end.
So hang a webhook off the booking, pipe it to a research prompt, and walk in already knowing their stack and their ask. Your next meeting writes its own brief.
pinterestThe stack: how to make Calendly do more than book a time. Its limit is that it never reads who's on the other end. The method: hang a webhook off the booking and pipe it to a research prompt, so you walk into every call already knowing their stack, their news, and their likely ask. Your next meeting writes its own brief.
blueskyThe stack: Calendly is fine for booking, but never reads who's on the other end. Fix: hang a webhook off the booking, pipe it to a research prompt. Walk in already knowing their stack. Your meeting writes its own brief.
youtubeTitle: Make Calendly Smarter: Auto-Brief Every Meeting With a Webhook
Calendly is fine for booking, but its limit is simple: it sets the time and never reads who is on the other end. We give away the method: hang a webhook off the booking, pipe it to a research prompt, and walk into every call already knowing their stack, their news, and their likely ask. Add one webhook to your scheduler and your next meeting writes its own brief.