Fetches video-processing-editing from erichowens/some_claude_skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/video-processing-editing
Restart Cursor to activate video-processing-editing. Access via /video-processing-editing in your agent's command palette.
⚠
Security Notice
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.
Correct approach 1: Chain operations in single command
# ✅ Single-pass encoding with all operationsffmpeg -ss 00:01:00 -i input.mp4 -i audio.mp3 \-to 00:04:00 \-vf"subtitles=subs.srt"\-map0:v -map1:a \-c:v libx264 -crf18-preset medium \-c:a aac -b:a 192k \ output.mp4
# Single re-encode, all operations applied at once
Problem: Color shifts, mismatched brightness, broken playback.
Wrong approach:
# ❌ Concatenate videos with different color spaces# clip1.mp4: BT.709 (HD), yuv420p# clip2.mp4: BT.601 (SD), yuvj420p (full range)# clip3.mp4: BT.2020 (HDR), yuv420p10le# Create concat listecho"file 'clip1.mp4'"> list.txt
echo"file 'clip2.mp4'">> list.txt
echo"file 'clip3.mp4'">> list.txt
# Concatenate without color normalizationffmpeg -f concat -safe0-i list.txt -c copy output.mp4
# Result: Color shifts between clips, broken HDR metadata
Why wrong:
Different color spaces (BT.601 vs BT.709 vs BT.2020)
Different pixel formats (yuv420p vs yuvj420p)
Different color ranges (limited vs full)
Metadata conflicts
Correct approach:
# ✅ Normalize color space before concatenation# Step 1: Analyze color space of each clipffprobe -v error -select_streams v:0 \-show_entriesstream=color_space,color_transfer,color_primaries,pix_fmt \-ofdefault=noprint_wrappers=1 clip1.mp4
# Step 2: Normalize all clips to common color space# Target: BT.709 (HD), yuv420p, limited range# Normalize clip1 (already BT.709)ffmpeg -i clip1.mp4 -c copy clip1_normalized.mp4
# Normalize clip2 (BT.601 SD → BT.709 HD)ffmpeg -i clip2.mp4 \-vf"scale=in_range=full:out_range=limited,colorspace=bt709:iall=bt601:fast=1"\-color_primaries bt709 \-color_trc bt709 \-colorspace bt709 \-c:v libx264 -crf18-preset medium \-c:a copy \ clip2_normalized.mp4
# Normalize clip3 (BT.2020 HDR → BT.709 SDR)ffmpeg -i clip3.mp4 \-vf"zscale=t=linear:npl=100,format=gbrpf32le,zscale=p=bt709,tonemap=hable:desat=0,zscale=t=bt709:m=bt709:r=limited,format=yuv420p"\-color_primaries bt709 \-color_trc bt709 \-colorspace bt709 \-c:v libx264 -crf18-preset medium \-c:a copy \ clip3_normalized.mp4
# Step 3: Concatenate normalized clipsecho"file 'clip1_normalized.mp4'"> list.txt
echo"file 'clip2_normalized.mp4'">> list.txt
echo"file 'clip3_normalized.mp4'">> list.txt
ffmpeg -f concat -safe0-i list.txt -c copy output.mp4
Color space guide:
Standard
Color Space
Transfer
Primaries
Use Case
BT.601
SD
bt470bg
bt470bg
Old SD content
BT.709
HD
bt709
bt709
Modern HD/FHD
BT.2020
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ 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.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
