Skip to main content
Skills follow the shared Agent Skills specification, making them generally compatible across different coding agents. However, some advanced features may be agent-specific.

Feature Compatibility Matrix

This table shows which features are supported by each agent:
Basic skills (markdown instructions with YAML frontmatter) work across all agents. Advanced features like allowed-tools, context: fork, and hooks have varying support.

Support by Agent

This compatibility information is based on agent specifications and may change as agents update their implementations. Always check your specific agent’s documentation for the most current information.

Supported Agents

The Skills CLI supports installation to 42+ coding agents. Each agent has specific project and global installation paths:

Universal Agents

These agents use the shared .agents/skills/ directory:
  • Amp - Universal AI coding assistant
  • Kimi Code CLI - Moonshot AI’s CLI agent
  • Replit - Cloud development environment
  • Cline - VS Code extension
  • Codex - OpenAI’s coding agent
  • Cursor - AI-first code editor
  • Gemini CLI - Google’s CLI coding agent
  • GitHub Copilot - GitHub’s AI pair programmer
  • OpenCode - Open-source coding agent

Agent-Specific Paths

Other agents use dedicated skills directories. Here are some examples:
Run npx skills add <repo> without flags to see which agents are detected on your system. The CLI automatically detects installed agents.

Complete Agent List

For the complete list of supported agents and their paths, see the README compatibility table.

Agent-Specific Notes

After installing skills to Kiro CLI, you must manually add them to your custom agent’s configuration:Edit .kiro/agents/<agent>.json:
This manual step is required for Kiro CLI to discover and load the skills.
Replit agent detection looks for .replit file in the current directory. Global installation is supported using the shared .agents/skills/ path.
Claude Code has the most complete feature support, including:
  • allowed-tools for restricting tool access
  • context: fork for isolated skill execution
  • Lifecycle hooks (before, after, error handling)
  • Plugin marketplace compatibility
OpenClaw supports three legacy directory names for backwards compatibility:
  • ~/.openclaw/skills/ (current)
  • ~/.clawdbot/skills/ (legacy)
  • ~/.moltbot/skills/ (legacy)
The CLI automatically detects which one exists on your system.

Custom Configuration Paths

Some agents support custom configuration directories via environment variables:
The Skills CLI respects these environment variables when installing skills.

Agent Config

Technical details about agent configuration

CLI Options

Command-line options for targeting specific agents

Troubleshooting

Common issues and solutions

Skills Directory

Browse available skills for all agents