Media Analysis
Analyze the user's link, local file, or visible images and deliver readable
findings with the actual visual evidence. Choose the necessary work internally.
Choose the work
- Video understanding: use
postplus media analyze video-analysis
for
actions, sound, dialogue, and development over time. Pass the original source;
the CLI owns acquisition and transfer. Read execution and recovery.
- Readable images: view them directly. No download, upload, or Gemini call
is needed for images already accessible in the conversation or locally.
- Native image posts: use
postplus media prepare --source <url>
, then
inspect the ordered originals. Read image evidence.
- Screenshots, text, color, or layout: inspect sufficient images or local
video frames without purchasing full video analysis. Read video frames.
An MP4 made from stills remains a video with a real timeline. Preparation must
return an actual local file before you treat it as downloaded evidence.
Keep multiple sources, failures, and outputs separate. Answer
follow-ups from existing reports and evidence without another paid analysis.
Video command
<!-- BEGIN GENERATED EXECUTION EXAMPLE -->
bash
postplus media analyze video-analysis \
--video ./reference.mp4 \
--output ./result.md
Bounded recovery: Current PostPlus CLIs handle a compatible update and retry the command once when no agent-session restart is required. If an older CLI only reports that an update is required, run
and retry once under the same condition. For a missing or invalid CLI session, run
yourself; it opens the browser by default. Immediately share its exact URL as a clickable link for the user to
Connect, then retry the original command once only after the CLI confirms success. Never ask the user to run the command or enter/compare a code, approve the connection for them, or automatically restart a cancelled/expired login. For a local usage rejection before remote work starts, use that command's
to make one unambiguous correction from existing user input and retry once.
If PostPlus returns
postplus_cli_balance_required
with an
user action, give the user its exact label and URL and stop for account action. Do not invent a checkout link, claim whether provider work or charging occurred, or blindly resubmit after payment; continue from the command's documented status or checkpoint once the user confirms credits are available.
Otherwise stop and report the exact error. Never expose login polling secrets, resubmit an operation when remote work may have started, change user intent, bypass approval, switch providers, rewrite payloads, or make a second recovery attempt. After success, briefly say that PostPlus updated, using only the official update details PostPlus reported.
<!-- END GENERATED EXECUTION EXAMPLE -->
Omit
for the default shot table and production notes described in
video report. Supply it for the user's
specific question or requested format; do not append an unrelated full report.
is the CLI capability key, not another Skill.
Use
postplus media schema --json
only when constructing or repairing an
unknown hosted media request shape; keep the generated command above for the
normal analysis path.
Deliver
Embed inspected images or real screenshots in the conversation or Markdown,
with source, original page index or measured video timestamp, and the observation
each supports. Paths or folder links alone are not visual delivery. Never replace
missing evidence with a cover, generated image, or guessed description.
For a long report, show representative frames in chat and link the full Markdown.
Preserve returned model Markdown unchanged; add Agent-viewed screenshots and any
corrections in a separate evidence note. Save attachments beside the report using
relative links, verify those links, and retain them after temporary cleanup.
Never delete user files or delivered evidence.
State missing pages, unreadable text, unavailable audio, and inspected subsets.
A few frames do not prove full audio/video coverage. Distinguish visible facts,
captured wording, interpretation, and claims that need external verification.
Recover
Report observed progress while waiting. Let the CLI perform bounded recovery;
after a disconnected wait use its emitted poll or checkpoint command for the
same task, account, and environment. Do not restart an uncertain paid analysis.
A content-quality concern or rewording request does not authorize a paid redo.
For an unambiguous local parameter rejection before remote work starts, use the
command's
and existing user input for one correction. If submission may
have started, follow only its emitted recovery command. Use
postplus doctor --skill media-analysis
for readiness
diagnostics after a readiness failure. Preserve task identity if submission may have happened.
Honor quote challenges using existing explicit cost authorization when sufficient;
otherwise ask for approval, then use the provided confirmation/retry commands.
For a terminal failure, give its stage, reason, operation id when present, cost
status, and concrete next step. Unknown results do not mean no charge. Deliver
useful partial evidence with its limits; never claim unseen material was analyzed.