blushneybusiness-glitch/roblox-omniskills/rbx-handoff-account

rbx-handoff-account

Triggers

Ownership questions surface late and cost the most: a place published under a personal account cannot sell passes attached to the group, and an animation or audio file uploaded under the wrong creator will not load for players. Fire this skill the moment a game is meant to be group-owned, a collaborator is added, revenue is shared, or an Open Cloud key is needed (rbx-opencloud).

The credential law, above every other rule here: prompts never contain and never request a password, a 2-Step Verification code, a .ROBLOSECURITY cookie, or an API key's text. The operator signs in themselves, in their own browser. Anything secret that comes back in chat is already in a log — ask for confirmation that the key exists and which scopes it carries, never for the key.

Do first (all of it, before any handoff)

1. Decide the owner before anything is published. Group-owned when revenue is shared,

collaborators exist, or the brand outlives one account; personal otherwise. Migrating a published place between owners loses its ids and its player base, so this is a one-time decision made deliberately, not discovered.

1. Write the role table: role name, rank number (0–255, Guest is 0, Owner is 255), and

the permissions each role gets — who edits experiences, who sees group funds, who posts. The prompt executes this table; it does not negotiate it.

1. Wire group perks code-side against the placeholder group id: Player:IsInGroup for

the join-for-a-bonus loop, Player:GetRankInGroup for role-gated doors and admin, both pcall'd and cached per session — group membership does not refresh mid-session, so the perk copy says "rejoin to claim" (rbx-badges-groups holds the perk patterns).

1. State the costs you already know the operator will hit: group creation costs 100

Robux, and group payouts require the owner account's 2-Step Verification to be enabled.

1. For API keys, prepare the scope list — least privilege, one key per purpose, an IP

allowlist and an expiry date decided in advance (rbx-opencloud).

The prompt

Fill cowork-handoff-template.md, identity header first, then STEPS per family:

• Group creation — roblox.com → Groups → Create (100 Robux fee, stated in the prompt),

name and description supplied verbatim, then Configure Group → Roles: create each row of the role table with its exact rank number, then tick permissions per role.

• Publish under the group — Studio → File → Publish to Roblox As → select the group.

The operator's role must hold the permission for creating and editing group experiences, or the group will not appear in the list; that failure is a permissions answer, not a bug.

• Collaborators — create.roblox.com → Creations → experience → Permissions: add the

username with the named access level. Usernames are supplied exactly, with the user id where known, since display names are not unique.

• API key — create.roblox.com → Credentials → API Keys → Create: name, the prepared

scope list, IP allowlist, expiry. REPORT BACK confirms creation and scopes, and states that the key was stored in the tool's credential store — never pasted into chat, a script, or a memory file.

• Payout / DevEx questions — report eligibility state only. Payouts need 2-Step

Verification; DevEx additionally has membership, age, and a 30,000 Robux minimum, and its rate changes — the operator reads the live figure on the DevEx page rather than quoting one from us. The model never enters payment or tax details.

REPORT BACK: group id, final rank number per role, collaborator usernames added, and for keys, "created, scopes: <list>" — no secret material.

Verify & clear

Group: pcall Player:GetRankInGroup(groupId) on a known member in a playtest — the number must equal the role table's rank, since perks gate on the number and not the label. Place ownership: confirm the published place appears under the group in Creations, and that a pass created there attaches to the same owner (rbx-handoff-dashboard). API key: verify by making one scoped call succeed, never by echoing the key.

Then clear the manual steps pending: line and record the group id, role→rank map, and owning creator in that game's projects.md block. Ownership facts are per-game and never transfer; a preference like "always group-owned" belongs in preferences.md instead (MEMORY-PROTOCOL.md).