PERSONAL PRODUCTIVITY

AI Refresh Brief for Stale Loom Walkthroughs

For each stale, low-view Loom walkthrough, transcribes the recording, uses an LLM to judge whether its content is likely outdated.

CategoryPersonal Productivity
EngineSim + Paperclip
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled sweep begins
  • ActionList stale low-view videos and fetch transcriptsLoomLoom
  • ActionLLM rates staleness and extracts outdated claimsOpenAI
  • LogicDrop low-risk, keep flagged-outdated videos
  • OutputOpen Linear refresh issue with checklistLinearLinear

What it does

It does the judgment work on aging Loom walkthroughs: pulling the transcript, reasoning about whether the content has likely drifted out of date, and opening a scoped refresh task only for the ones that actually need re-recording.

When to use it

Use it when your stale backlog is large and you do not want to manually rewatch every clip to decide what to redo. Best for product, support, or enablement teams whose walkthroughs reference fast-changing UI, pricing, or process that silently goes stale.

How it works

  1. 1A schedule kicks off the periodic sweep.
  2. 2It lists Loom videos older than the threshold with low view counts and fetches each one's transcript.
  3. 3An LLM step reads the transcript and rates likely staleness, returning a verdict plus the specific outdated claims it spotted.
  4. 4A logic branch drops low-risk videos and keeps the ones flagged as outdated.
  5. 5For each flagged video it creates a Linear issue containing the suspect claims and a re-record checklist, linking back to the original recording.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LoomVideo transcripts, libraries.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.