Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Screen Recorder

ASecurity

Capture professional screen recordings with setup, narration, editing, and delivery best practices.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgo

Works with

cursorcli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill screen-recorder --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Screen Recorder?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Screen Recorder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-screen-recorder/badge)](https://www.skillsdirectory.com/skills/aicodedecode-screen-recorder)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: screen-recorder
description: Capture professional screen recordings with setup, narration, editing, and delivery best practices.
category: video
---

## Overview

Screen recordings power tutorials, demos, bug reports, and courses — but most are unwatchable: tiny
text, rambling narration, 20-minute runtimes for 3-minute content. Professional screen capture is a
production discipline: prepare the environment, script the narration, record cleanly, and edit
tightly. This skill covers the full workflow.

## When to use

- Recording software tutorials or course lessons

- Capturing product demos or sales walkthroughs

- Creating bug reproduction videos for developers

- Recording presentations or webinars

- Producing onboarding or training videos

## Core concepts

- - **Prepare the stage.** Close notifications (Do Not Disturb), hide personal bookmarks/tabs, clean
  the desktop, use a fresh browser profile, zoom UI to 125-150% so text reads on video. The viewer
  sees everything — curate it.
- - **Resolution discipline.** Record at 1920×1080 (or the delivery resolution) — not a 4K screen
  downscaled weirdly, not a tiny window. If the UI is dense, zoom the app rather than recording a
  postage stamp.
- - **Script, don't ramble.** Write the narration (or detailed bullet beats) before recording.
  Rambling "ums" and dead air while you think are the #1 tutorial killer. Scripted 5 minutes beats
  improvised 20.
- - **Separate audio from video.** Record narration on a decent mic as its own track (or record
  voiceover after the screen capture). Clean audio over screen content matters more than
  pixel-perfect capture.
- - **Mouse as a presenter.** Move deliberately, pause on clicks, use cursor highlighting/zoom for
  key actions. A frantic cursor is visual noise — slow down, narrate the click before you make it.
- - **Edit tightly.** Cut mistakes, dead air, and loading waits (jump-cut or speed up). Add
  zooms/callouts on critical UI, captions for key terms. A 10-minute raw recording should become 5-6
  minutes.

## Practical workflow

1. 1. **Plan the video.** One topic per video, defined outcome ("by the end, the viewer can X"),
   outline of steps. Decide: voiceover-first (record audio, then capture to match) or capture-first.
2. 2. **Set up the environment.** Do Not Disturb on, clean desktop/browser, test accounts with
   realistic (non-personal) data, app zoomed appropriately, recording area framed.
3. 3. **Test the stack.** 30-second test recording: check resolution, frame rate (30fps fine for UI;
   60 for smooth motion), audio levels, and that system audio (if needed) captures. Watch the test
   fully.
4. 4. **Record in segments.** One section per take — mistakes only cost the segment, not the whole
   video. Clap or pause 3 seconds between segments for easy edit points.
5. 5. **Narrate well.** Speak 10% slower than conversation, smile (it shows in the voice), describe
   what you're doing as you do it, and pause after key points. Record in a quiet room; closets work
   surprisingly well.
6. 6. **Edit the capture.** Assemble segments, cut errors and waits, add zooms on small UI,
   callouts/arrows for emphasis, intro/outro bumpers if it's a series. Normalize audio, remove
   background noise.
7. 7. **Export and package.** Per platform spec (YouTube 1080p, etc.), descriptive title/thumbnail,
   chapters for longer videos, and captions (auto + corrected). Include links/resources mentioned in
   the description.

## Common pitfalls

- - **Recording the messy real desktop.** Personal emails, notification popups, embarrassing tabs.
  The audience notices everything — stage the environment.
- - **Tiny unreadable UI.** Recording a 4K screen at native scaling: text becomes ants on YouTube.
  Zoom the OS/app UI before recording.
- - **Unscripted rambling.** "So, uh, let's just... hmm, where was I..." Script the beats at
  minimum; word-for-word for key explanations.
- - **Noisy audio.** Laptop mic in an echoey room with keyboard clatter. A $50 USB mic in a quiet
  room beats a $500 mic in a noisy one — but any external mic beats built-in.
- - **Real-time waiting.** Watching a progress bar for 90 seconds in real time. Edit it out or
  speed-ramp — respect the viewer's time.
- - **One giant video.** A 45-minute "complete guide" nobody finishes. Split into focused 5-10
  minute chapters — better retention, better searchability, easier updates.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →