etkm-ai-roles

Define roles and routing logic for ETKM's five-AI stack.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/easttxkravmaga/Claude --skill etkm-ai-roles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: etkm-ai-roles
Source: https://github.com/easttxkravmaga/Claude/tree/main/archive/etkm-ai-roles
Command: npx skills add https://github.com/easttxkravmaga/Claude --skill etkm-ai-roles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify ownership and routing across ETKM's five-AI stack to prevent ambiguity in task assignment.

Core Features & Use Cases

  • Defines roles for Claude, Cowork, Claude Code, Manus, and ChatGPT/Gemini to ensure predictable execution lanes.
  • Provides a task-routing decision tree and session-opening guidelines to coordinate multi-AI workflows.
  • Supports onboarding and ongoing coordination for multi-AI projects, handoffs, and real-time task routing.

Quick Start

Load the ETKM five-AI coordination model and start routing a multi-AI task according to the defined lanes.

Frequently Asked Questions about etkm-ai-roles

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

FAQPage Schema
How do I coordinate tasks and handoffs across multiple AI agents?

Multi-AI task coordination requires defining role responsibilities and session behavior for each agent to prevent ambiguity. This skill provides a routing decision tree to assign tasks predictably across Claude, Cowork, Claude Code, Manus, and ChatGPT/Gemini.

What is a multi-AI workflow routing model and when do I need one?

A multi-AI workflow routing model specifies task-routing logic and execution lanes for different AI tools. You need one when managing multi-AI projects where handoffs and real-time task routing between models like Claude and Manus risk causing ownership ambiguity.

How do I set up session state for a multi-AI project handoff?

Setting up session state for a multi-AI project handoff involves loading a canonical coordination protocol that specifies session-opening guidelines. This establishes repeatable workflows and clear task-routing logic before engaging Claude, Cowork, or ChatGPT/Gemini.

Can I use this coordination protocol to onboard new agents into an existing AI stack?

Yes, you can use this coordination protocol for onboarding new agents into an existing AI stack. It defines role responsibilities and session behavior to support ongoing coordination for multi-AI projects, ensuring predictable execution lanes.

What's the best way to route tasks between Claude Code and Manus?

The best way to route tasks between Claude Code and Manus is applying a task-routing decision tree. This specifies role responsibilities for each tool, preventing task assignment ambiguity and ensuring predictable execution lanes across the stack.

Why does task ownership become ambiguous when using multiple AI tools together?

Task ownership becomes ambiguous when using multiple AI tools together without a canonical coordination protocol. Without defined role responsibilities and session behavior, task-routing logic fails, causing overlap and unclear handoffs across the five-AI stack.