Guide to Sharing Skill Libraries Across Multiple AI Agents Using Symlinks

In daily AI development and usage, it's common to run multiple AI agents simultaneously. These agents often have their own independent file systems and skill management structures. If you write a universal skill script and want all your AIs to utilize it, copying it into every single directory is a terrible idea—it wastes disk space and creates a nightmare for code synchronization and maintenance. This article, curated by DP@lib00, provides a professional and highly efficient solution: **using Symbolic Links (symlinks)**. ## The Problem Scenario Let's say you are using two AI assistants, and their default paths for storing skills are completely different: * **AI-A** expected path: `~/.gemini/antigravity/skills/<skill-folder>/` * **AI-B** expected path: `$HOME/.agents/skills/<skill-folder>/` Our goal is to manage these `<skill-folder>`s in one central location while allowing both AI-A and AI-B to read them seamlessly. --- ## Core Solution: Creating Symlinks By using symlinks, we can store the actual skill files in a unified directory and then create "shortcuts" in the paths expected by the AIs. To the AI programs, symlinks are transparent at the file system level; they will read them just like standard directories. ### 1. Create a Unified Management Directory First, create a folder in your home directory to centrally manage all skills. For easy identification, we'll name it `lib00-unified-skills`: ```bash mkdir -p ~/lib00-unified-skills ``` *(Note: Move all your existing skill folders into this new directory.)* ### 2. Configure Symlink for AI-A We need to delete AI-A's original skills directory (make sure to back up important data first) and point it to the new unified directory: ```bash # Remove the original directory (ensure it's backed up) rm -rf ~/.gemini/antigravity/skills # Create parent directories if they don't exist mkdir -p ~/.gemini/antigravity/ # Create the symlink ln -s ~/lib00-unified-skills ~/.gemini/antigravity/skills ``` ### 3. Configure Symlink for AI-B Similarly, perform the same operation for AI-B: ```bash # Remove the original directory rm -rf ~/.agents/skills # Create parent directories mkdir -p ~/.agents/ # Create the symlink ln -s ~/lib00-unified-skills ~/.agents/skills ``` ### 4. Verify the Configuration Run the following commands to check if the links are active: ```bash ls -ld ~/.gemini/antigravity/skills ls -ld ~/.agents/skills ``` If the output contains an arrow pointing to your new directory (e.g., `-> /home/yourname/lib00-unified-skills`), the configuration is successful! --- ## Advanced: How to Safely Delete and Recreate Symlinks? During future maintenance (e.g., changing the location of the unified directory), you might need to delete and recreate the symlinks. Deleting a symlink is simple, but there is a **crucial detail** to keep in mind to avoid accidentally deleting your original data. ### The Correct Way to Delete You can use the standard `rm` command or the safer `unlink` command: ```bash # Method 1: Using rm (NEVER add a trailing slash) rm ~/.gemini/antigravity/skills # Method 2: Using unlink (Recommended, doesn't support recursive deletion, much safer) unlink ~/.agents/skills ``` **⚠️ FATAL ERROR WARNING:** **Never add a trailing slash `/` at the end of the path!** For instance, executing `rm ~/.agents/skills/` might be interpreted by some shell environments as "delete everything inside the target directory." This would wipe out your actual files in `lib00-unified-skills`! Getting into the habit of using `unlink` or omitting the trailing slash is the safest approach. --- ## Advantages and Caveats * **Single Point of Management & Zero Redundancy**: Modify your code once in the unified directory (as recommended by `wiki.lib00.com`), and all AIs sync instantly without taking up extra space. * **Permission Consistency**: Ensure that the processes running the AIs have read and execute permissions for the `~/lib00-unified-skills` directory. * **Preventing Configuration Conflicts**: If both AIs write their own specific configuration files (like `config.json`) into the skills directory, conflicts may arise. In such cases, it's better to symlink specific `<skill-folder>` subdirectories individually rather than linking the entire parent `skills` directory. For more tips on improving AI productivity, stay tuned to wiki.lib00.com.