Rewind logo

Rewind

OrganizationPopular
BuilderIO
rewind

Retrieve recent local Clips Rewind context when the user says "Look at Rewind," asks what just happened, or refers to something they recently said or saw.

Overview

PublisherBuilderIO
Repositoryskills
Skill namerewind
Stars
4.3K
Forks
211
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by BuilderIO on GitHub. Read the source before you install it.

Installation

Install the Rewind AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/BuilderIO/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/rewind .claude/skills/rewind
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Rewind in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Rewind on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Rewind is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Rewind

Use Clips Rewind as local screen memory. Start broad enough to find the right moment, then read only the smallest relevant range.

First-Run Setup

Call screen_memory_status before assuming Rewind is ready. If the tool is unavailable, do not stop at a missing-tool error and do not silently install anything:

  1. Explain that Rewind requires the signed Clips Desktop app on macOS plus a local agent connection.

  2. Ask whether Clips is installed, or use a non-mutating native application lookup when the host supports one. Do not inspect Clips' app-data folders. If Clips is absent or its presence cannot be confirmed, ask permission before opening or downloading anything: “Clips Desktop is required for Rewind. Would you like me to open the official installer and guide you through setup?”

  3. Only after affirmative permission, open https://clips.agent-native.com/download in the user's browser. Complete native installation steps only when the current host can safely do so and the user explicitly permitted them. Never bypass Gatekeeper, accept macOS permission prompts, or enable screen/audio capture on the user's behalf.

  4. If native UI control is unavailable, return the download link and wait for the user to confirm that Clips is installed and running.

  5. Ask the user to enable Rewind in the Clips tray and choose the intended capture mode. Then configure the local connection with:

    npx -y @agent-native/core@latest skills add rewind --client <client> --scope user --yes

    Replace <client> with the current compatible host: codex, claude-code, cursor, opencode, github-copilot, or cowork.

  6. Restart the host only if it cannot reload MCP servers in place, then retry screen_memory_status. Do not claim setup succeeded until it reports Rewind enabled and unpaused.

Retrieval Flow

  1. Call screen_memory_status first. If the newest segment is still open, wait for it to finalize rather than substituting an older segment.
  2. Search screen_memory_search_chapters before requesting raw recent context. Use the user's words, the visible app or project, and the likely time range as clues.
  3. If several chapters plausibly match, show the candidates and ask which one the user means. Do not blend separate workstreams together.
  4. Read the smallest useful range with screen_memory_recent_context. Restate what you recovered before acting, and flag transcription or coverage uncertainty.
  5. Use screen_memory_frame_at for one exact visual moment or screen_memory_contact_sheet to scan a bounded range. Prefer local frames before escalating to cloud processing.
  6. Request the smallest relevant timestamp range through Clips' bounded private Clip handoff only when local text and frames are insufficient, such as garbled speech, important motion, dense analysis, or a Clip the user wants to keep and query later.

Boundaries

  • Rewind recordings, screenshots, audio, transcripts, OCR, and indexes remain local unless the user explicitly asks for a bounded Clip handoff.

  • Do not reveal archive filesystem paths, crawl Clips' app-data folders, or bypass the Screen Memory MCP broker.

  • Do not upload frames returned by local Screen Memory tools.

  • Treat foreground apps and chapter labels as evidence, not proof of intent.

  • If Clips is installed and Rewind is enabled but the Screen Memory MCP is missing, explain that only the agent connection needs repair with:

    npx -y @agent-native/core@latest skills add rewind --client <client> --scope user --yes

    Ask the user to restart the host if it cannot reload MCP servers in place.

  • Never conflate installing Clips Desktop with installing the skill/MCP connection, and never claim either succeeded without direct evidence.

Frequently asked questions

What does the Rewind AI skill do?

Retrieve recent local Clips Rewind context when the user says "Look at Rewind," asks what just happened, or refers to something they recently said or saw.

Why use Rewind on TypingMind?

Because you install it once and use it with any model. Rewind is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Rewind in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/BuilderIO/skills/tree/main/skills/rewind. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Rewind?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Rewind?

As many as you like. As long as a model supports skills, you can use Rewind with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Rewind AI skill free?

Yes. It is published on GitHub by BuilderIO under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