render-qa
/render-qa
Produce and verify code-rendered films, animation, browser scenes, and audio/video deliverables. Use for Remotion, Three.js, canvas, or FFmpeg media tasks that require finished artifacts, visual quality checks, and resumable multi-agent production.
- Author
- FlintSH ↗
- Repository
- tinderbox ↗
- Licence
- MPL-2.0
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MPL-2.0, otwarta.
What it does and when to use it
Produce and verify code-rendered films, animation, browser scenes, and audio/video deliverables. Use for Remotion, Three.js, canvas, or FFmpeg media tasks that require finished artifacts, visual quality checks, and resumable multi-agent production.
Original author description
Produce and verify code-rendered films, animation, browser scenes, and audio/video deliverables. Use for Remotion, Three.js, canvas, or FFmpeg media tasks that require finished artifacts, visual quality checks, and resumable multi-agent production.
How it works
SKILL.md has no level-two headings · 38 lines, 335 words
SKILL.md preview
--- name: render-qa description: Produce and verify code-rendered films, animation, browser scenes, and audio/video deliverables. Use for Remotion, Three.js, canvas, or FFmpeg media tasks that require finished artifacts, visual quality checks, and resumable multi-agent production. --- # Deliver the actual rendered artifact Use the project's chosen engine. Load Remotion skills only for Remotion work; do not migrate a Three.js/canvas film merely because Remotion skills are installed. 1. Read the creative brief, storyboard, source/truth rules, ownership map and existing status documents. Distinguish confirmed facts from dramatization. Honor project privacy/redaction rules and keep credentials out of artifacts. 2. Define deliverables and measurable acceptance: duration, resolution, frame rate, audio format/loudness, captions, titles, typography, visual consistency, pacing and final export paths. Resolve consequential creative ambiguity early. 3. For a multi-agent project, identify one coordinator, one Git writer, file ownership and a render lock. Parallel departments must not race on generated assets, shared output paths, dependency installation or the final export. 4. Start with a representative short render and contact sheet. Fix engine-level defects before rendering the whole film. Use deterministic seeds/time and staged outputs. Default to one heavy render at a time unless the machine clearly has headroom. 5. Inspect real frames at transitions and difficult typography. Check clipping, contrast, legibility, caption timing, missing assets and empty/black frames. For audio, inspect levels, true peaks, duration, continuity and sync; use listening when available and state when an audio judgment is only automated. 6. Render the actual final files, then use ffprobe/FFmpeg and project checks to verify containers, codecs, dimensions, frame rate, duration, audio tracks, caption tracks and decode errors. Inspect a fresh sample of the final export, not just the pre-export browser preview. Record content hashes in a manifest. 7. Keep review loops focused and budget-aware. Correct concrete defects before convening another broad review; don't exhaust the account on duplicate panels. Save a concise status/handoff before session rollover. 8. Deliver reachable artifact links using the project's configured destination and authorized credentials. Never invent a successful upload or reuse tokens copied out of old chat history. Report remaining quality limitations honestly. Prose, release notes and explanatory copy should match the user's existing voice and any voice rules in their global instructions: direct, specific and low-hype by default.
Versions
The database has no other skills named render-qa.
Database snapshot: 13.11.2026 · package version 0550eebb82b4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90media-production
Create and process finished videos with Remotion, Motion Canvas, Manim, FFmpeg or an available AI video provider. Use when producing a video, UI demo, explainer, subtitles, narration timeline or format conversion; select the renderer from the content rather than defaulting every video to one engine. - 95Remotion
Programmatic video creation with React. USE WHEN video, animation, motion graphics, video rendering, React video, intro video, YouTube video, TikTok video, video production, render video. - 95remotion-video-composition
Provider-independent production workflow for assembling generated or sourced media into React/Remotion videos. Use when an agent must plan, build, render, review, variant-render, or hand off Remotion compositions with media custody, captions, audio, animation, accessibility,… - 95Remotion
Programmatic video creation with React via Remotion — compositions, animations, motion graphics, rendered to MP4. USE WHEN video, animation, motion graphics, video rendering, React video, intro video, YouTube video, TikTok video, video production, render video, content to… - 100remotion-script-writer
Write a complete, render-ready Remotion video script as structured JSON: analyze the user's codebase or product, break the video into timed scenes, specify every visual element, animation, transition, and voiceover line, and list required assets and Remotion packages. Use… - 100frame-inspect
動画・画像のフレーム抽出、Remotion レンダリング、仕様チェック、目視検証を行う汎用ビデオツールキット。 ffmpeg / ffprobe / remotion still / remotion render を統一シェルスクリプト (video-tool.sh) で操作し、 Read ツール(マルチモーダル対応)で実際の見た目を確認して品質レポートを出す。 Use when: 動画のフレームを確認したい、レンダリング結果を検証したい、 画像の品質を目視チェックしたい、Remotion プロジェクトを MP4 に出力したい、…