premiere-look-effects

Build consistent, reversible visual effect recipes in Adobe Premiere Pro from effects confirmed as installed. Use for clip effects, parameterized looks, motion treatments, vignettes, controlled tests, or applying one approved recipe across multiple clips through the Premiere Pro MCP server.

Jump to install

Repository: ayushozha/AdobePremiereProMCP
Last source activity: August 6, 2026 at 17:50
Detected SKILL.md language: English
Stars: 90
Forks: 20

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/ayushozha/AdobePremiereProMCP --skill premiere-look-effects

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Premiere Look Effects

Discover capabilities from the host and test a look on one representative clip before batching it.

Required server profile

Start or restart the MCP server with MCP_TOOL_PROFILE=effects for the smallest dedicated surface. The default standard profile also contains this skill's verified discovery, attachment, parameter-update, and readback tools.

Workflow

Inspect the project, timeline, installed effects, and current clip effect chain. Resolve the active sequence index, call premiere_duplicate_sequence, verify exactly one new copy, and activate it with premiere_set_active_sequence. Leave the source sequence untouched as the recovery boundary.

Record the current chain with premiere_get_clip_effects and the sequence hash. Use premiere_snapshot_timeline or premiere_save_sequence_version only as optional audit records; neither restores a whole sequence.

Build a minimal ordered recipe using only display names returned by premiere_get_installed_effects.

Apply one effect at a time with premiere_apply_video_effect. Require a public-DOM component-count increase and the attached component name.

Set only properties actually exposed by that component with premiere_set_effect_parameter; read the chain and values back before continuing.

Test the recipe on one representative clip. If application or parameter readback fails, stop, reactivate the untouched source sequence, and report the failed duplicate for inspection; do not attempt an unverified component removal or undo. After approval, repeat the same verified steps on additional clips and stop on the first mismatch.

Guardrails

Never assume an effect display name exists; confirm it with premiere_get_installed_effects.

Avoid destructive baking. Keep changes parameterized and reversible.

Do not use legacy effect-enable or named grain, glow, vignette, drop-shadow, stroke, and cinematic-bar helpers in this verified workflow; they either lack portable component-state readback or can return instructions/requested values instead of a verified mutation. Use the generic verified effect path.

Do not claim visual quality from parameter success alone; request a frame review when appearance matters.