菜单
Use when users need multi-provider image/video generation workflows in `<workspace-root>/grok-aurora-cli`, including running `grok make`, provider-specific `grok video` and image commands, tracking async tasks, stitching clips, and evaluating outputs with `grok eval`.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Standalone Speedrift-native planning and Workgraph compilation. PlanForge V2 uses a model-mediated planner persona, validated schema, critic pass, and Speedrift module/model assignment to produce an executable Workgraph with tests, evals, drift gates, and fix loops. Use directly when you need discovery, decomposition, or an end-to-end Speedrift execution graph.
Use when agents need Google Workspace access across Drive, Docs, Sheets, Calendar, Slides, Tasks, People, or related GWS services; choose the correct gws-account profile before using gws CLI or domain-specific gws-* skills. Do not use Python gspread/googleapiclient or custom OAuth. Use msgvault for email search/reading.
gws CLI shared reference. Use before any gws-* skill to choose the correct gws-account profile, avoid raw gws config drift, and apply shared Drive flags, auth checks, output formatting, and security rules.
Use when a local Pi agent needs administrator privileges, a password-protected command, or approval for global or ambiguous deletion
Workgraph-first drift-control autopilot (driftdriver + coredrift + optional specdrift/datadrift/depsdrift/uxdrift/therapydrift/yagnidrift/redrift) with optional Amplifier runtime integration. Use for start/resume, dependency-aware execution, and keeping code/spec/intent synced without hard blocks.
Use when managing projects, programs, initiatives, dependencies, schedules, Workboard/PAIA Program tasks, Linear/GitHub/Google/Folio work, cross-system planning, weekly operating reviews, stale work rescue, operational task decomposition, or research-backed planning for Braydon's work. Covers a model-mediated program panel, research/evidence discovery, model-authored records, HTML inspection packets, change plans, approval gates, and execution ledgers.
| name | grok-aurora-cli |
| description | Use when users need multi-provider image/video generation workflows in `<workspace-root>/grok-aurora-cli`, including running `grok make`, provider-specific `grok video` and image commands, tracking async tasks, stitching clips, and evaluating outputs with `grok eval`. |
Run the existing grok-aurora-cli project reliably and reproducibly. Prefer direct CLI commands over ad-hoc scripts, and produce concise run summaries with output paths, provider/model used, and any failures.
cd <workspace-root>/grok-aurora-clisource activate.shgrok --help../claude-agent-toolkit/skills/grok-aurora-cli/scripts/check-env.shgrok make for guided, interactive runs.grok video, grok fal-image, grok novita-image, grok venice-image, grok gemini-image, grok kling-image, grok banana).-o output/<name>.mp4).grok video-status for pending tasks.--fal, --novita, --kling, --seedance2, --veo) as needed.grok veo-4k for Veo upgrade flows.grok eval <image-paths...> with optional --reference to score identity/style consistency.grok stitch for chain assembly.grok log --errors for debugging.output/ with scenario-based subfolders.Use the smallest command that satisfies the request:
grok generate "..." or grok gemini-image ...grok fal-image ..., grok novita-image ..., grok venice-image ..., grok kie-image ..., grok banana ...grok video <prompt-file> -i <image> --provider <provider>grok makegrok eval ...grok log, grok clear-logPrefer prompt files under prompts/ for reproducibility rather than inline prompt text for long runs.
After each run, provide:
scripts/check-env.sh: Print provider key readiness and fail if no providers are configured.scripts/run-grok.sh: Run grok with project activation handled automatically.references/command-recipes.md: Common command templates for repeatable generation and evaluation.Use GUIDE.md in the CLI project as the authoritative command/options reference when a flag question is ambiguous.