Agent Skills Setup Guide

This skill provides standardized instructions on how to install, structure, and configure custom skills for various AI agents. It covers directory paths, file requirements, and triggering mechanisms for global and project scopes.

🚀 Quick Start: IDE Migration Workflow

When user mentions IDE migration, follow this workflow:

Step 1: Ask for Migration Details

Ask the user:

1. 1. Source IDE: Which IDE are you migrating FROM?
2. Target IDE: Which IDE are you migrating TO?
3. Content Types: What to migrate? (skills, rules, prompts, mcp, config, project) - default: all available

Supported IDEs:

• - antigravity, claude, codex, copilot, cursor, INLINECODE5
• INLINECODE6, openclaw, trae, INLINECODE9
• INLINECODE10, zed, neovim, INLINECODE13
• INLINECODE14, aider, roo-code, cline, INLINECODE18

If the IDE is not in the list, follow the "Handling Unknown IDEs" section below.

Step 2: Preview Migration (Dry Run)

Always run dry-run first:

CODEBLOCK0

Skill path varies by current IDE:

• - Trae CN: INLINECODE19
• Trae: INLINECODE20
• Claude Code: INLINECODE21
• Antigravity: INLINECODE22
• OpenClaw: INLINECODE23

Step 3: Execute Migration

After user confirms the preview:

CODEBLOCK1

Step 4: Post-Migration Steps

Inform user about manual steps based on target IDE:

• - VS Code Copilot: Update settings.json to reference migrated skills
• Cursor/Windsurf: Review .cursorrules/.windsurfrules files
• OpenClaw: Update openclaw.json and run INLINECODE24
• Trae: Restart IDE and verify in Skills Center
• Codex: Add agents/openai.yaml for UI visibility

Supported IDEs

IDE	Identifier	Global Path
Antigravity	INLINECODE25	INLINECODE26
Claude Code

claude | ~/.claude/ | | OpenAI Codex CLI | codex | ~/.codex/ | | VS Code Copilot | copilot | ~/.vscode/extensions/ | | Cursor | cursor | ~/.cursor/ | | Windsurf | windsurf | ~/.windsurf/ | | JetBrains IDEs | jetbrains | ~/.idea/ | | OpenClaw | openclaw | ~/.openclaw/ | | Trae (International) | trae | ~/.trae/ | | Trae CN (China) | trae-cn | ~/.trae-cn/ | | VS Code | vscode | ~/.vscode/ | | Zed | zed | ~/.config/zed/ | | Neovim | neovim | ~/.config/nvim/ | | Emacs | emacs | ~/.emacs.d/ | | Continue.dev | continue | ~/.continue/ | | Aider | aider | ~/.aider/ | | Roo Code | roo-code | ~/.roo/ | | Cline | cline | ~/.cline/ | | Amazon Q Developer | amazon-q | ~/.aws/amazon-q/ | | Sourcegraph Cody | cody | ~/.vscode/extensions/ | | Codeium | codeium | ~/.vscode/extensions/ | | Tabnine | tabnine | ~/.vscode/extensions/ | | Replit AI | replit | ~/.replit/ | | PearAI | pearai | ~/.pearai/ | | Supermaven | supermaven | ~/.supermaven/ | | Pieces | pieces | ~/.pieces/ | | Blackbox AI | blackbox | ~/.vscode/extensions/ |

Supported CLI Tools

CLI Tool	Identifier	Global Path	Rules File
Gemini CLI	INLINECODE79	INLINECODE80	INLINECODE81
Goose CLI

goose-cli | ~/.config/goose/ | GOOSE.md | | OpenCode | opencode | ~/.config/opencode/ | OPENCODE.md | | Kilocode | kilocode | ~/.kilocode/ | KILOCODE.md | | Kimi AI CLI | kimiai | ~/.kimi/ | KIMI.md |

🔍 Handling Unknown IDEs

When user mentions an IDE not in the supported list, AI should:

1. 1. Search for information about the IDE's AI assistant configuration:

- Official documentation - GitHub repository - Community forums

1. 2. Identify key configuration paths:

