Egonex-AI Platform-Specific Installation Paths: Supported Platforms for Understand-Anything

The Egonex-AI Understand-Anything installer supports 13 AI-assistant platforms, mapping each to a specific target directory via a pipe-separated table in install.sh that defines whether skills are linked individually or as a folder.

The Understand-Anything repository by Egonex-AI provides a unified skill set for multiple AI coding assistants. The installation script automatically determines where to place skill symlinks based on platform-specific installation paths defined in the source code, ensuring compatibility with each assistant's expected directory structure.

Supported Platforms and Target Directories

The platforms_table function in install.sh (lines 31-45) defines a mapping table that records where each platform expects its skills. Each row follows the format:

<platform-id>|<target-directory>|<link-style>

The installer recognizes 13 supported platforms, each with a distinct installation path in the user's home directory.

Per-Skill Link Platforms

These platforms create individual symlinks for each skill file:

• gemini: $HOME/.agents/skills
• codex: $HOME/.agents/skills
• opencode: $HOME/.agents/skills
• pi: $HOME/.agents/skills
• vibe: $HOME/.vibe/skills
• vscode: $HOME/.copilot/skills
• trae: $HOME/.trae/skills
• nanobot: $HOME/.nanobot/workspace/skills
• kiro: $HOME/.kiro/skills

Folder Link Platforms

These platforms create a single symlink pointing to the entire skills/ directory:

• openclaw: $HOME/.openclaw/skills
• antigravity: $HOME/.gemini/antigravity/skills
• hermes: $HOME/.hermes/skills
• cline: $HOME/.cline/skills

How install.sh Resolves Platform Paths

When you run ./install.sh <platform>, the script invokes the resolve_platform function to parse the table. According to the source code in install.sh, the function extracts the target directory using cut -d'|' -f2 and the link style using cut -d'|' -f3.

The link_skills function then creates the appropriate symlinks based on the extracted style:

• per-skill: Iterates through individual skill files and creates symlinks in the target directory
• folder: Creates one symlink pointing the platform's skills directory to the repository's skills/ folder

Installing and Managing Skills by Platform

To deploy Understand-Anything skills for a specific AI assistant, execute the installation script with the platform identifier.

List available platforms from the command line:

./install.sh --help | grep -A1 "Supported platforms"

Install the skill set for a specific platform (e.g., vscode):

./install.sh vscode

This command clones the repository if needed, links each skill into $HOME/.copilot/skills, and creates a universal plugin root at $HOME/.understand-anything-plugin.

Uninstall the skill links for a platform:

./install.sh --uninstall vscode

This removes the symlinks from $HOME/.copilot/skills while leaving the cloned repository untouched, as other platforms may still reference it.

Summary

• Egonex-AI Understand-Anything supports 13 AI-assistant platforms through a centralized mapping table in install.sh.
• The platform table at lines 31-45 defines each platform's ID, target directory, and link style using pipe-separated fields.
• Per-skill linking creates individual symlinks for each skill file, while folder linking creates a single symlink to the entire skills/ directory.
• The resolve_platform function parses this table to determine where to place symlinks for the requested platform.
• Installation and uninstallation are handled via ./install.sh <platform> and ./install.sh --uninstall <platform> respectively.

Frequently Asked Questions

What AI-assistant platforms does Egonex-AI support?

Egonex-AI supports 13 platforms including Gemini, Codex, OpenCode, Pi, OpenClaw, Antigravity, Vibe, VSCode (Copilot), Hermes, Cline, Trae, Nanobot, and Kiro. Each maps to a specific subdirectory in the user's home folder, such as $HOME/.agents/skills for Gemini and Codex, or $HOME/.copilot/skills for VSCode.

How do I uninstall skills for a specific platform without affecting others?

Run ./install.sh --uninstall <platform-id> (e.g., ./install.sh --uninstall vscode). This executes the uninstall logic in install.sh that removes only the symlinks from that platform's target directory, leaving the underlying repository intact so other platforms can continue using it.

What is the difference between per-skill and folder link styles?

Per-skill creates individual symlinks for each file in the skills/ directory, allowing platforms to see specific skill files directly. Folder creates a single symlink pointing the platform's expected skills directory to the entire skills/ folder, which is used by platforms like OpenClaw and Cline that expect a directory reference rather than individual files.

Where is the platform configuration defined in the source code?

The configuration is defined in the platforms_table function within install.sh at lines 31-45. This function outputs the pipe-separated table that the resolve_platform function parses to determine the correct target directory and linking method for each supported platform.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}