agentskills.codes
AS

Ask Claude via local CLI and capture a reusable artifact

Install

mkdir -p .claude/skills/ask-claude-byonk19-svg && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13678" && unzip -o skill.zip -d .claude/skills/ask-claude-byonk19-svg && rm skill.zip

Installs to .claude/skills/ask-claude-byonk19-svg

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Ask Claude via local CLI and capture a reusable artifact
56 charsno explicit “when” trigger

About this skill

Ask Claude (Local CLI)

Use the locally installed Claude CLI as a direct external advisor for focused questions, reviews, or second opinions.

Usage

/ask-claude <question or task>

Routing

Preferred: Local CLI execution

Run Claude through the canonical OMX CLI command path (no MCP routing):

omx 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.

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:
claude --version

Artifact requirement

After local execution, save a markdown artifact to:

.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}}

Search skills

Search the agent skills registry