ecosystem-layering

Organizes multi-agent AI coding environments into canonical, runtime, and librarian planes to prevent cross-contamination.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill ecosystem-layering-avatar-arts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecosystem-layering
Source: https://github.com/AvaTar-ArTs/.Agent-skills/tree/main/skills/autonomous-ai-agents/ecosystem-layering
Command: npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill ecosystem-layering-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple AI coding agents (Codex, Cursor, Cline, Copilot, Gemini CLI, etc.) share a home directory, they recursively load each other's SKILL.md and AGENTS.md files, causing silent tool-name mismatches and wrong behavior. This Skill provides a governance pattern that isolates each agent while keeping skills shareable. ## Core Features & Use Cases - Three-Plane Governance Model: Separates skills into a canonical source-of-truth plane, per-agent runtime planes, and a librarian documentation plane with clear edit rules. - Adaptation Pipeline: Translates tool names, paths, and conventions (e.g., Task → delegate_task, Bash → terminal) when porting skills between platforms, with a Python adaptation script template. - Contamination Auditing: Provides shell commands to inventory every SKILL.md and AGENTS.md on disk, detect foreign-directory loads, and verify runtime scoping. - Use Case: You install Cline alongside Codex and notice Cline referencing tools it doesn't have. Use this Skill to scope Cline to ~/.cline/skills/, adapt your canonical skills with correct tool names, and build an ecosystem map to track drift. ## Quick Start Audit my home directory for all SKILL.md files and help me set up the three-plane model so each of my AI coding agents only loads skills from its own directory.

Frequently Asked Questions about ecosystem-layering

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

FAQPage Schema
How do I stop AI coding agents from loading each other's skills?

Scope each agent to load only from its own directory, such as ~/.cline/skills/ for Cline or ~/.codex/skills/ for Codex. Maintain a single canonical skills directory and adapt skills into each runtime rather than copying them raw.

How do I share a SKILL.md between Codex and Cline?

Never copy it raw, because tool names differ between platforms. Run it through an adaptation script that maps tool names, for example Task to spawn_agent, Bash to run_commands, and WebFetch to fetch_web_content, then place the adapted copy in the target agent's directory.

Why does my agent reference tools it doesn't have?

The agent loaded a skill written for a different platform, since most agents recursively search the home directory for SKILL.md files. The skill's instructions get followed with wrong tool names, causing silent wrong behavior rather than explicit errors.

Can I use symlinks to share skills between agents?

No. Symlinks deliver raw content without adaptation, so a symlinked Codex skill would expose Codex tool names to another agent. Always adapt skills into each runtime directory instead of linking.

When is ecosystem layering not needed?

Skip it for single-agent setups, fully containerized agents that do not share a home directory, or teams where each developer uses exactly one platform. The cross-contamination problem only exists when multiple agents share $HOME.