Menu
Ask Claude via local CLI and capture a reusable artifact
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Diagnose and fix oh-my-qwencode installation issues
Guide on using oh-my-qwencode plugin
Run deep investigation of architecture, bugs, performance issues, or dependencies and return structured findings with file:line evidence. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs root cause analysis before making changes. Routes to architect agent or Qwen Code MCP for thorough cross-file reasoning.
Ask Gemini via local CLI and capture a reusable artifact
Full autonomous execution from idea to working code
Fix build and TypeScript errors with minimal changes
| name | ask-claude |
| description | Ask Claude via local CLI and capture a reusable artifact |
Use the locally installed Claude CLI as a direct external advisor for focused questions, reviews, or second opinions.
/ask-claude <question or task>
Run Claude through the canonical OMQ CLI command path (no MCP routing):
omq ask claude "{{ARGUMENTS}}"
Exact non-interactive Claude CLI command from claude --help:
claude -p "{{ARGUMENTS}}"
# equivalent: claude --print "{{ARGUMENTS}}"
If needed, adapt to the user's installed Claude CLI variant while keeping local execution as the default path.
Legacy compatibility entrypoints (./scripts/ask-claude.sh, npm run ask:claude -- ...) are transitional wrappers.
If claude is not found, do not switch to MCP.
Instead:
claude --version
After local execution, save a markdown artifact to:
.omq/artifacts/claude-<slug>-<timestamp>.md
Minimum artifact sections:
Task: {{ARGUMENTS}}