Keep · astra-grok SKILL.md

Computer-use 3D artist (GUI drive)

WhenUse when Blender MCP (or engine MCP) is unavailable and the job still needs real DCC progress: menus, outliner, material panels, render settings, save/export dialogs. Also use for one-off UI paths MCP does not expose.

StopNarrow steps only — one menu path or panel action per beat; no "finish the whole scene" mega-clicks. Stop immediately on auth, license, login, store, or payment walls. Report the wall; do not try to bypass. Do not click through OS security dialogs that grant broad permissions without human go. Prefer MCP when it reconnects; do not keep GUI-driving out of habit.

Steps

Confirm MCP is unavailable (or insufficient for this UI path). Note why in the run log.
Launch the DCC via desktop if needed. Wait for idle UI. Screenshot the starting state.
Execute a short, named micro-plan (≤8 GUI steps), e.g. "set camera FOV", "assign principled base color", "export glTF".
After each risky step (delete, apply, export overwrite): Screenshot and verify.
Wait for renders/compiles with explicit idle checks (progress bar gone, button re-enabled) — do not click early.
Save project file. Export if that was the goal. Capture a closing Screenshot.
If blocked by license/auth: stop, attach screenshot of the wall, hand back to human.
Summarize clicks taken, files touched, and next MCP-eligible steps.

Oven

Default: Grok Bot tools — GenerateImage / computerUse / browserUse / Shell / Blender MCP if connected / Screenshot. (Swap this one line for Astra / Fable / Claude.)

Done when

The named micro-plan is complete or cleanly stopped on a wall.
Project saved; exports present if requested.
Screenshot trail covers start, mid checkpoints, and end (or wall).
Run log says why GUI was used instead of MCP.

Cross-model

Recipe is fixed: GUI only when MCP cannot, narrow micro-plans, stop on walls, screenshot trail. Only the OVEN line swaps — computerUse/desktop automation maps to the host's desktop tool; stop lines and micro-plan discipline stay the same on Astra, Grok Bot, Fable, or Claude.

LoadOVEN: Default: Grok Bot tools — GenerateImage / computerUse / browserUse / Shell / Blender MCP if connected / Screenshot. (Swap this one line for Astra / Fable / Claude.) Done when: - The named micro-plan is complete or cleanly stopped on a wall. - Project saved; exports present if requested. - Screenshot trail covers start, mid checkpoints, and end (or wall). - Run log says why GUI was used inste

SourceAstra skills reworked for Grok Bot

Copy SKILL.mdRaw SKILL.md

---
name: "Computer-use 3D artist (GUI drive)"
description: "Use when Blender/Unreal/Unity must be driven via desktop GUI because MCP is unavailable."
---

# Computer-use 3D artist (GUI drive)

## When
Use when Blender MCP (or engine MCP) is unavailable and the job still needs real DCC progress: menus, outliner, material panels, render settings, save/export dialogs. Also use for one-off UI paths MCP does not expose.

## Stop
- Narrow steps only — one menu path or panel action per beat; no "finish the whole scene" mega-clicks.
- Stop immediately on auth, license, login, store, or payment walls. Report the wall; do not try to bypass.
- Do not click through OS security dialogs that grant broad permissions without human go.
- Prefer MCP when it reconnects; do not keep GUI-driving out of habit.

## OVEN
Default: Grok Bot tools — GenerateImage / computerUse / browserUse / Shell / Blender MCP if connected / Screenshot. (Swap this one line for Astra / Fable / Claude.)

## Steps
1. Confirm MCP is unavailable (or insufficient for this UI path). Note why in the run log.
2. Launch the DCC via desktop if needed. Wait for idle UI. Screenshot the starting state.
3. Execute a short, named micro-plan (≤8 GUI steps), e.g. "set camera FOV", "assign principled base color", "export glTF".
4. After each risky step (delete, apply, export overwrite): Screenshot and verify.
5. Wait for renders/compiles with explicit idle checks (progress bar gone, button re-enabled) — do not click early.
6. Save project file. Export if that was the goal. Capture a closing Screenshot.
7. If blocked by license/auth: stop, attach screenshot of the wall, hand back to human.
8. Summarize clicks taken, files touched, and next MCP-eligible steps.

## Done when
- The named micro-plan is complete or cleanly stopped on a wall.
- Project saved; exports present if requested.
- Screenshot trail covers start, mid checkpoints, and end (or wall).
- Run log says why GUI was used instead of MCP.

## Cross-model
Recipe is fixed: GUI only when MCP cannot, narrow micro-plans, stop on walls, screenshot trail. Only the OVEN line swaps — computerUse/desktop automation maps to the host's desktop tool; stop lines and micro-plan discipline stay the same on Astra, Grok Bot, Fable, or Claude.