arcplume

name	arcplume
description	Arcplume runs Grok through the Grok Build CLI's own OAuth-authenticated session (grok login) for image generation, with strict preflight validation, secret-safe handling, and headless CLI-driven execution -- no separate XAI_API_KEY billing. Video falls back to the billed xAI API. USE WHEN a user wants to generate an image via a locally logged-in Grok Build CLI session, e.g. 'generate an image with grok', 'use grok build', or 'use my logged-in grok session'.
cluster	media-gen
version	1.1.0
origin	craft-agent workspace
displayName	🪽 Arcplume — Grok Build CLI Session
emoji	🪽
homepage	https://skills.sh
license	MIT

🪽 Arcplume — Grok Build CLI Session

Use this skill when the user explicitly wants Grok via the locally authenticated Grok Build CLI session and CLI-driven execution.

When to trigger

Trigger on prompts like:

• "use grok build to generate an image"
• "generate an image with grok"
• "run the grok CLI"
• "use my logged-in grok session"

Do not auto-trigger for generic “use Grok API” requests unless the user asks for the CLI/logged-in-session mode.

Default behavior

1. Validate local prerequisites (grok available)
2. Verify the session is logged in (scripts/preflight.sh)
3. Execute via CLI-driven headless image generation path
4. Keep outputs concise and never expose secrets

Auth resolution order (strict)

1. Check the grok binary is present on PATH
2. Check that a logged-in session exists (Grok Build CLI manages its own OAuth tokens; this skill does not resolve or read any env vars or cookie files)

If either check fails, stop and return a precise remediation message.

Mandatory preflight (must pass)

command -v grok && grok --version

bash scripts/preflight.sh

If preflight fails, do not attempt Grok execution. Explain exactly which layer failed:

• binary missing
• session not logged in
• session invalid/expired

Execution path

Primary: CLI-driven headless image generation (recommended)

Drive the already-authenticated grok binary directly:

1. Run scripts/generate-image.sh --prompt "<text>" --out "<path>" (optional --max-turns)
2. This invokes grok headlessly (single-turn, JSON output) with a system-prompt override that forces use of Grok's real built-in image-generation tool, not a hand-drawn approximation
3. The script locates the resulting image file and copies it to the requested --out path
4. Return the resolved output path + a brief summary

This path is default because it relies on the CLI's own maintained OAuth session rather than any credential this skill would otherwise have to manage.