skills.rest
aashahin
aashahinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

kimi-grok-delegate

Delegate bounded implementation, debugging, and review tasks from Kimi to the Grok Build CLI.

Updated Jun 22, 2026
Search Tags:#code review#bash#delegation#agent orchestration#git worktree#parallel workers#grok cli
One-click install
npx skills add https://github.com/aashahin/ai-skills --skill kimi-grok-delegate-aashahin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kimi-grok-delegate
Source: https://github.com/aashahin/ai-skills/tree/main/kimi-grok-delegate
Command: npx skills add https://github.com/aashahin/ai-skills --skill kimi-grok-delegate-aashahin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires grok, jq, setsid, flock, pgrep, git, sha256sum, and includes scripts (resource) components.

What problem does it solve? Delegating coding work to an external CLI agent risks unbounded runs, leaked prompts, dirty repositories, and orphaned processes. This Skill wraps the Grok Build CLI in a hardened runner so Kimi can hand off implementation, debugging, review, research, and testing tasks with enforced deadlines, isolated Git worktrees, and verified completion. ## Core Features & Use Cases - Hardened execution wrapper: scripts/grok-run.sh enforces prompt-file privacy (mode 600), wall-clock deadlines, turn caps, output size limits, heartbeats, and process-group cleanup with a watchdog. - Isolated write modes: Run read-only reviews, create unique wrapper-managed Git worktrees per task, or write into an existing linked worktree with duplicate-writer locking. - Performance profiles: Choose safe (no memory/subagents, 20 turns, 30 minutes) for small reviews or heavy (native capabilities, 40 turns, 60 minutes) for implementation and research. - Verified acceptance: Runs are accepted only on zero exit, matching session ID, validated EndTurn JSON, and no surviving descendant processes. - Use Case: Ask Kimi to fix a bug in a feature branch; Kimi writes a standalone prompt file, launches one bounded Grok worker in a fresh worktree, inspects the resulting diff, runs independent tests, and merges only verified changes. ## Quick Start Ask Kimi to delegate a specific coding task to Grok, for example: "Delegate to Grok the implementation of input validation in src/api/handler.ts on a new worktree, then verify the diff and run the test suite."

Frequently Asked Questions about kimi-grok-delegate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate a coding task from Kimi to Grok?▼

Write a standalone prompt containing the repository path, branch, files, constraints, and verification commands into a mode-600 file, then run scripts/grok-run.sh with --prompt-file. Use --worktree for isolated writes or --existing-worktree inside a selected linked worktree.

What is the difference between safe and heavy performance modes?▼

Safe mode disables Grok memory and subagents with defaults of 20 turns and a 30-minute deadline, suiting small or privacy-sensitive reviews. Heavy mode preserves native Grok capabilities with 40 turns and a 60-minute deadline for implementation, debugging, and research.

Can multiple Grok workers run in parallel on the same repository?▼

Yes, invoke --worktree once per independent task and the wrapper creates a unique linked Git worktree for each, allowing parallel isolated workers. Two writers cannot share one checkout because the wrapper rejects duplicate writers with a lock.

Why was my delegated Grok run rejected as failed?▼

A run fails on nonzero exit, timeout, output-limit breach, missing metadata, mismatched session ID, non-EndTurn stop reason, or surviving descendant processes. Partial JSON output is diagnostic only and never accepted as a completed result.

Can I run native Grok workflows through this wrapper?▼

No, saved .grok/workflows/*.rhai runs are background jobs owned by a persistent Grok session and a one-shot headless process can exit before completion. Run native workflows in the Grok TUI with /workflow and monitor them with /workflows instead.

Related Skills

Explore More Software Engineering Skills→
tutur3ututur3u
53

using-git-worktrees

Create isolated git worktrees for feature development with safety checks.

Official
Basic
novuhqnovuhq
39.7k

nv-worktree-cleanup

Audits git worktrees and removes merged, missing, or confirmed stale entries with their branches.

Official
Intermediate
Smooth-OperationSmooth-Operation

subagent-driven-development

Assign each task to a fresh subagent and require review between tasks.

Official
Advanced
Lento47Lento47
1

grok

Delegate coding tasks to the xAI Grok Build CLI via headless or interactive sessions.

Community
Intermediate