skills.rest
alvis
alvisCOMMUNITY
Explore all skills by this author →
Website𝕏@alvishttangGitHub

review-render

Records stakeholder feedback and approvals bound to exact render revisions and timecode ranges.

4|1|Updated Jul 31, 2025
Search Tags:#video production#approval workflow#post-production#stakeholder feedback#timecode#revision tracking#render review
One-click install
npx skills add https://github.com/alvis/.agents --skill review-render-alvis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-render
Source: https://github.com/alvis/.agents/tree/main/plugins/production/skills/review-render
Command: npx skills add https://github.com/alvis/.agents --skill review-render-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Stakeholder feedback like "approved" or "make the text larger" is meaningless without knowing exactly which render revision it applies to, and approvals silently carrying over to new revisions cause costly mistakes in video production. ## Core Features & Use Cases - Revision-Bound Review Records: Every disposition binds to one render id at one immutable revision, with timecode ranges for positional feedback. - Approval Lifecycle Management: Classifies feedback as change requests, questions, observations, or approvals/rejections, and evaluates whether prior approvals lapse when a new revision arrives. - Use Case: A client says "approved" on cut v7, then v8 is rendered. Use this Skill to record the original approval against v7, report that it lapsed for v8, and identify which scoped aspects (e.g., brand palette) a superseding decision preserves. ## Quick Start Record the stakeholder feedback "approved the pacing but make the title text larger" against render promo-cut at revision v7.

Frequently Asked Questions about review-render

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record stakeholder approval for a video render?▼

Record an approval with the full binding tuple: render id, immutable revision, reviewer and their authority, approved scope, timestamp, and unresolved exceptions. If the feedback names no revision, confirm the exact render entry before recording anything.

Does an approval carry over when a new render revision is created?▼

No, approvals never carry forward to a new revision automatically. Each prior approval is evaluated as lapsed, and only aspects named in a superseding decision's preserves list, such as brand palette or CTA, remain current.

Can partial feedback count as a full render approval?▼

No, scoped or partial feedback is never upgraded into a full approval. An approval of named aspects like pacing or grade is recorded as scoped approval only, and missing tuple fields must be filled by the user rather than inferred.

What happens when a decision invalidates an approved render?▼

The historical approval is never rewritten or deleted. A validity stale mark is routed to the asset tracking skill, the review consequence is recorded, and new remediation work carries the rework.

Does this skill edit media files or the asset manifest?▼

No, it never edits media and only routes validity marks through the separate track-assets skill. It records review truth in a namespaced review file while the main agent handles all writes.

Related Skills

Explore More Design & Creative Skills→
synthaicodesynthaicode
4

presentation_flow_review

Review and restructure presentation slide order into an explicit causal argument flow.

Community
Intermediate
x85446x85446

pm-auditor

Detect stale downstream features, epics and tests via base_version tracking and cascade analysis.

Community
Advanced
xotongxotong

context-save

Capture git state, decisions, and remaining work for session resumption.

Community
Intermediate
wangcb8i8iwangcb8i8i

revise-markdown

Identify, resolve, and remove all embedded review comments in markdown documents.

Community
Intermediate