ask-claude

Run Claude locally via the OMX CLI and save artifacts to .omx/artifacts.

1|Updated Mar 17, 2025
One-click install
npx skills add https://github.com/ozby/node-pubsub --skill ask-claude-ozby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-claude
Source: https://github.com/ozby/node-pubsub/tree/main/.codex/skills/ask-claude
Command: npx skills add https://github.com/ozby/node-pubsub --skill ask-claude-ozby

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Run Claude locally via the OMX CLI and capture a reusable artifact of the interaction for offline use and auditing.

Core Features & Use Cases

  • Local Claude CLI execution to bypass cloud routing and enable offline access.
  • Automatic artifact generation and storage to the repository at .omx/artifacts/claude-<slug>-<timestamp>.md.
  • Safe-guarded behavior when Claude CLI is not installed, including a clear user prompt to install it.

Quick Start

Run the local Claude CLI against a task and save a structured artifact.

Frequently Asked Questions about ask-claude

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

FAQPage Schema
How do I run Claude locally and save the interaction as an artifact?

To run Claude locally and save the interaction, use the OMX CLI to execute the Claude CLI binary and automatically store the output as a markdown artifact in the .omx/artifacts directory. This enables offline access and auditing.

What happens if the Claude CLI is not installed on my machine?

If the Claude CLI is not installed, the Skill enforces safe-guarded behavior by detecting the missing binary and providing a clear prompt instructing you to install it before proceeding with local execution.

Can I use local Claude execution for offline consultations without cloud routing?

Yes, local Claude execution via the OMX CLI bypasses cloud routing to enable offline access. It handles quick consultations and logs the interaction as a structured artifact for later review.

How are captured Claude artifacts named and stored in my repository?

Captured Claude artifacts are stored as markdown files in the .omx/artifacts directory, following the naming convention claude-<slug>-<timestamp>.md to ensure traceable and reusable interaction logs.

Do I need any specific dependencies to capture Claude insights locally?

You need the OMX CLI and the Claude CLI binary installed locally to capture insights. The Skill has no external package dependencies but strictly requires the local Claude CLI environment to function properly.