clink-standalone

Bridge external AI CLIs without MCP server for isolated sessions.

7|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/VCnoC/clink-standalone --skill clink-standalone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clink-standalone
Source: https://github.com/VCnoC/clink-standalone/tree/main
Command: npx skills add https://github.com/VCnoC/clink-standalone --skill clink-standalone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standalone Clink Standalone provides a direct bridge to external AI CLIs (gemini, codex, claude) without requiring an MCP server, enabling isolated tool usage within conversations.

Core Features & Use Cases

  • Isolated CLI sessions with per-tool context
  • Role-based prompts and file reference capabilities
  • Cross-CLI orchestration for coding, planning, and reviews

Quick Start

Copy this skill into your Claude/Gemini/OpenAI Codex skills directory and start the bridge with the clink.py script.

Frequently Asked Questions about clink-standalone

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

FAQPage Schema
How do I use external AI CLIs like Gemini and Claude without an MCP server?▼

You can bridge external AI CLIs directly without an MCP server by using a Python script to enable isolated context and role-based usage across Gemini, Codex, and Claude. This approach supports multi-CLI orchestration and file references for cross-tool automation.

What is the best way to orchestrate multiple AI CLIs for coding and planning?▼

Orchestrating multiple AI CLIs for coding and planning is best handled through a direct bridge that supports cross-CLI orchestration with isolated sessions and per-tool context. This allows role-based prompts and file reference capabilities across different environments.

Do I need Python to run cross-tool automation for external AI CLIs?▼

Yes, you need Python 3.9+ and pydantic to run this cross-tool automation bridge. Additionally, the respective external AI CLIs (gemini, codex, claude) must be installed and authenticated on your system before initiating the bridge.

Can I maintain isolated context when using different AI CLIs in a single workflow?▼

Yes, you can maintain isolated context when using different AI CLIs by running isolated CLI sessions with per-tool context. This ensures role-based usage and prevents context bleed across Gemini, Codex, and Claude during multi-CLI orchestration.

What are the limitations of bridging AI CLIs directly without an MCP server?▼

A limitation of bridging AI CLIs directly without an MCP server is that it requires specific local dependencies, including Python 3.9+, pydantic, and pre-authenticated CLI installations. It operates as a standalone script rather than a persistent server-side integration.

Does direct CLI bridging support file references for AI code reviews?▼

Yes, direct CLI bridging supports file reference capabilities for AI code reviews. It allows you to pass file references directly to external AI CLIs within isolated sessions, enabling role-based prompts for coding, planning, and review tasks.