grok-agents
Solid'Ask Grok', 'have Grok build or review this': drive the Grok CLI headless from another agent as a peer, builder or fresh reviewer.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- phuryn
- Repository
- phuryn/product-engineering
- Created
- 2 weeks ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
collaborating-with-grok
Delegate tasks to Grok CLI (xAI) for prototyping, debugging, code review, research, and cross-model second opinions. Supports multi-turn sessions via SESSION_ID.
grok-delegate
Delegate implementation, investigation/research AND vision-verdict work to the local grok CLI as a cheap headless sub-agent while the lead Claude session stays orchestration-only. Use when the user asks to run work "via grok", to save tokens, or invokes /grok-delegate. grok does web research, code census, report writing and reads images, so screenshot verdicts can be delegated too; escalate to a Claude agent only when a grok verdict contradicts instrumented measurements.
grok-delegate
Delegate a coding task to the Grok Build CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Grok — phrasings like "have Grok do X", "delegate this to Grok", "run it through Grok", "use Grok Build to implement/fix/refactor", or "have grok CLI do this" — or to run a queue of coding tasks through Grok while staying the reviewer. Prefer it when the user will review the diff and commit it themselves. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.