Hotel Amenity Clip

---
name: "hotel-amenity-clip"
description: "Turn hotel amenity stills the property already took into one hotel amenity video per labeled still. This hotel facility clip studio makes each amenity still clip from the photo the property already took, then delivers a hotel facility video, a pool amenity video, and a gym amenity clip from photos already on file. Use it for hotel amenity packs that give each still its own clip."
---

# Hotel Amenity Clips

Turn hotel amenity stills the property already took into one short
clip per labeled still. Cover pool, gym, and lobby first when those
photos exist.

## Scope and adjacent routes

Use this Skill when a hotel needs one short facility clip from each
amenity still it already photographed.

Route listing room stills to `listing-room-video-pack`. Route
assembly steps to `assembly-one-step-clip`. Route a generic still that
is not a hotel amenity to `image-to-motion`.

Read only the supplied stills and amenity names. Do not add a
facility, slogan, or camera move that is not on the list.

## Collect the amenity stills

Hard inputs are:

- at least one inspectable amenity still the host Agent can open;
- the amenity name for each still (pool, gym, lobby, spa, or another
  name the property already uses);
- a duration in the 2–15s range, or permission to use 5s.

Reuse already-known language, aspect, and must-keeps. Ask only for a
missing hard input.

Do not invent a pool, gym, or reading from a similar hotel. File
access is not consent to reuse a still outside this amenity set.

If a still exists and its amenity name is empty, stop and collect the
name.

## Plan the free shot list

Write a labeled amenity-clip list before any paid animate. One slot
per still. Each slot records the amenity name from the property, the
inspected still facts, and the chosen duration.

That list is the free visible result. Planning is not approval.

Safe defaults:

- one `beatra.videos.animate` call per still;
- `model: "auto"`;
- the still as the first frame;
- no `driving_audio`;
- a source-derived aspect ratio;
- duration 5s unless the seller names another supported integer in
  2–15.

Inspect each still. Record MIME type, width, height, aspect ratio,
byte size, and whether it has an alpha channel. For a local file,
upload only through the bundled client after inspection
(`scripts/mcp_client.py` / `beatra.assets.upload`). Keep the returned
artifact id. Never pass a local path to `beatra.videos.animate`.

## Confirm animate

Before video, call `beatra.models.list` for `image_to_video`:

```json
{"capability": "image_to_video"}
```

Admit each still against a current card that accepts a first-frame
image without driving audio. Compare every image fact and the chosen
duration with advertised constraints. If any required media fact is
unavailable or incompatible, stop before video.

Show one current production card and wait before any video
`client_request_id` or `beatra.videos.animate` call:

1. Work — one amenity clip per named still (`beatra.videos.animate`).
2. Credits — the live `image_to_video` price just read. Do not reuse a
   remembered number.
3. Count — one paid call per still.
4. Identity — one new opaque `client_request_id` per still.
5. If we stop here — the labeled shot list remains usable.
6. If the balance is insufficient — relay the official message and
   its top-up URL exactly. Translate the prose; keep the URL. Do not
   retry until the seller says they have topped up.

Submit each still once through bundled `scripts/mcp_client.py`. Poll
`beatra.tasks.get`. Read actual video MIME, duration, size, and
`billing.net_charged_credits`. Do not promise the prepaid estimate is
the final charge. A storyboard preview is not the clip review.

## Review, deliver, and recover

Review that every clip keeps the amenity shown in that still. Report
only what the host can actually see.

After a returned `task_id`, poll that task. If the create response is
lost, search with `beatra.tasks.list` and verify with
`beatra.tasks.get` before replay. Reuse an ID only with
byte-identical arguments. A changed still, prompt, duration, or model
is a new card and a new ID. Cancel only when the seller asks.

## Execution

Invoke every remote Beatra operation only through this package's bundled
`scripts/mcp_client.py`. Put the MCP tool name after `call` and send one
JSON object on standard input.

```bash
python3 scripts/mcp_client.py call beatra.models.list
```

```json
{"capability": "image_to_video"}
```

```text
printf '%s' '{"image":{"type":"artifact","artifact_id":"<the uploaded amenity still>"},"prompt":"<the written amenity name for this still>","duration":5,"client_request_id":"opaque-amenity-01"}' | python3 scripts/mcp_client.py call beatra.videos.animate
```

Do not configure or call a host Beatra Connector, and do not use
REST/OpenAPI as a fallback.

## Account balance

When the user asks how many credits remain or whether a live estimate fits,
call `beatra.wallet.get`. When they ask what was charged, call
`beatra.wallet.ledger`. Both are read-only. Do not invent an account-balance or
top-up tool. Do not make `wallet.get` a required step before every paid submit.

When a model card comes back carrying a `top_up` block, relay its tiers as the
card lists them and in that order. Do not rank them, do not talk one down, and
do not pick one for the user. Which tier suits them is their call, made on
the wallet page with the whole list in front of them. Never quote a tier from
memory.

## References by task

- For shot lists, payloads, and recovery, read
  [Hotel amenity clip workflow](references/workflow.md).
- For authorization and the non-billable registration step, read
  [installation and authentication](references/installation-and-auth.md)
  and [installation registration](references/installation-registration.md).
- For shared task, billing, and connection details, read [tasks and
  results](references/tasks-and-results.md), [billing, errors, and
  recovery](references/billing-errors-and-recovery.md), and [Bundled MCP
  Client diagnostics](references/mcp-connection.md).
- For update guarantees and controls, read [automatic updates and
  safety](references/automatic-updates-and-safety.md). For removal, read
  [uninstall and disconnect](references/uninstall-and-disconnect.md).

## Runtime and safe automatic updates

The bundled client silently checks for a newer release at most once
every 24 hours per installation. When a newer version is available, it
installs automatically without separate confirmation. It downloads only
from the fixed official Beatra discovery and immutable CDN paths for
this package, channel, and locale, verifies discovery data, archive,
manifest, and every packaged file, and replaces only package-owned
files.

Update checks, downloads, verification, replacement, rollback, and
recovery fail open: the current installation remains usable and the
original command continues. An update failure never authorizes retrying
a paid video request. The setting persists for this
installation. See
[automatic updates and safety](references/automatic-updates-and-safety.md).

```text
python3 scripts/mcp_client.py update --auto off
python3 scripts/mcp_client.py update --auto on
python3 scripts/mcp_client.py update --check
```