Turn user-supplied resident event names and points into a four-to-eight still resident event set. This community event pack studio lays out each named activity as its own resident event still. Use it for activity still pack layouts, resident event graphic packs, and community activity still sets.
Installs into .claude/skills of the current project.
Are you the author of Resident Event Set?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/beatra-ai-resident-event-set)
---
name: "resident-event-set"
description: "Turn user-supplied resident event names and points into a four-to-eight still resident event set. This community event pack studio lays out each named activity as its own resident event still. Use it for activity still pack layouts, resident event graphic packs, and community activity still sets."
---
# Resident Event Pack
Make a four-to-eight still pack from event names and points the office
already supplied. Use this Skill when a street window needs a matching
resident-event still set — one still per named activity — not a lab
cover pack and not a session cover pack.
Use `lab-cover-set` when the work is one still per named assignment.
Use `wealth-cover-set` when the work is one still per named investor
session. Use `hanzi-card-set` when the work is one still per named
character. Do not look up public posts for missing event titles. Do
not invent attendance, a ranking, an official stamp, or a red-head
notice.
## Collect supplied events
Hard inputs are the exact pack name and the user-supplied event names
and points that will appear on the stills. Do not invent an event,
attendance count, ranking, or official stamp to finish a slot. Reuse
destination (print, screen, slide), language, palette, and must-keeps
already in the conversation.
Ask only for facts that change the pack:
- exact hall, street, or pack name;
- each named activity and the points the office already approved;
- destination surface and language; and
- an optional brand still if the pack should match that look.
A scan or photo is a visual reference, not a source for missing
event titles. Uploading makes media available to Beatra and does
not inspect it. When the host cannot view a file, keep the user's
declared role for it.
Default to one still per named activity, four to eight stills in
the pack. If they name fewer than four activities, keep that count.
Cap the pack at eight. If they want a standard set and have not
numbered activities, plan four stills from the names already given.
Omit a line whose fact is missing and keep that gap on the plan so
the office can add it later.
Keep the same type, palette, and layout across the pack so the stills
read as one resident event set.
## Plan the free pack list
Write a labeled pack list before any paid image. For each activity
record the printed lines, language, layout (event name, points,
optional footer), canvas, and any optional reference role. That list
is the free visible result. Planning is not approval.
Before setting a concrete model, canvas, output count, or price, read
the current `beatra.models.list` card for `text_to_image`. Keep `model`
as `auto` and `count` at `1` per still. Default canvas is 3:4 2K for
print hall posters. Change canvas only when the user names a
destination that needs another ratio. A user who wants another
candidate adds a distinct slot and approves that new work.
Use `beatra.images.edit` only after the user accepts a still and asks
for a local correction, with that accepted image as `images[0]`.
Read [resident event pack workflow](references/workflow.md) when writing
the payload or recovering a task.
## Confirm once, create by activity
Planning is free. Before the first billable call, show one current
production card that lists every named activity still, and wait:
1. Work — one activity still per named event, a generate
call (`beatra.images.generate`).
2. Credits — the live `text_to_image` price just read. Do not reuse a
remembered number.
3. Count — one paid call per activity still. This card lists every
slot in the pack. Do not batch several activities into one
`count`. This approval does not cover retries.
4. Identity — one new opaque `client_request_id` per still. A changed
prompt, event line, file, model, or canvas mints a new ID.
5. If we stop here — the labeled pack 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 user says they have topped up.
Submit once through bundled `scripts/mcp_client.py`. Poll
`beatra.tasks.get`. Deliver actual bytes plus
`billing.net_charged_credits`. Do not promise the prepaid estimate is
the final charge.
After approval, submit each still once. Keep no more than two
generation tasks in flight on one connection.
## Review, deliver, and recover
Review printed lines against the confirmed pack list. Report only the
text the host can actually see. Treat generated small type as a review
item, not as an official notice or an attendance record.
Deliver the stills in activity order, the pack list, observed
dimensions and formats, task IDs, resolved models, and returned
`billing.net_charged_credits`. A focused correction is new paid work
with its own card and ID.
After a returned `task_id`, poll that task. If the create response is
lost, retry only the identical frozen payload with the original ID. If
the task ID is missing, use `beatra.tasks.list` and verify candidates
with `beatra.tasks.get` before another submit. Use `beatra.tasks.cancel`
only when the user 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": "text_to_image"}
```
```text
printf '%s' '{"prompt":"Create the approved resident-event still for the named activity. Print only the confirmed event name and points. Keep the shared pack look.","model":"auto","count":1,"canvas":{"type":"preset","tier":"2K","aspect":"3:4"},"client_request_id":"opaque-resident-event-01"}' | python3 scripts/mcp_client.py call beatra.images.generate
```
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 pack lists, payloads, confirmation, polling, recovery, and review,
read [resident event pack 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 image 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
```
