delegation-bridge

Delegate file I/O and routine tasks to Gemini Flash via MCP server.

2|3|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/mkalhitti-cloud/universal-or-strategy --skill delegation-bridge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delegation-bridge
Source: https://github.com/mkalhitti-cloud/universal-or-strategy/tree/main/.agent/skills/delegation-bridge
Command: npx skills add https://github.com/mkalhitti-cloud/universal-or-strategy --skill delegation-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables universal delegation of file I/O and routine tasks to the cheapest execution layer (Gemini Flash) via the MCP server, reducing operational costs across AI models while preserving AI-agnostic compatibility.

Core Features & Use Cases

  • Universal cost optimization: Route file I/O, deployment, logging, and context updates to Gemini Flash to minimize per-task expense.
  • AI-agnostic delegation: Works with Claude, Gemini, Grok, and other models that support MCP delegation.
  • Operational continuity: Maintains cross-IDE portability by updating shared state files under .agent/state and .agent/PROJECT_STATE.md.

Quick Start

Initiate a simple delegation task: read a small text file from the project root and verify the results via the delegated execution path.

Frequently Asked Questions about delegation-bridge

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

FAQPage Schema
How does delegating file I/O to a cheaper AI model reduce MCP deployment costs?

Delegating file I/O to Gemini Flash via an MCP server reduces deployment costs by routing routine operations to the cheapest execution layer. This preserves complex code logic processing with the current AI while minimizing per-task expenses.

What is universal AI delegation for routine file operations and deployment tasks?

Universal AI delegation is routing file I/O, documentation, and context tracking to a cheaper model like Gemini Flash. It enforces mandatory delegation for routine analysis while keeping code logic with the primary AI across multiple IDEs.

Can I use MCP delegation for cost optimization across different IDEs and AI models?

Yes, MCP delegation works across Claude, Gemini, Grok, and other models supporting it. It maintains cross-IDE portability by updating shared state files in .agent/state and .agent/PROJECT_STATE.md.

What's the best way to maintain operational continuity when switching between AI models?

The best way to maintain operational continuity is updating shared state files under .agent/state and .agent/PROJECT_STATE.md. This configuration ensures cross-IDE portability and tracks context across different AI models.

Why should I delegate routine analysis instead of keeping it with my current AI?

You should delegate routine analysis to enforce cost optimization and reduce operational expenses. The delegation bridge configuration preserves code logic with the current AI while routing file operations to the cheapest execution layer.

Do I need specific configuration files to enable cross-AI deployment delegation?

Yes, you need the delegation bridge configuration in .agent/config/ai_capabilities.json. This file enables universal delegation of file I/O and routine tasks to the cheapest execution layer via the MCP server.