robo-engineer

Configure, theme, extend, and orchestrate the Robo Agent CLI and desktop app.

16|Updated Sep 22, 2026
One-click install
npx skills add https://github.com/igniteenow/robo --skill robo-engineer-igniteenow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: robo-engineer
Source: https://github.com/igniteenow/robo/tree/main/skills/autonomous-ai-agents/robo-engineer
Command: npx skills add https://github.com/igniteenow/robo --skill robo-engineer-igniteenow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Robo Agent is a provider-agnostic AI agent framework with many surfaces (CLI, TUI, desktop app, gateway, dashboard), and its breadth makes it hard to answer setup, configuration, theming, and multi-agent orchestration questions accurately without loading the right reference material. ## Core Features & Use Cases - Configuration & CLI guidance: Route questions to references covering CLI commands, slash commands, providers, config.yaml sections, toolsets, voice/STT/TTS, and security toggles. - Extension authoring: Build desktop UI plugins, TUI widgets, skins/themes, and pet mascots using bundled templates and SDK references. - Multi-agent orchestration: Spawn independent Robo processes in one-shot or interactive tmux PTY mode, coordinate parallel agents, and diagnose delegate_task concurrency behavior. - Use Case: A user wants a synthwave theme and a live clock widget in the TUI; the skill loads the themes and tui-widgets references, applies the skin via robo config set display.skin, and installs the clock widget from the bundled template. ## Quick Start Ask the agent to configure a Robo provider, create a custom skin, or spawn a background Robo agent for a long-running task, and it will load the matching reference file before answering.

Frequently Asked Questions about robo-engineer

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

FAQPage Schema
How do I spawn multiple Robo agents in parallel?▼

Use tmux to run each Robo process in its own session, since the interactive CLI requires a real terminal. Start with `tmux new-session -d -s agent1 'robo -w'`, send prompts with `tmux send-keys`, and read output with `tmux capture-pane`. For quick subtasks, prefer the delegate_task tool instead.

How do I create a custom theme or skin for Robo?▼

Copy the skin.yaml template into ~/.robo/skins/<name>.yaml, edit the palette, then apply it with `robo config set display.skin <name>`. Every surface repaints live within about a second. To tweak one color, edit the active skin with `robo skin set <key> <hex>` rather than forking the default.

Can Robo connect to MCP servers?▼

Yes, Robo has a built-in MCP client supporting stdio and HTTP transports configured under mcp_servers in config.yaml. Tools are auto-discovered at startup and registered with the prefix mcp_<server>_<tool>. The mcp Python package must be installed, and changes require a restart.

Why did delegate_task run fewer subagents than I configured?▼

Only three code paths cap a batch: a per-call hard reject, a per-turn truncator, and a cost-warning log that caps nothing. Check `robo config get delegation.max_concurrent_children` and grep agent.log for 'Truncated' or 'Too many tasks'; if neither fired, the model self-limited the batch.

Does Robo support providers other than OpenAI and Anthropic?▼

Yes, over 35 provider profiles ship as plugins, including OpenRouter, DeepSeek, Gemini, xAI, Kimi, local models via custom base_url, and OAuth providers like openai-codex. Multiple credentials per provider form a rotating pool, and fallback chains are configured with `robo fallback`.

Where do secrets and settings go in Robo configuration?▼

API keys and secrets belong only in ~/.robo/.env, while all non-credential settings go in ~/.robo/config.yaml. Never hand-edit config.yaml; use `robo config set KEY VAL` to avoid corrupting the file and breaking the live gateway.