We only use cookies to enhance your experience. No cross-site tracking, no ads. Read our Cookie Policy.

Turn your recordings into a knowledge base.

Put what your team records into a shared playlist. Then anyone can ask it a question and get an answer back.

Record in Supercut

Explain the thing on camera, the way you would to a person.

Put it in a playlist

One playlist per topic, shared with your whole team.

The answer comes back

Ask your agent, and it reads the playlist and tells you.

In a nutshell

You can turn your team's screen recordings into a knowledge base by putting them in a shared playlist and connecting Supercut to your agent. Anyone on your team can then ask their agent a question in plain language, tell it to look at the Supercut playlists, and get an answer back with a link to the part of the video that answers it.

Ingredient list.

Supercut

Connected to your agent.

An MCP client

Claude, Cursor, or similar.

01. A playlist is a library

A playlist is how you build a library. Put every recording about the same thing in one place: a playlist for SOPs, one for how-to guides, one for onboarding, one for sales. You decide who can see each playlist, so a library can be open to everyone or to one team.

You record it instead of writing it up

Nobody has to turn the recording into a document afterwards. You explain the thing once, on screen, with everything visual that goes with it, and the recording is the documentation.

The team fills it, not one person

Invite everyone to the playlist and they add their own recordings to it. The library grows from whoever happened to know the answer, which is the opposite of how documentation usually gets written.

02. Anyone on the team asks it a question

No keywords, no filenames. They ask in whichever agent they already use, and point it at a playlist: "check the how-to guides and tell me how this feature works". Nobody has to open Supercut, and nobody has to know which recording holds the answer.

It only sees what they see

Each person's agent inherits their permissions. A playlist someone cannot open is a playlist their agent cannot read.

03. The answer comes back

A few sentences in plain English, plus a link to the part of the recording that answers the question. A support agent asking how a feature works gets the answer straight away, and can open the video at that exact point if they want to see it. If several recordings cover the same question, the agent reads them all and tells you where they disagree.

Use this prompt

Paste this to your agent. Swap [PLAYLIST] for the playlist to search and [QUESTION] for what you actually want to know.

Search the Supercut playlist [PLAYLIST] and answer this question: [QUESTION]

- Give me the answer in plain language.
- Give me the timestamped link to the moment in the video that answers it, so I can check it myself.
- If several recordings answer this and contradict each other, say so and give me both with dates, so I can pick the winner.
- If you cannot find an answer, say so plainly.
- Only answer from what is in the recordings. Do not fill the gaps.
- Quote people accurately.

If you have a pile of recordings and no playlists yet, run this one first to give the library a shape. Swap [TOPICS] for the ones your team records.

Sort my Supercut recordings into playlists by topic: [TOPICS]. Read the transcript before you decide which one a recording belongs in, not just the title. Create the playlists if they do not exist, and list anything that does not fit rather than forcing it.

Your agent can only find what somebody recorded. It answers from the transcripts, so a decision made in a meeting nobody recorded is not in there.

Your team already knows this. It is just trapped in video.

Documentation gets written by the few people who will write documentation. Everyone else explains things out loud, on a call or in a walkthrough. That knowledge is real, and it gets recorded, and then it sits there, because video is the one format nobody can search.

Record the answer the first time you give it

The habit that makes this work is a small one: when somebody asks you something, answer it on camera instead of in a message. Screen, camera, a meeting. Then drop it in the playlist and it is there for the next person who asks.

A knowledge base nobody has to maintain

The usual problem with internal documentation is not writing it, it is keeping it true. This library updates itself, because it is made of the recordings people were going to make anyway.

Move work forward with Supercut.