read_skill

com.frapea/editor · Verify this server

Returns Frapea's agent guide: editing conventions, tool workflow tips, the current feature surface, and the CREATIVE MANDATE — how far to run with a terse brief (source stock footage, sounds, voiceover, motion graphics and deliver a finished video vs. when to hand control back to the user). Read once at the start of an editing session. MOTION topics: 'motion' is the API surface (imports, fonts, props schema, the parts-board-first golden example) and routes to the rest — read before create_motion_composition; 'motion-examples' (two finished pieces that differ in look); 'motion-craft' (anticipation, overshoot, stagger, the tells of machine-made motion — read with 'motion', always); 'motion-text' (size floors, fitting copy that cannot clip, per-word animation, annotations); 'motion-effects' (grain, duotone, light leaks, blurs, glow); 'motion-transitions' (TransitionSeries, presentations, cut overlays); 'motion-sound' (where sound lives, the built-in SFX pack, placement and levels); 'motion-review' (the same loop as 'review', from a motion job). The CRAFT guides teach how to actually cut: 'core' (rhythm, b-roll, audio hierarchy, restraint — read first), then the format you are making — 'shorts' | 'longform' | 'podcast' | 'tutorial' | 'montage'. Also 'voiceover' (read BEFORE generate_voiceover: narration is generated in segments, not one block) and 'verify' (how to prove the cut is right — read before every export), and 'review' (for any piece with an audience: an opponent argues with your rendered frames in rounds until it is finished — read before you start).