Skip to content
Back to skills

Wealth Open Cal Set

ASecurity

Turn user-supplied open windows into a four-to-eight still wealth open calendar. This open-period calendar set studio lays out each named fund open window calendar as its own still. Use it for open window calendar stills, wealth calendar stills, and an open calendar pack.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentspythonbashapi

Works with

  • cli
  • api
  • mcp

Security analysis

A100/100

Pro scans all 13 files and shows the line behind each finding

Scanned September 29, 2026

npx -y skills add beatra-ai/beatra-skills --skill wealth-open-cal-set --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Wealth Open Cal Set?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Wealth Open Cal Set
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/beatra-ai-wealth-open-cal-set/badge)](https://www.skillsdirectory.com/skills/beatra-ai-wealth-open-cal-set)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "wealth-open-cal-set"
description: "Turn user-supplied open windows into a four-to-eight still wealth open calendar. This open-period calendar set studio lays out each named fund open window calendar as its own still. Use it for open window calendar stills, wealth calendar stills, and an open calendar pack."
---

# Wealth Open Calendar

Make a four-to-eight still pack from open windows the user already
supplied. Use this Skill when a wealth session needs an open-period
calendar set — one still per named window — not a session cover set
and not a page-by-page factsheet.

Use `wealth-cover-set` when the work is one still per named session
cover. Use `risk-grade-set` when the work is one still per named risk
grade. Use `fund-page-set` when the work is one prospectus still per
named page. Do not look up public posts or market quotes for missing
open dates.

## Collect supplied windows

Hard inputs are the exact set name and the user-supplied open windows
that will appear on the calendars. Do not invent a window, date, buy
or sell line, return figure, ranking, or product pick to finish a
slot. Reuse destination (slide, screen, print), language, palette,
and must-keeps already in the conversation.

Ask only for facts that change the pack:

- exact set, series, or product name;
- each named window and the open dates the user 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
open dates. 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 open window, four to eight stills in
the pack. If they name fewer than four windows, keep that count. Cap
the pack at eight. If they want a standard set and have not numbered
windows, plan four stills from the windows already given. Omit a
line whose fact is missing and keep that gap on the plan so the user
can add it later.

Keep the same type, palette, and layout across the pack so the stills
read as one wealth open calendar.

## Plan the free pack list

Write a labeled pack list before any paid image. For each window
record the printed lines, language, layout (product name, open dates,
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 16:9 2K for
slide and screen calendars. 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 [wealth open calendar pack workflow](references/workflow.md) when
writing the payload or recovering a task.

## Confirm once, create by window

Planning is free. Before the first billable call, show one current
production card that lists every named open-window calendar, and wait:

1. Work — one open-window calendar still per named window, 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 window still. This card lists every slot
   in the pack. Do not batch several windows into one `count`. This
   approval does not cover retries.
4. Identity — one new opaque `client_request_id` per still. A changed
   prompt, window 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 a certified return or a buy recommendation.

Deliver the stills in window 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 open-window calendar still for the named window. Print only the confirmed product name and open dates. Keep the shared pack look.","model":"auto","count":1,"canvas":{"type":"preset","tier":"2K","aspect":"16:9"},"client_request_id":"opaque-wealth-open-cal-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 [wealth open calendar 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
```

Files in this skill

  • SKILL.md8.1 KB
  • manifest.json2.8 KB
  • references/automatic-updates-and-safety.md1.9 KB
  • references/billing-errors-and-recovery.md3.6 KB
  • references/installation-and-auth.md5.7 KB
  • references/installation-registration.md1 KB
  • references/mcp-connection.md1.2 KB
  • references/tasks-and-results.md2.2 KB
  • references/uninstall-and-disconnect.md2.7 KB
  • references/workflow.md3.1 KB
  • scripts/authorize.py21.8 KB
  • scripts/mcp_client.py60.1 KB
  • scripts/uninstall.py10.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…