bring-grok

Logs local and free model failures to a markdown file for future Grok escalation decisions.

Updated Sep 20, 2026
One-click install
npx skills add https://github.com/GreenyZA/neo-light --skill bring-grok-greenyza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bring-grok
Source: https://github.com/GreenyZA/neo-light/tree/main/.grok-home/skills/bring-grok
Command: npx skills add https://github.com/GreenyZA/neo-light --skill bring-grok-greenyza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running agent workloads on local (llama.cpp, Vulkan, Ollama) or free cloud models (OpenRouter free, MiniMax), some tasks fail on quality, context length, or tool calling. Without a record of these failures, there is no evidence to decide when paying for a premium model like SuperGrok is justified. ## Core Features & Use Cases - Failure Logging: Appends a structured row (Date, Task, What failed, Lane tried, Why Grok would help) to a when-grok.md file whenever a turn fails on local or free tiers. - Escalation Evidence: Builds a real-world brief over time that shows exactly which task categories justify premium model spend. - Use Case: A coding task fails on a 3B local model due to context limits. The Skill logs the failure row, and after enough rows accumulate, the team has concrete data to write the Grok usage playbook. ## Quick Start Tell the agent to log this failed turn with bring-grok, noting what failed and which lane was tried.

Frequently Asked Questions about bring-grok

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

FAQPage Schema
How do I track when local LLMs fail on agent tasks?▼

Log each failed turn as a row in a markdown table with the date, task, failure reason, and lane tried. This Skill appends that row to a when-grok.md file whenever local or free models cannot finish a task.

When should I escalate from free models to a paid model like Grok?▼

Escalate only after real failure rows accumulate showing repeated quality, context, or tool-calling failures on local and free lanes. This Skill builds that evidence file instead of guessing when premium spend is worth it.

Does this Skill call the SuperGrok API directly?▼

No. The Skill explicitly does not call SuperGrok from this environment. It only records failure evidence so a human can later decide when bringing in Grok is justified.

What information is recorded for each model failure?▼

Each row records the date, the task attempted, what failed, which lane was tried (vulkan, ollama, minimax, or openrouter-free), and why Grok would help. No cost estimates or full prompt dumps are stored.

What are the limitations of logging failures to a markdown file?▼

Markdown logging requires manual review to spot patterns and does not automate escalation decisions. It suits small teams building evidence before committing to paid model routing rules.