$npx -y skills add derailed-dash/dazbo-agent-skills --skill deploy-skills-in-antigravityDownloads, installs, and relocates new agent skills to the global Antigravity shared directory (~/.gemini/skills/) to make them available across all tools. Use when the user requests to download, install, import, or update new agent skills.
| 1 | # Deploying Skills in Antigravity |
| 2 | |
| 3 | This skill provides a structured workflow for downloading, installing, and relocating new agent skills. It automates the installation process via `npx` and ensures that all downloaded skills are cleanly migrated to the global/shared location so they are instantly accessible to all Google Antigravity tools. |
| 4 | |
| 5 | ## Table of Contents |
| 6 | |
| 7 | - [Triggers](#triggers) |
| 8 | - [Prerequisites](#prerequisites) |
| 9 | - [Installation and Relocation Workflow](#installation-and-relocation-workflow) |
| 10 | - [OS-Specific Relocation Commands](#os-specific-relocation-commands) |
| 11 | - [Verification Loop](#verification-loop) |
| 12 | |
| 13 | ## Triggers |
| 14 | |
| 15 | This skill MUST trigger whenever: |
| 16 | |
| 17 | - The user asks to download, install, import, setup, or update a new agent skill. |
| 18 | - The user mentions adding a skill from a repository or a specific branch/commit. |
| 19 | - The user or agent refers to CLI commands such as `npx skills add`, `skills add`, `skills install`, or `npx skills`. |
| 20 | - The user provides a repository URL (e.g. `https://github.com/...`) and asks to "add" or "integrate" its skills. |
| 21 | |
| 22 | ## Prerequisites |
| 23 | |
| 24 | - **Node.js**: The system must have `npx` available to run the `skills` tool. |
| 25 | - **Access Permissions**: Ensure you have directory write permissions for `~/.agents/skills/` and the global (Agy) shared directory `~/.gemini/skills/`. |
| 26 | |
| 27 | ## Installation and Relocation Workflow |
| 28 | |
| 29 | Copy this checklist and track your progress: |
| 30 | |
| 31 | ``` |
| 32 | Skill Deployment Progress: |
| 33 | - [ ] Step 1: Parse the user's installation request |
| 34 | - [ ] Step 2: Run the installation command |
| 35 | - [ ] Step 3: Relocate the skills to the shared global directory |
| 36 | - [ ] Step 4: Verify that files are correctly positioned |
| 37 | ``` |
| 38 | |
| 39 | **Step 1: Parse the user's installation request** |
| 40 | |
| 41 | Identify the target repository URL and optional flags such as `--skill` or specific branch/commit references. |
| 42 | Common patterns: |
| 43 | - Repository installation: `npx skills add https://github.com/username/repo-name -y -g` |
| 44 | - Specific skill installation: `npx skills add https://github.com/username/repo-name -y -g --skill skill-name` |
| 45 | |
| 46 | **Step 2: Run the installation command** |
| 47 | |
| 48 | Propose and execute the installation command using the `run_command` tool. |
| 49 | If the command fails due to permission errors, request appropriate permissions before retrying. |
| 50 | |
| 51 | **Step 3: Relocate the skills to the shared global directory** |
| 52 | |
| 53 | Once installed, the skills reside in `~/.agents/skills/`. To make them available to all Google Antigravity tools, relocate them to `~/.gemini/skills/`. |
| 54 | Use the appropriate OS-specific relocation command based on the host operating system. |
| 55 | |
| 56 | **Step 4: Verify that files are correctly positioned** |
| 57 | |
| 58 | Perform the comprehensive checks outlined in the [Verification Loop](#verification-loop) to ensure the skill is fully functional and registered. |
| 59 | |
| 60 | ## OS-Specific Relocation Commands |
| 61 | |
| 62 | Depending on the operating system, execute the appropriate shell command or script: |
| 63 | |
| 64 | ### Linux & macOS (Bash/Zsh) |
| 65 | |
| 66 | Run this clean replacement script. It removes any existing versions in `~/.gemini/skills/` before moving the newly installed versions: |
| 67 | |
| 68 | ```bash |
| 69 | mkdir -p "$HOME/.gemini/skills/" && [ -d "$HOME/.agents/skills" ] && for d in "$HOME/.agents/skills"/*/; do [ -d "$d" ] && rm -rf "$HOME/.gemini/skills/$(basename "$d")" && mv "$d" "$HOME/.gemini/skills/"; done |
| 70 | ``` |
| 71 | |
| 72 | ### Windows (PowerShell) |
| 73 | |
| 74 | If operating on a Windows host environment, run the following PowerShell command: |
| 75 | |
| 76 | ```powershell |
| 77 | $sourceDir = "$HOME\.agents\skills" |
| 78 | $destDir = "$HOME\.gemini\skills" |
| 79 | if (-not (Test-Path $destDir)) { New-Item -ItemType Directory -Path $destDir -Force } |
| 80 | Get-ChildItem -Path $sourceDir -Directory | ForEach-Object { |
| 81 | $target = Join-Path $destDir $_.Name |
| 82 | if (Test-Path $target) { Remove-Item -Path $target -Recurse -Force -ErrorAction SilentlyContinue } |
| 83 | Move-Item -Path $_.FullName -Destination $destDir -Force |
| 84 | } |
| 85 | ``` |
| 86 | |
| 87 | ## Verification Loop |
| 88 | |
| 89 | Before completing the task, the agent MUST run the following verification sequence: |
| 90 | |
| 91 | ### 1. Folder Existence and Relocation Verification |
| 92 | Confirm the skill directory has been successfully moved to the global shared path: |
| 93 | - **Linux/macOS:** `ls -la ~/.gemini/skills/` |
| 94 | - **Windows:** `Get-ChildItem "$HOME\.gemini\skills"` |
| 95 | |
| 96 | ### 2. Frontmatter & Integrity Check |
| 97 | Verify that the `SKILL.md` file exists in the target directory and has a valid YAML frontmatter block: |
| 98 | - **Command:** Read the first 10 lines of the relocated `SKILL.md` and confirm it starts with `---` and contains valid `name` and `description` keys. |
| 99 | |
| 100 | ### 3. Subdirectory Validation |
| 101 | For complex skills, ensure that nested folders (such as `references/`, `evals/`, or `scripts/`) are present and populated: |
| 102 | - **Command:** Verify that critical folders are present a |