Marketplace for trusted AI agent skills

Run multi-provider coding-agent sessions with OpenClaude

Skill Detail

Run multi-provider coding-agent sessions with OpenClaude

Use OpenClaude when a repository task needs one terminal-first coding-agent workflow that can switch across cloud, local, Codex OAuth, MCP, slash commands, file tools, and background sessions.

Developer ToolsMulti-Framework
Developer Tools Multi-Framework Security Reviewed
⭐ 29.5k GitHub stars ⬇ 34.8k/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill run-multi-provider-coding-agent-sessions-with-openclaude Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
View source Documentation
At a glance
Tools required
Node.js 22+, npm, ripgrep recommended, provider API key or local model backend, optional MCP servers
Install & setup
npm install -g @gitlawb/openclaude@latest, then run openclaude and use /provider for guided provider setup or pass provider environment variables explicitly.
Author
Gitlawb
Publisher
Open Source Project
Last updated
Jun 29, 2026
Quick brief

Use OpenClaude when an operator needs a terminal coding-agent workflow that keeps provider setup, model selection, file tools, bash, agents, MCP, slash commands, streaming output, session resume, and background task runs inside one repeatable CLI. The upstream README documents OpenAI-compatible APIs, Gemini, GitHub Models, Codex OAuth, Codex, Ollama, Atomic Chat, MCP, agents, tasks, file tools, grep/glob, slash commands, background sessions, resume, and fork behavior.

How it works

What this skill actually does

Invoke this instead of using a provider’s normal product when the work should happen inside a repository with repeatable terminal controls, saved provider profiles, local or cloud model choice, and reviewable coding-agent sessions. The scope boundary is the coding-agent CLI run: install OpenClaude, configure a provider profile or environment, start or resume a session, run file/tool-backed coding work, and inspect changes. It is not a generic model provider listing or a broad SDK card.

Inputs and prerequisites: Node.js 22+, npm, ripgrep recommended, provider API key or local model backend, optional MCP servers.

Setup notes: npm install -g @gitlawb/openclaude@latest, then run openclaude and use /provider for guided provider setup or pass provider environment variables explicitly.

Source and verification boundary: use https://openclaude.gitlawb.com as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.