- Global config directory (usually in ~/.<ide-name>/ or ~/.config/<ide-name>/) - Project-level config files (usually .<ide-name>/ in project root) - Rules/instructions file format - MCP server configuration (if supported)

1. 3. Ask the user to confirm findings:

CODEBLOCK2

1. 4. If unable to find information, ask user:

CODEBLOCK3

1. 5. After gathering information, proceed with migration:

- Use the discovered paths - Document the new IDE for future reference

Content Types to Migrate

Type	Description	Example Paths
INLINECODE97	Skills and capabilities (SKILL.md files)	INLINECODE98 → INLINECODE99
INLINECODE100

Coding rules and instructions | .cursorrules → .windsurfrules | | prompts | Custom prompts and prompt templates | .cursor/prompts/ → .windsurf/prompts/ | | mcp | MCP server configurations | ~/.trae-cn/mcps/ | | config | IDE configuration files | argv.json, settings.json | | project | Project-level configurations | .trae/skills/ → .claude/skills/ |

Migration Example

CODEBLOCK4

0. Source of Truth Rule

Unless the user explicitly requests otherwise, treat Antigravity as the canonical source:

• - Antigravity global skills: INLINECODE114
• Mirror targets: Claude Code, OpenAI Codex, VS Code Copilot, Trae, Trae CN, and OpenClaw
• For directory-based agents, sync whole skill folders and remove extras not present in Antigravity
• For VS Code Copilot, flatten each SKILL.md into INLINECODE116
• For Codex, preserve internal directories such as INLINECODE117
• For OpenClaw, sync whole skill folders into ~/.openclaw/skills/ for shared skills and into <agent-workspace>/skills/ for per-agent overrides
• After changes, verify inventory parity and content parity rather than assuming the copy succeeded

1. Quick Reference: Skills Paths

Agent	Global Path	Project Path
Antigravity	INLINECODE120	INLINECODE121
Claude Code

~/.claude/skills/ | .claude/skills/ | | OpenAI Codex | ~/.codex/skills/ | .agents/skills/ | | OpenClaw | ~/.openclaw/skills/ + ~/.openclaw/openclaw.json | <agent-workspace>/skills/ | | Trae | ~/.trae/skills/ | ./.trae/skills/ | | Trae CN | ~/.trae-cn/skills/ | ./.trae/skills/ | | VS Code Copilot| ~/.copilot-skills/ + settings.json | .github/copilot-instructions.md |

2. Universal Skill Structure

Regardless of the agent, every skill should follow this anatomy:

CODEBLOCK5

3. Agent-Specific Deep Dives

For detailed configuration instructions, structure nuances, and UI requirements per agent, refer to:

• - Antigravity: See antigravity.md
• Claude Code: See claude-code.md
• OpenAI Codex: See codex.md (requires agents/openai.yaml for UI features)
• OpenClaw: See openclaw.md (supports bundled/managed/workspace skills, per-agent workspaces, ClawHub, and installer metadata)
• Trae / Trae CN: See trae.md (supports skills CLI and UI import)
• VS Code Copilot: See vscode-copilot.md (supports multiple configuration levels)
• Public Distribution: See publishing.md for GitHub, skills.sh, and Awesome Copilot release paths

4. Setup Workflow

When installing a new skill:

1. 1. Determine Scope: Should this be Global (all projects) or Project-level (shared in repo)?
2. Create Directory: Navigate to the appropriate path above and create the <skill-name> folder.
3. Draft SKILL.md: Ensure the description is comprehensive, as it is the primary trigger for ALL agents.
4. Agent-Specific Polish:

- For OpenClaw, decide whether the skill belongs in shared ~/.openclaw/skills/ or an individual agent workspace skills/ folder, and configure skills.entries / agents.list as needed - For Codex, add the agents/openai.yaml for UI visibility - For VS Code Copilot, add file reference to settings.json - For Trae, can use skills CLI or UI import

5. Recommended Maintenance Workflow

When updating a shared skill used across agents:

