by Don-Uwe
:four_leaf_clover: ai agent video editor to feed raw footage and a creative brief, and a coordinated agent ensemble handles shot selection, agentic video trimming, video rendeing and agentic ai qualify review
# Add to your Claude Code skills
git clone https://github.com/Don-Uwe/video-editor-ai-agentGuides for using ai agents skills like video-editor-ai-agent.
video-editor-ai-agent is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Don-Uwe. :four_leaf_clover: ai agent video editor to feed raw footage and a creative brief, and a coordinated agent ensemble handles shot selection, agentic video trimming, video rendeing and agentic ai qualify review. It has 90 GitHub stars.
video-editor-ai-agent's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/Don-Uwe/video-editor-ai-agent" and add it to your Claude Code skills directory (see the Installation section above).
video-editor-ai-agent is primarily written in TypeScript. It is open-source under Don-Uwe on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh video-editor-ai-agent against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Production-oriented fork of an AI-assisted video pipeline. Feed raw footage and a creative brief; a coordinated agent ensemble handles shot selection, trimming, rendering, and quality review.
The CLI is the primary, fully supported interface. AVE Studio (Next.js + Hono API) provides an experimental non-linear editor shell with optional Redis-backed persistence.
Built as a TypeScript monorepo (apps/ + packages/) with shared infrastructure in @ave/core (config, logging, errors, Redis, Zod schemas).
| Capability | Description |
|---|---|
| Agent pipeline | Director, Trim Refiner, Editor, and Reviewer orchestrated from YAML manifests |
| Preprocessing | Footage indexing via ffprobe (scene detection / transcription are planned enhancements) |
| Retry loop | Reviewer-driven quality gate with configurable thresholds and versioned outputs |
| Style templates | Structured YAML guidance for pacing, overlays, and segment structure |
| AVE Studio | Web UI with timeline, monitors, inspector, and live job streaming |
| Persistence | Optional Redis layer for job snapshots and Studio cache |
| Configurable security | CORS and filesystem browse roots controlled via environment variables |
flowchart TB
subgraph Input
Footage[Raw footage folder]
Brief[Creative brief JSON]
Pipeline[Pipeline YAML]
end
subgraph Core["TypeScript core (@ave/domain)"]
Pre[Preprocess\nffprobe indexing]
Runner[Pipeline runner]
Director[Director agent\nGemini]
Trim[Trim Refiner]
Editor[Editor / FFmpeg]
Reviewer[Reviewer agent\nGemini]
end
subgraph Output
MP4[Rendered MP4]
Scores[Review scores]
end
Footage --> Pre
Pre --> Runner
Brief --> Runner
Pipeline --> Runner
Runner --> Director --> Trim --> Editor --> Reviewer
Reviewer -->|score below threshold| Director
Editor --> MP4
Reviewer --> Scores
flowchart LR
Browser[Browser\nNext.js Studio]
NextAPI[Next.js API routes\n/cache]
Hono[Hono API\n@ave/api]
Redis[(Redis\noptional)]
Pipeline[Pipeline runner]
Browser -->|REST + WebSocket| Hono
Browser --> NextAPI
NextAPI --> Redis
Hono --> Redis
Hono --> Pipeline
PATHgit clone https://github.com/your-org/agentic-video-editor.git
cd agentic-video-editor
npm install
cp .env.example .env
# Edit GOOGLE_API_KEY and optional Redis settings
Environment variables are loaded automatically by the CLI, API, and Studio.
| Variable | Default | Purpose |
|---|---|---|
GOOGLE_API_KEY |
— | Required for Gemini agents |
AVE_LOG_LEVEL |
info |
Logging verbosity |
AVE_OUTPUT_DIR |
output |
Render output directory |
AVE_CORS_ORIGINS |
http://localhost:3000,... |
Allowed browser origins |
AVE_BROWSE_ROOTS |
~ |
Comma-separated roots for /api/browse |
REDIS_ENABLED |
true |
Toggle Redis features |
REDIS_URL |
redis://127.0.0.1:6379 |
Redis connection URL |
REDIS_KEY_PREFIX |
ave: |
Key namespace prefix |
PORT |
8000 |
Hono API listen port |
NEXT_PUBLIC_API_URL |
`` | Override API base URL in Studio |
See .env.example for the full list including Redis tuning options.
npm run dev:cli -- edit \
--footage-dir /path/to/footage \
--brief '{"product": "My Product", "audience": "Women 25-45", "tone": "authentic", "duration_seconds": 30}' \
--pipeline pipelines/ugc-ad.yaml \
--style styles/dtc-testimonial.yaml
Briefs may be inline JSON or a path to a .json file. Outputs land in output/ with versioned filenames when the reviewer triggers retries.
{
"product": "Product name",
"audience": "Target demographic",
"tone": "energetic, calm, professional",
"duration_seconds": 30,
"style_ref": "styles/dtc-testimonial.yaml"
}
npm run dev:cli -- edit --footage-dir ./footage --brief brief.json
Terminal 1 — API:
npm run dev:api
Terminal 2 — Studio:
npm run dev:studio
npm run validate # typecheck + lint + test + build (all workspaces)
npm run typecheck
npm run lint
npm run test
npm run build
On Windows, scripts/validate.ps1 runs the same checks.
| Suite | Scope |
|---|---|
npm test (root) |
Vitest unit tests under tests/unit/ |
| Studio lint | ESLint + TypeScript in @ave/studio |
Core pipeline integration tests are intentionally deferred — they require Gemini credentials and FFmpeg fixtures.
agentic-video-editor/
├── apps/
│ ├── api/ # Hono REST + WebSocket (@ave/api)
│ └── studio/ # Next.js frontend (@ave/studio)
├── packages/
│ ├── core/ # Config, logging, errors, Redis, schemas
│ ├── domain/ # Pipeline, agents, FFmpeg tools
│ └── cli/ # `ave` CLI entry point
├── pipelines/ # YAML pipeline manifests
├── styles/ # Director style templates
├── tests/unit/ # Vitest unit tests
├── docs/internal/ # Maintainer audit notes
└── scripts/ # validate.ps1 / validate.sh
Structure decisions are documented in docs/internal/STRUCTURE.md.
| Symptom | Likely cause | Fix |
|---|---|---|
GOOGLE_API_KEY errors |
Missing or invalid key | Set in .env or export in shell |
| Browse returns 403 | Path outside AVE_BROWSE_ROOTS |
Add parent directory to roots |
| Redis unavailable | Server not running | Start Redis or set REDIS_ENABLED=false |
| FFmpeg not found | Binary not on PATH | Install FFmpeg and verify with ffmpeg -version |
| Studio cannot reach API | Wrong proxy target | Set NEXT_PUBLIC_API_URL=http://localhost:8000 |
Check Redis connectivity from Studio:
curl http://localhost:3000/api/cache/status
Is the web UI production-ready?
No. AVE Studio is experimental. Use the CLI for reliable workflows.
Do I need Redis?
No. The app runs without Redis; persistence and cache features degrade gracefully.
Can I add custom agents?
Implement an agent under packages/domain/src/agents/ and reference it in a pipeline YAML manifest.
How are retries versioned?
Each reviewer-triggered retry writes {name}_v{N}.mp4 so you can compare iterations.
npm run validate.MIT