Skip to content
Agentmart
Submit a tool

plan-trailer

Research references and plan trailers for a work, product, event, or experience.

Skill by JoseArron

IndexedMIT★ 2
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/josearron-plan-trailer

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Research references and plan trailers for a work, product, event, or experience. Use for treatments, storyboards, shot plans, pacing, edit briefs, or music research when a track drives the sequence.

Use cases: writing, research

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/plan-trailer

What's inside

Skill name
plan-trailer
Description
Research references and plan trailers for a work, product, event, or experience. Use for treatments, storyboards, shot plans, pacing, edit briefs, or music research when a track drives the sequence.
License
MIT
Instructions
31 lines in SKILL.md · view on GitHub

Files (3)

  • EDIT-PLAN.md
  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# Plan a trailer

Turn purpose, available material, and direction into an editable sequence. Match the intended experience and make the subject clear. Choose genre, cultural context, tone, and pacing from the brief.

## Identify the output

Use project context, audience, channel, length, direction, available footage, and music when relevant. Distinguish music research, reference research, treatment, storyboard, edit plan, and assembled trailer. For research-only requests, do not fabricate a final sequence or claim to have edited footage.

## Research songs and trailers

Choose references for the subject and intended audience. Prefer official trailers, creator releases, and production breakdowns; for song research, use official artist releases and authorized lyric publications. Inspect audio/video for claims about timing and structure. Link the version examined and useful timestamps.

For thematic searches, record motif, language, artist, evidence, and whether it appears in a verse, repeating hook, chorus, bridge, or another identifiable section. Separate lyrical references from title matches and inferred themes. Quote within applicable limits, normally no more than ten lyric words from a song source; paraphrase the rest and link it.

For trailer references, explain techniques to borrow: opening image, reveal, escalation, pauses, cuts, readable subject matter, typography, ending, and sound or music relationships when relevant. A link list does not explain fit.

Do not invent BPM, bars, section labels, or timestamps from URLs or snippets. Measure or verify them, or label the structure provisional. Online availability does not establish permission for release; record supplied or verified usage status without presenting research as clearance.

## Build the plan

Use [EDIT-PLAN.md](EDIT-PLAN.md) for executable fields. Let the brief determine whether story, demonstration, imagery, voice, sound, or music drives the structure. For a music-led sequence, phrasing, density changes, vocal emphasis, silence, and transitions provide cues. Cutting on every beat is an option, not a default.

Keep the promised experience visible. Distinguish available footage, staged captures, and material needing production. Allow reading time for text. Represent the work or product accurately; for games, distinguish actual mechanics from cinematics.

Use `design-motion` for detailed graphic movement, `write-image-prompts` for storyboard prompts, and `create-procedural-art` for code-generated shots when requested. Load only relevant skills through the available mechanism or read their entrypoints.

## Verify

For plans, check duration, sources, dependencies, and correspondence to the chosen narrative or musical structure. For assembled sequences, watch with and without sound; inspect readability, footage claims, transitions, mix, and export settings. State missing footage, provisional cues, and unchecked timing accurately.

From JoseArron/skills, MIT.

More from JoseArron/skills

Signals

Stars
2
Forks
0
Open issues
0
Last commit (this folder)
Oct 11, 2026 (18 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from JoseArron

Cite this page

plan-trailer skill. Agent Mart. https://agentmart.dev/skills/josearron-plan-trailer (last updated 2026-10-24)