Automated Workflows — topic-it-automations — Temerarii Media Back Office

post topic-it-automationskind topicweek —date —campaign it-dev-pillarpillar it_devbeat —asset videoduration 113.4sground blackscenes 19

Checklist the per-video bar — engine/sim

99.1/100

plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness

quantitative quality · weights learn from your reviews (engine.sim.memory review topic-it-automations good|bad)

⚠ 1 flag(s) — not yet ship-ready: too_complex · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SceneReel

9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending

▶ open rendered mp4

expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 19 scenes · 113.4s · comp_id + rendered still + tier + the script

#	Layer (comp_id · still · tier)	Beat	Timecode	Motion	Logo	Audio	VO / on-screen / caption
1	still pending matches intent shared field signature-3d	open	0–5.2s	spatial-parallax	icon·white-knockout	♪ —	There is a task you do every single day by hand. Let us automate the boring half of it. on-screen: The task you do every day
	expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→three-mark
2	still pending matches intent LogStream template	legacy	5.2–11.9s	crossfade-8f	icon·ember-fill	♪ —	The old way was copy, paste, switch tabs, repeat, an invisible tax you pay in hours every week. on-screen: The copy-paste tax
	expected on screen: black ground · a LogStream panel over a dimmed Signal Field · Faber leads · crossfade-8f · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id LogStreamshape boxground blacktreatment ember-fillmotion crossfade-8fpower morphinstrument decay→three-symboliccurate rows
3	still pending matches intent NumberedList template	teach	11.9–16.9s	kinetic-build	icon·wireframe	♪ —	First we write down the workflow as numbered steps, exactly the way you do it now. on-screen: Step 1: map the steps
	expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
4	still pending matches intent ChecklistCard template	teach	16.9–23.099999999999998s	kinetic-build	icon·white-knockout	♪ —	Every automation needs a trigger, a new row, an email, a form, the moment work should start. on-screen: Step 2: find the trigger
	expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate items, nodes
5	still pending matches intent JsonDiff template	teach	23.1–29.900000000000002s	kinetic-build	icon·liquid-chrome	♪ —	Instead of a node graph, we let Claude Code call the tools directly: Airtable, Gmail, your sheet. on-screen: Step 3: tools, not nodes
	expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id JsonDiffvisual node-graphshape boxground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate fileName, lines, nodes
6	still pending matches intent NodeGraphCard template	teach	29.9–36.5s	kinetic-build	icon·ember-fill	♪ —	Each app speaks through an MCP server, one common plug, so the agent talks to all of them the same way. on-screen: Step 4: MCP is the adapter
	expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id NodeGraphCardvisual node-graphshape boxground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate hub, nodes
7	still pending matches intent FlowSchematic template	teach	36.5–42.8s	kinetic-build	icon·wireframe	♪ —	The flow reads the source first, decides, then writes, so it never acts on data it has not actually on-screen: Step 5: read before write
	expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id FlowSchematicvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes, stages
8	still pending matches intent WireframeMock template	teach	42.8–48.9s	kinetic-build	icon·white-knockout	♪ —	The if-this-then-that lives in plain language now: when the deal is over a threshold, route it differently. on-screen: Step 6: branch on the data
	expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id WireframeMockvisual node-graphshape boxground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes
9	still pending matches intent ProcessFlow template	teach	48.9–55.199999999999996s	kinetic-build	icon·liquid-chrome	♪ —	Independent steps run at the same time, so a five-tool flow finishes in one pass, not five. on-screen: Step 7: parallel where safe
	expected on screen: black ground · a ProcessFlow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id ProcessFlowvisual node-graphshape boxground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, steps
10	still pending matches intent SchematicCard template	teach	55.2–61.1s	kinetic-build	icon·ember-fill	♪ —	Every run writes a line to a log, so when it misbehaves you can read exactly what it did. on-screen: Step 8: log every run
	expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id SchematicCardvisual node-graphshape boxground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes
11	still pending matches intent CheatSheet template	teach	61.1–67.1s	kinetic-build	icon·wireframe	♪ —	Before it touches live data we run it in dry mode, where it tells you what it would do but does nothing. on-screen: Step 9: dry run first
	expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id CheatSheetvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes, points, uses
12	still pending matches intent PipelineMap template	teach	67.1–73.5s	kinetic-build	icon·white-knockout	♪ —	We decide up front what happens when a tool times out, so a hiccup pauses the flow instead of corrupting it. on-screen: Step 10: handle the failure
	expected on screen: black ground · a PipelineMap panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id PipelineMapvisual node-graphshape boxground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes, stages
13	still pending matches intent BlueprintGrid template	teach	73.5–78.7s	kinetic-build	icon·liquid-chrome	♪ —	Once it is trustworthy we schedule it, so the workflow wakes itself up at the right time. on-screen: Step 11: put it on a cron
	expected on screen: black ground · a BlueprintGrid panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id BlueprintGridvisual node-graphshape boxground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, rows
14	still pending matches intent BuildLog template	teach	78.7–84.60000000000001s	kinetic-build	icon·ember-fill	♪ —	At the end it pings a person only when a human decision is actually needed, never just to say on-screen: Step 12: notify a human
	expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual node-graphshape boxground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate lines, nodes
15	still pending matches intent DiffCard template	teach	84.6–90.8s	kinetic-build	icon·wireframe	♪ —	The whole workflow lives in a file in version control, so changing it is a reviewed edit, not a on-screen: Step 13: version the flow
	expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id DiffCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate lines, nodes
