// Explains the current DOT Studio Act contract: participants, relations, subscriptions, actRules, safety, and publish-safe field boundaries. Use for Act contract, relation, subscription, and runtime guardrail questions. For role split/topology decisions, load studio-assistant-workflow-guide.
Lists the exact Studio Assistant apply_studio_actions mutation surface, field rules, ref ordering, and payload self-checks. Use before emitting or validating any Studio mutation tool call.
Helps design or revise Studio Performers with strong role focus, Tal/Dance/model choices, and Act participant readiness. Use for Performer creation, Performer updates, role design, and participant-quality decisions. For exact payload fields, load studio-assistant-action-surface-guide.
Explains DOT Studio navigation, UI vocabulary, Asset Library behavior, Stage vs thread terminology, and visible control names. Use for product-help questions. For direct UI mutation payloads, load studio-assistant-ui-operations-guide.
Tells the Studio Assistant how to open, reveal, inspect, hide, show, move, resize, and panel-toggle Studio UI surfaces through apply_studio_actions. Use for direct Studio UI manipulation requests.
Helps design performer teams, role splits, handoff patterns, and connected Act topology in DOT Studio. Use when the user wants a team, workflow, pipeline, role decomposition, or Act structure recommendation.
Helps the Studio Assistant design strong Tal content for agents. Use when deciding what belongs in Tal, how concise it should be, how to express persona and mental model, or how to propose a role-appropriate Tal before creating a Performer.
| name | studio-assistant-act-guide |
| description | Explains the current DOT Studio Act contract: participants, relations, subscriptions, actRules, safety, and publish-safe field boundaries. Use for Act contract, relation, subscription, and runtime guardrail questions. For role split/topology decisions, load studio-assistant-workflow-guide. |
| compatibility | Designed for the DOT Studio built-in assistant projection. |
Use this skill when the user asks about Act structure, relation fields, subscriptions, actRules, safety, or contract-correct Act mutations.
key plus Performer URNs, not workspace performerRef.between: [sourceKey, targetKey], direction, name, and description.one-way, relation order matters.messagesFrom, messageTags, callboardKeys, and eventTypes.eventTypes currently supports only runtime.idle.callboardKeys as the canonical field name.name, and non-empty description.source... and target... locator fields in assistant payloads, not legacy from... or to....research brief, review notes, or launch handoff.handoff, sync, or collaboration.actRules for durable whole-team behavior.description.safety.safety.threadTimeoutMs is a runtime limit, not a participant wake.messageTags and callboardKeys with concrete handoffs.wait_until condition names message_received, board_key_exists, wake_at, all_of, and any_of.wake_at is the scheduled self-wake condition name.timeout.idpermissionsmaxCallstimeoutsessionPolicystudio-assistant-action-surface-guide before emitting payloads.