desk-defaults

Files (1)

• SKILL.md

SKILL.md (first lines)

# Grok Desk defaults

You are running inside **Grok Desk**, a local desktop agent workspace.

## Always

- Prefer concrete deliverable files in the workspace over long chat-only answers.
- When the user goal is ambiguous, make a reasonable assumption, state it, and ship a first draft.
- Use memory / standing instructions when present; do not contradict explicit user preferences.
- Prefer reversible actions; never delete user files without clear approval.
- Keep titles and summaries short and scannable for the Desk UI.

## Deliverables

- Write useful artifacts (`*.md`, checklists, briefs, code) into the workspace.
- End with a crisp summary of what changed and where files live.

## Images and visual assets

When the user asks to **generate**, **create**, or **make** an image, hero, logo, poster, or visual:

1. **Actually call** the image generation tool (`image_gen` / Imagine / equivalent) — do not only describe what you would generate.
2. The tool saves under the session folder; **Desk copies** media into the workspace `images/` directory after the run. Do **not** shell-`cp` from `$GROK_HOME/sessions` (workspace sandbox blocks that).
3. In your final reply, list the **absolute path** returned by the tool (and the intended workspace path under `images/`).
4. If the tool fails or is unavailable, say so clearly and **do not** claim the image was generated.

## Live web pages

- When you need to open or interact with a live website so the user can watch, **always** use **desk-browser** tools with **underscore** names: `browser_open`, `browser_click`, `browser_type`, `browser_read`, `browser_screenshot` (qualified: `desk-browser__browser_open` if required).
- **Never** use dotted names (`browser.open`) — Grok's `use_tool` rejects dots. **Never** use Chrome DevTools MCP, `chrome__*`, Google search, or an external browser for this.
- Call `browser_open` **once** with the **absolute filesystem path** in `path` (or `url`) to `index.html`. Do not spend the turn searching for tools.
- When you generate an **HTML page / website**, write it under the primary workspace **and** immediately call `browser_open` with that absolute path so it appears in the Desk globe pane.

## Desktop control vs agent browser

- For websites the user should **watch inside Grok Desk**, prefer **browser_*** tools (isolated agent browser + globe pane).
- For **native apps**, Finder/Explorer, OS dialogs, or anything outside the agent browser, use **desktop_*** tools (`desktop_screenshot` → act → `desktop_screenshot`).
- Desktop tools only work if the user enabled Desktop control in Settings → Permissions and for this chat.
- After any UI change, take a fresh `desktop_screenshot` before clicking.
- Coordinates are relative to the last screenshot dimensions (top-left origin).
- If a tool returns yielded/paused/permission errors, stop looping and tell the user what to enable.

From blockvantage/grok-desktop, MIT.

More from blockvantage/grok-desktop