1. 1. Edit the Antigravity copy first.
2. If needed, add or update helper scripts under scripts/.
3. Sync all target IDEs from Antigravity.
4. Verify:

- directory inventories match for OpenClaw managed skills after sync - directory inventories match for Claude, Trae, and Trae CN - directory inventories match for Codex after excluding .system/ - Copilot markdown files match Antigravity SKILL.md files - changed skills have matching content after sync

1. 5. Only then report completion.

6. Sync Script

Use the bundled script for repeatable global sync operations:

CODEBLOCK6

Examples:

CODEBLOCK7

Behavior:

• - Creates missing target directories
• Removes extra skills from mirror targets so they exactly match Antigravity
• Preserves Codex internal INLINECODE147
• Mirrors OpenClaw managed skills into INLINECODE148
• Rebuilds Copilot markdown files from Antigravity INLINECODE149
• Prints a concise verification summary

6.1 OpenClaw Automation Helpers

Use the bundled OpenClaw helpers when you need first-class OpenClaw setup rather than a plain file copy:

CODEBLOCK8

The auto-configure helper:

• - installs OpenClaw via the official installer when missing
• installs ClawHub when missing
• syncs shared skills into INLINECODE150
• syncs per-agent overrides into each configured workspace skills/ directory
• installs skill dependencies declared in INLINECODE152
• writes skills.load, skills.install, skills.entries, and agents.list settings into INLINECODE157
• supports --skip-doctor when you need a non-intrusive apply on a machine with an existing gateway service

The update helper:

• - runs openclaw update for the runtime
• runs clawhub update --all for registry-managed workspace skills
• detects and applies local source-of-truth skill changes to shared/per-agent OpenClaw skill directories
• runs openclaw doctor after non-dry-run updates
• supports --skip-doctor for machine-safe update runs when zero gateway interaction is required

Use the ClawHub release helper when you want an exact publish command and metadata validation for a public OpenClaw release:

CODEBLOCK9

7. Smart IDE Migration

The Smart IDE Migration system provides intelligent migration between any supported IDE environments. You specify the source and target IDEs, and the tool handles the migration with real-time progress feedback and comprehensive reporting.

7.1 Supported IDEs

IDE	Identifier	Global Path
Antigravity	INLINECODE163	INLINECODE164
Claude Code

claude | ~/.claude/skills/ | | OpenAI Codex | codex | ~/.codex/skills/ | | VS Code Copilot | copilot | ~/.copilot-skills/ | | Cursor | cursor | ~/.cursor/ | | Windsurf | windsurf | ~/.windsurf/ | | JetBrains IDEs | jetbrains | ~/.idea/ | | OpenClaw | openclaw | ~/.openclaw/skills/ | | Trae (International) | trae | ~/.trae/skills/ | | Trae CN (China) | trae-cn | ~/.trae-cn/skills/ |

7.2 Basic Usage

CODEBLOCK10

Required Parameters:

• - --source <ide>: The IDE to migrate FROM
• INLINECODE184: The IDE to migrate TO

7.3 Migration Options

Option	Description
INLINECODE185	Source IDE (required)
INLINECODE186

Target IDE for migration (required) | | --workspace <dir> | Workspace root directory (default: current directory) | | --objects <list> | Objects to migrate, comma-separated (default: auto-detect) | | --strategy <mode> | Migration strategy: skip, overwrite, backup (default: backup) | | --report <file> | Save migration report to file | | --dry-run | Preview changes without modifying files |

7.4 Migration Content Types

The following content types can be migrated:

Type	Description	Notes
INLINECODE192	Skills and capabilities (SKILL.md files)	Global skills directory
INLINECODE193

Coding rules and instructions | .cursorrules, .windsurfrules, etc. |
| prompts | Custom prompts and prompt templates | Project-level prompts |
| mcp | MCP server configurations | IDE-specific MCP settings |
| config | IDE configuration files | Settings and preferences |
| project | Project-level configurations | .trae/skills, .claude/skills, etc. |

7.5 Migration Strategies

Strategy	Behavior
INLINECODE202	Create timestamped backup before overwriting (default)
INLINECODE203

