/dev-ask
Advisory router — query Claude, Codex, or Gemini for a quick second opinion. Experimental — only Claude is guaranteed available; other models require dev-mcp-setup configuration.
$ npx -y skills add evolution-foundation/evo-nexus --skill dev-ask --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/dev-ask
Context preview
The summary Claude sees to decide when to auto-load this skill.
Advisory router — query Claude, Codex, or Gemini for a quick second opinion. Experimental — only Claude is guaranteed available; other models require dev-mcp-setup configuration.
SKILL.md
dev-ask.SKILL.mdname: dev-ask
description: Advisory router — query Claude, Codex, or Gemini for a quick second opinion. Experimental — only Claude is guaranteed available; other models require dev-mcp-setup configuration.
Dev Ask
Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.
**EXPERIMENTAL.** Quick advisory query to a specific LLM (Claude, Codex, Gemini) for a second opinion. Different from `dev-ccg` which runs all three in parallel — `dev-ask` is single-shot.
Use When
- You want a fast second opinion from a specific model
- Comparing how different models approach the same problem
- Validating Claude's answer against another model
Do Not Use When
- Need consensus across models → use `dev-ccg`
- Just need an answer → ask the active session directly
- Codex/Gemini APIs not configured → only Claude available, fall back
Workflow
1. **Pick the target model:** `claude` | `codex` | `gemini` 2. **Format the question** model-agnostically 3. **Send** via the appropriate API 4. **Return** the answer with the model's name attached 5. Optional: save to `workspace/development/research/[C]ask-{topic}-{date}.md`
Configuration
| Model | Required setup | |---|---| | Claude | Native — always available | | Codex | OpenAI API key configured via `dev-mcp-setup` | | Gemini | Google API key configured via `dev-mcp-setup` |
If a target model isn't configured, the skill warns: > "{model} is not configured. Only Claude is currently available. Configure via `dev-mcp-setup` or use `dev-ccg` to compare available models."
Output Format
## Ask — {target model}
### Question
{question}
### Answer (from {model})
{answer}
### Note
[Any caveats — model version, response time, confidence, etc.]Pairs With
- `dev-ccg` (multi-model parallel)
- `dev-mcp-setup` (configures non-Claude APIs)
- `@apex-architect` (often the consumer of multi-model perspectives)
Read more
name: dev-ask description: Advisory router — query Claude, Codex, or Gemini for a quick second opinion. Experimental — only Claude is guaranteed available; other models require dev-mcp-setup configuration.
Dev Ask
Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.
**EXPERIMENTAL.** Quick advisory query to a specific LLM (Claude, Codex, Gemini) for a second opinion. Different from `dev-ccg` which runs all three in parallel — `dev-ask` is single-shot.
Use When
- You want a fast second opinion from a specific model
- Comparing how different models approach the same problem
- Validating Claude's answer against another model
Do Not Use When
- Need consensus across models → use `dev-ccg`
- Just need an answer → ask the active session directly
- Codex/Gemini APIs not configured → only Claude available, fall back
Workflow
1. **Pick the target model:** `claude` | `codex` | `gemini` 2. **Format the question** model-agnostically 3. **Send** via the appropriate API 4. **Return** the answer with the model's name attached 5. Optional: save to `workspace/development/research/[C]ask-{topic}-{date}.md`
Configuration
| Model | Required setup | |---|---| | Claude | Native — always available | | Codex | OpenAI API key configured via `dev-mcp-setup` | | Gemini | Google API key configured via `dev-mcp-setup` |
If a target model isn't configured, the skill warns: > "{model} is not configured. Only Claude is currently available. Configure via `dev-mcp-setup` or use `dev-ccg` to compare available models."
Output Format
## Ask — {target model}
### Question
{question}
### Answer (from {model})
{answer}
### Note
[Any caveats — model version, response time, confidence, etc.]Pairs With
- `dev-ccg` (multi-model parallel)
- `dev-mcp-setup` (configures non-Claude APIs)
- `@apex-architect` (often the consumer of multi-model perspectives)
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill

