Post-process raw screen recordings to improve pacing — remove silent segments, then speed up the result.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionraw-video-processingExecute the skills CLI command in your project's root directory to begin installation:
Fetches raw-video-processing from zc277584121/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate raw-video-processing. Access via /raw-video-processing in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
0
upvotes
Run in your terminal
0
installs
0
this week
—
stars
Post-process raw screen recordings to improve pacing — remove silent segments, then speed up the result.
Prerequisite: FFmpeg and uv must be installed.
The user has recorded a screencast and wants to clean it up before publishing. Typical issues in raw recordings:
When the user provides a raw video file, run both scripts in sequence by default:
uv run --python 3.12 /path/to/skills/raw-video-processing/scripts/remove_silence.py <input.mp4> -t="-20dB" -d 0.5
This detects and cuts out silent portions (including keyboard sounds), producing <input>_nosilence.mp4.
Always pass these parameters (tuned for screen recordings with keyboard noise):
-t="-20dB" — aggressive threshold that filters out keyboard typing and background noise (use = syntax to avoid argparse treating negative values as flags)-d 0.5 — remove short silences too (0.5s minimum)-p 0.2 — seconds of breathing room kept around speech boundaries (default, usually no need to pass)The script prints a detailed summary: number of silent segments found, total silence removed, and all kept segments with timestamps. Review this output to confirm the result looks reasonable.
uv run --python 3.12 /path/to/skills/raw-video-processing/scripts/speed_video.py <input>_nosilence.mp4
This applies a speed multiplier to the silence-removed video, producing <input>_nosilence_1.2x.mp4.
Default parameters:
--speed 1.2 — 1.2x playback speed (a subtle boost that doesn't feel rushed)| Flag | Default | Description |
|---|---|---|
-o, --output |
<input>_nosilence.mp4 |
Custom output path |
-t, --threshold |
-30dB |
Silence threshold in dB (higher = more aggressive). Always use -20dB for screencasts — pass as -t="-20dB" to avoid argparse issues with negative values |
-d, --duration |
0.8 |
Minimum silence duration in seconds to remove. Use 0.5 for screencasts |
-p, --padding |
0.2 |
Padding kept around non-silent segments |
--dry-run |
off | Only print detected segments, don't export |
| Flag | Default | Description |
|---|---|---|
-o, --output |
<input>_<speed>x.mp4 |
Custom output path |
-s, --speed |
1.2 |
Playback speed multiplier |
-t="-30dB" -d 0.8 if the default is cutting too much speech.-t="-15dB" -d 0.3 and --speed 1.5 for maximum compression.--dry-run on remove_silence.py to see what would be cut without creating a file.-o on either script to control the output path.Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
affaan-m/everything-claude-code
remotion-dev/skills
supercent-io/skills-template
heygen-com/skills
davila7/claude-code-templates
zrong/skills
Solid pick for teams standardizing on skills: raw-video-processing is focused, and the summary matches what you get after install.
We added raw-video-processing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend raw-video-processing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: raw-video-processing is the kind of skill you can hand to a new teammate without a long onboarding doc.
raw-video-processing reduced setup friction for our internal harness; good balance of opinion and flexibility.
raw-video-processing reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for raw-video-processing matched our evaluation — installs cleanly and behaves as described in the markdown.
raw-video-processing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
raw-video-processing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in raw-video-processing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 69