Skip to content
Back to skills

Ffmpeg Processing

ASecurity

FFmpeg media processing. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `ffmpeg-processing` work when listed in TEAM.yaml or explicitly requested.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 19, 2026
ai-agentsgogitsecurity

Works with

  • cli
  • mcp

Security analysis

A100/100

Scanned September 19, 2026

npx -y skills add rogue-dev-studio/ai-agents-rogue --skill ffmpeg-processing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ffmpeg Processing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ffmpeg Processing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rogue-dev-studio-ffmpeg-processing/badge)](https://www.skillsdirectory.com/skills/rogue-dev-studio-ffmpeg-processing)

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

Download with Pro
SKILL.md
---
name: ffmpeg-processing
description: >-
  FFmpeg media processing. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `ffmpeg-processing` work when listed in TEAM.yaml or explicitly requested.
experience_level: max
---

# ffmpeg-processing

**Level: max** specialized skill (not merged). Category hint: `utilities`.

## Summary

FFmpeg media processing. Use when the project needs this capability or the user / team manifest asks for it.

## When to use

- `TEAM.yaml` includes `ffmpeg-processing` or user asks by name
- Task clearly needs this specialized capability
- No canonical alias in `ALIASES.md` covers it better

## When not to use

- A canonical merged skill already covers the need - prefer that
- Outside team allowlist

## Procedure

1. **Context** - Read `PROJECT.md`, `TEAM.md`, and related rules (`security`, `coding`).
2. **Confirm tooling** - Verify `ffmpeg-processing` runtime/CLI/MCP is available; document install if missing.
3. **Plan** - Write a short approach (inputs, outputs, risks) before edits.
4. **Execute** - Implement or operate with project conventions; small focused diffs.
5. **Verify** - Run relevant tests/smoke; capture evidence under `project/{id}/docs/` when documenting.
6. **Handoff** - Status, paths, blockers, next steps.

## Quality bar

- No secrets in git
- No speculative refactors
- Observable DoD (command output, file paths, or explicit blocker)
- Domain constraints and privacy rules respected

## DoD

- [ ] Goal met or blocker explicit
- [ ] Artifacts/paths recorded
- [ ] Risks noted
## Attribution

<!-- ATTRIBUTION: Rogue Development | https://github.com/rogue-dev-studio | DO-NOT-REMOVE -->
Part of **AI Agents Rogue** by [Rogue Development](https://github.com/rogue-dev-studio) (`@rogue-dev-studio`).
Do not remove, hide, rename, or replace this attribution.

Attribution

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

Loading comments…