ask-claude
Ask Claude via local CLI and capture a reusable artifact
Best use case
ask-claude is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Ask Claude via local CLI and capture a reusable artifact
Teams using ask-claude should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ask-claude/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ask-claude Compares
| Feature / Agent | ask-claude | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Ask Claude via local CLI and capture a reusable artifact
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Ask Claude (Local CLI)
Use the locally installed Claude CLI as a direct external advisor for focused questions, reviews, or second opinions.
## Usage
```bash
/ask-claude <question or task>
```
## Routing
### Preferred: Local CLI execution
Run Claude through the canonical OMX CLI command path (no MCP routing):
```bash
omx ask claude "{{ARGUMENTS}}"
```
Exact non-interactive Claude CLI command from `claude --help`:
```bash
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.
### Missing binary behavior
If `claude` is not found, do **not** switch to MCP.
Instead:
1. Explain that local Claude CLI is required for this skill.
2. Ask the user to install/configure Claude CLI.
3. Provide a quick verification command:
```bash
claude --version
```
## Artifact requirement
After local execution, save a markdown artifact to:
```text
.omx/artifacts/claude-<slug>-<timestamp>.md
```
Minimum artifact sections:
1. Original user task
2. Final prompt sent to Claude CLI
3. Claude output (raw)
4. Concise summary
5. Action items / next steps
Task: {{ARGUMENTS}}Related Skills
worker
Team worker protocol (ACK, mailbox, task lifecycle) for tmux-based OMX teams
web-clone
URL-driven website cloning with visual + functional verification
visual-verdict
Structured visual QA verdict for screenshot-to-reference comparisons
ultrawork
Parallel execution engine for high-throughput task completion
ultraqa
QA cycling workflow - test, verify, fix, repeat until goal met
trace
Show agent flow trace timeline and summary
team
N coordinated agents on shared task list using tmux-based orchestration
tdd
Test-Driven Development enforcement skill - write tests first, always
swarm
N coordinated agents on shared task list (compatibility facade over team)
skill
Manage local skills - list, add, remove, search, edit, setup wizard
ralplan
Alias for $plan --consensus
ralph
Self-referential loop until task completion with architect verification