16	still pending matches intent CodeWindow template	teach	90.8–96.7s	kinetic-build	icon·white-knockout	♪ —	Finally we time the manual version against the automated one, so the win is a number, not a vibe. on-screen: Step 14: measure the hours
	expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual node-graphshape boxground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate codeLines, nodes, windowTitle
17	still pending matches intent KpiGrid template	proof	96.7–102.4s	receipts-count	icon·liquid-chrome	♪ —	That is a daily chore turned into a flow that triggers, decides, acts, and logs without you. on-screen: Manual hours, gone
	expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape boxground blacktreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate kpis, statsLabels
18	still pending matches intent shared field signature-3d	futurist	102.4–107.4s	spatial-parallax	icon·ember-fill	♪ —	Stack enough of these and your team stops running the business by hand and starts steering it. on-screen: What this unlocks
	expected on screen: black ground · box hero in the shared Signal Field · Faber leads · spatial-parallax · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldshape boxground blacktreatment ember-fillmotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
19	still pending matches intent shared field signature-3d	resolve	107.4–113.4s	coalescence	icon·white-knockout	♪ swell	Tell us the task you dread doing daily. We will map it and automate it. temerarii.xyz. on-screen: Name your daily chore
	expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→three-coalescence

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 12 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBlueskyEmailSMSBlog

Social captions supplemental published copy · per channel (comp_id level)

tiktokThere's a task you do by hand every single day. Let's automate the boring half. (AI-assisted.) The build: write the workflow as numbered steps. Find the trigger, a new row, an email, a form. Let Claude Code call the tools directly through MCP, one common plug for every app. Read before write. Branch in plain language. Run independent steps in parallel. Log every run. Dry run first. Then put it on a cron. Tell us the task you dread doing daily. temerarii.xyz.

instagramThere is a task you do by hand every single day. Let us automate the boring half. The build: Map the steps. Find the trigger. Let Claude Code call tools via MCP. Read before you write. Log every run, dry run first. Then put it on a cron. Name your daily chore at temerarii.xyz #Automation #MCP #ClaudeCode #BuildInPublic #Temerarii

linkedinThere is a task you do by hand every single day. The old way was copy, paste, switch tabs, repeat, an invisible tax you pay in hours every week. Here is how we automate the boring half. The method: 1. Write the workflow as numbered steps, exactly how you do it now. 2. Find the trigger: a new row, an email, a form, the moment work should start. 3. Let Claude Code call the tools directly, Airtable, Gmail, your sheet, instead of a node graph. 4. Each app speaks through an MCP server, one common plug, so the agent talks to all of them the same way. 5. Read the source first, decide, then write, so it never acts on data it has not seen. 6. Branch in plain language, run independent steps in parallel, and log every run. 7. Dry run before it touches live data, then put it on a cron and notify a human only when a real decision is needed. The result is a daily chore turned into a flow that triggers, decides, acts, and logs without you. Tell us the task you dread doing daily. We will map it and automate it. temerarii.xyz

xThere's a task you do by hand every day. Automate the boring half: map the steps, find the trigger, let Claude Code call tools via MCP, read before write, log every run, dry run first, then cron it. Name your daily chore: temerarii.xyz

facebookThere is a task you do by hand every single day. Let us automate the boring half of it. The old way was copy, paste, switch tabs, repeat, an invisible tax you pay in hours every week. The build: write the workflow as numbered steps. Find the trigger, a new row, an email, a form. Let Claude Code call the tools directly through MCP, one common plug for every app like Airtable or Gmail. Read before you write. Branch in plain language. Run independent steps in parallel. Log every run, dry run first, then put it on a cron. Tell us the task you dread doing daily. We will map it and automate it. temerarii.xyz.

threadsThere's a task you do by hand every single day. Automate the boring half: map the steps, find the trigger, let Claude Code call tools directly via MCP, read before write, branch in plain language, log every run, dry run first, then cron it. Name your daily chore at temerarii.xyz

pinterestHow to automate a daily workflow with Claude Code and MCP: map the steps, find the trigger, let the agent call tools directly, read before you write, branch on the data in plain language, run independent steps in parallel, log every run, dry run first, then schedule it on a cron. A plain-language guide to replacing copy-paste busywork with a real automation. temerarii.xyz

blueskyThere's a task you do by hand every single day. Automate the boring half: map the steps, find the trigger, let Claude Code call tools via MCP, read before write, log every run, dry run first, then cron it. Name your daily chore at temerarii.xyz

youtubeAutomate Your Daily Workflow with Claude Code and MCP There is a task you do by hand every single day. The old way was copy, paste, switch tabs, repeat, an invisible tax you pay in hours every week. This video walks the full build of automating it. The method: - Write the workflow as numbered steps, exactly how you do it now. - Find the trigger: a new row, an email, a form, the moment work should start. - Let Claude Code call the tools directly, Airtable, Gmail, your sheet, instead of a node graph. - Each app speaks through an MCP server, one common plug, so the agent talks to them all the same way. - Read the source first, decide, then write, so it never acts on data it has not seen. - Branch in plain language, run independent steps in parallel, and log every run. - Dry run before it touches live data, handle the failure case, then put it on a cron and notify a human only when a real decision is needed. The result is a daily chore turned into a flow that triggers, decides, acts, and logs without you. Tell us the task you dread doing daily. We will map it and automate it. temerarii.xyz

Cross-links every lens is a view on this one record

→ Wireframe · scenes → Calendar week → Media (audience preview)→ Storyboard hub → Day view → Channel view