Screen Recording

OrganizationPopular

vellum-ai

screen-recording

Record the user's screen as a video file

Overview

Publisher	vellum-ai
Repository	`vellum-assistant`
Skill name	`screen-recording`
Stars	1.4K
Forks	208
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

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 vellum-ai on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/vellum-ai/vellum-assistant/tree/main/skills/screen-recording
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.

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/vellum-ai/vellum-assistant.git /tmp/vellum-assistant
mkdir -p .claude/skills
cp -r /tmp/vellum-assistant/skills/screen-recording .claude/skills/screen-recording

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Screen Recording 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 Screen Recording 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 Screen Recording 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.

Capture screen recordings as video files attached to the conversation.

Activation

The user asks to start, stop, pause, resume, or restart a screen recording. Routing does not depend on matching phrases: see Routing below.

Routing

Recording is managed through dedicated HTTP endpoints (/v1/recordings/*) rather than text-based intent detection. Two routing mechanisms exist:

1. `commandIntent` (structured command) - highest priority

The macOS client can send structured intents with domain: 'screen_recording' and action: 'start' | 'stop' | 'restart' | 'pause' | 'resume'. These bypass text parsing entirely. The assistant checks for commandIntent before any text analysis.

2. HTTP endpoints

Clients call the recording HTTP endpoints directly:

POST /v1/recordings/start - start a screen recording
POST /v1/recordings/stop - stop the active recording
POST /v1/recordings/pause - pause the active recording
POST /v1/recordings/resume - resume a paused recording
GET /v1/recordings/status - get current recording status
POST /v1/recordings/status - recording lifecycle callback from the client

3. Normal processing

If no recording intent is detected, the message flows to the classifier and computer-use session as usual.

Behavior Rules

Do not invoke computer use for recording-only requests. The assistant handles these directly.
One recording at a time. If a recording is already active, starting another returns an "already recording" message.
Conversation-linked. Each recording is linked to the conversation that started it for attachment purposes. However, since only one recording can be active at a time, stop commands from any conversation will stop the active recording regardless of which conversation started it.
Permission required. Screen recording requires macOS Screen Recording permission. If denied, the user sees actionable guidance to enable it in System Settings.
Mixed-intent prompts (recording + other task) are NOT intercepted by the standalone route - the recording action is deferred and executed alongside the task.
Restart always reopens the source picker and requires source reselection.
Restart cancel (user closes the source picker) leaves state idle - no false "recording started" message.
Pause/resume toggle the recording without stopping it. The HUD shows paused state.

What This Skill Does NOT Do

This skill does not contain recorder logic - the RecordingManager and ScreenRecorder in the macOS app handle the actual recording.
This skill does not provide shell commands or scripts for recording.
This skill does not fall back to computer use for recording tasks.
This skill does not handle informational questions about recording - those flow through to normal AI response.

Frequently asked questions

What does the Screen Recording AI skill do?

Record the user's screen as a video file

Why use Screen Recording on TypingMind?

Because you install it once and use it with any model. Screen Recording 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 Screen Recording in TypingMind?

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

Which AI models can use Screen Recording?

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 Screen Recording?

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

Is the Screen Recording AI skill free?

Yes. It is published on GitHub by vellum-ai 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

Subagent Driven Development

obra

CommunityPopular

Use when executing implementation plans with independent tasks in the current session

Unified Memory

Share durable, inspectable context and handoffs between Claude, Codex, Hermes, Cursor, OpenCode, and other agents through the local ECC Memory Vault. Use when an agent must save work state, transfer…

Draw Your Font

Turn a handwriting photo into an installable TTF font.

Adversarial Ux Test

Roleplay a hostile user to find and triage UX pain points.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Activation

Routing

1. commandIntent (structured command) - highest priority

2. HTTP endpoints

3. Normal processing

Behavior Rules

What This Skill Does NOT Do

Frequently asked questions

Related AI Skills

Set up your own AI workspace now

1. `commandIntent` (structured command) - highest priority