Replace existing files without backup | | skip | Skip existing files, only copy new ones |

7.6 Example Workflows

Migrate All Content from Trae CN to Claude Code

CODEBLOCK11

Preview Migration (Dry Run)

CODEBLOCK12

Migrate Only Skills and Rules

CODEBLOCK13

Migrate with Custom Workspace

CODEBLOCK14

7.7 Post-Migration Steps

After migration, the report will indicate any manual steps required:

• - VS Code Copilot: Update settings.json to reference migrated skills
• Cursor/Windsurf: Review .cursorrules or .windsurfrules files
• OpenClaw: Update openclaw.json and run INLINECODE209
• Trae: Restart IDE and verify in Skills Center
• Codex: Add agents/openai.yaml for UI visibility

7.8 Content Type Mapping by IDE

Different IDEs use different names and locations for similar content:

Content Type	Antigravity	Claude Code	Trae/Trae CN	VS Code Copilot	Cursor	Windsurf
Skills	INLINECODE211	INLINECODE212	INLINECODE213	INLINECODE214	INLINECODE215	INLINECODE216
Project Skills

.agents/skills/ | .claude/skills/ | ./.trae/skills/ | .github/copilot-instructions.md | .cursor/ | .windsurf/ |
| Rules | - | - | - | .github/instructions/ | .cursorrules | .windsurfrules |
| Prompts | - | - | - | .github/prompts/ | .cursor/prompts/ | .windsurf/prompts/ |
| MCP Servers | - | - | ~/.trae-cn/mcps/ | settings.json | - | - |
| Agent Config | - | - | argv.json | settings.json | - | - |

8. Migrating Skills Between Agents (Legacy)

From Antigravity to All Other Agents

CODEBLOCK15

From Trae CN to Antigravity

CODEBLOCK16

9. Configuration Priority (All Agents)

Priority	Level	Description
1 (Highest)	Project	INLINECODE231, .agents/skills/, .github/copilot-instructions.md, INLINECODE234
2

Workspace | .vscode/settings.json (VS Code only) | | 3 | Global/User | ~/.openclaw/skills/, ~/.trae/skills/, ~/.gemini/antigravity/skills/, settings.json | | 4 (Base) | Bundled | OpenClaw bundled skills and any other agent-managed built-ins |

10. Quick Migration Commands

One-command migration to all agents

CODEBLOCK17

11. Operational Notes

• - Prefer rsync -a --delete over ad hoc copy loops when exact mirror behavior is required.
• Avoid destructive cleanup commands when a mirror sync can express the same intent more safely.
• If Trae international is not installed yet, creating ~/.trae/skills/ is sufficient for pre-seeding the directory.
• If a target contains system-managed content, add an explicit preserve rule before syncing.
• For OpenClaw multi-agent setups, remember that shared skills live in ~/.openclaw/skills/ while per-agent overrides live under each agent workspace skills/ directory.
• OpenClaw skill env injection from skills.entries.*.env only applies to host runs; sandboxed agents need matching agents.defaults.sandbox.docker.env or agents.list[].sandbox.docker.env when a skill must execute inside the sandbox.

12. Public Release Workflow

If the goal is to publish a skill so more people can find and install it:

1. 1. Keep the Antigravity copy as the authoring source.
2. Export the target skill into a public GitHub repository skeleton.
3. Add a repository README with install commands and compatibility notes.
4. Publish the repository publicly on GitHub.
5. Optionally increase discovery by:

- listing or sharing it via skills.sh - contributing it to github/awesome-copilot - posting examples and screenshots in the repo README and release notes

Use the bundled export helper:

CODEBLOCK18

The export helper copies the selected skill into a publishable repository layout and generates a starter README.md.

13. Publishability Criteria

Before publishing a skill publicly, verify that it:

• - solves a specific problem rather than repeating generic model behavior
• does not depend on private local paths without documenting replacements
• includes clear install instructions for at least one agent ecosystem
• explains what the skill does, when to use it, and any safety boundaries
• avoids bundling sensitive credentials, internal URLs, or proprietary assets