skills.rest
j5ik2o
j5ik2oCOMMUNITY
Explore all skills by this author →
Website𝕏@j5ik2oGitHub

migrate-skill-to-agent

Migrate skill directories to .agents/skills and create symlinks for Claude Code and Codex CLI.

Updated Jun 23, 2026
Search Tags:#claude code#dotfiles#bash#codex cli#directory structure#symlink#skill migration
One-click install
npx skills add https://github.com/j5ik2o/marp-ai-base --skill migrate-skill-to-agent-j5ik2o
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-skill-to-agent
Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/migrate-skill-to-agent
Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill migrate-skill-to-agent-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Skills stored under .claude/skills are only visible to Claude Code, forcing duplication when you also use Codex CLI. This Skill centralizes the real skill directory under .agents/skills and exposes it to both tools through symlinks, eliminating copy drift. ## Core Features & Use Cases - Directory Migration: Moves a skill from .claude/skills/{name} to .agents/skills/{name} as the single source of truth. - Symlink Creation: Creates relative symlinks from both .claude/skills/ and .codex/skills/ pointing to the migrated directory. - Safety Validation: Refuses to run if the source is missing, already a symlink, or the target already exists. - Use Case: You built a skill under .claude/skills and now want Codex CLI to use the same skill without maintaining two copies; run the migration once and both tools share one directory. ## Quick Start Ask the AI to migrate the skill named my-skill to .agents/skills so both Claude Code and Codex CLI can use it.

Frequently Asked Questions about migrate-skill-to-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share a skill between Claude Code and Codex CLI?▼

Move the skill directory to .agents/skills/{name} and create symlinks from .claude/skills/{name} and .codex/skills/{name} pointing to it. This Skill automates that migration with a single bash script invocation.

How do I migrate a skill from .claude/skills to .agents/skills?▼

Run bash scripts/migrate.sh <skill-name> [project-root] with the skill directory name as the required argument. The script moves the directory and creates relative symlinks in both .claude/skills and .codex/skills.

What happens if the skill is already a symlink in .claude/skills?▼

The migration script exits with an error. It validates that .claude/skills/{name} is a real directory, not a symlink, and that .agents/skills/{name} does not already exist before moving anything.

Does the migration script work outside the project root?▼

Yes, pass the project root path as the optional second argument to migrate.sh. If omitted, it defaults to the current working directory and resolves all paths relative to it.

What are the limitations of this skill migration approach?▼

It only migrates from .claude/skills as the source and relies on symbolic links, which may not work on filesystems or environments without symlink support. It does not merge or handle conflicting existing targets.

Related Skills

Explore More Software Engineering Skills→
defprod1defprod1

defprod-{{skill-name}}

Provides a starter template for authoring DefProd agent skills with phased workflows.

Official
Basic
songkg7songkg7
6

configure-ecc

Guide interactive installation of Everything Claude Code skills and rules.

Community
Intermediate
yan-labsyan-labs
197

skill-link-check

Audits .agents/skills and .claude/skills directories for symlink consistency issues.

Community
Intermediate
adikpbadikpb
1

hermes-agent-profiles

Create and manage directory-locked Hermes agent profiles with isolated skills, personalities, and CLI tools.

Community
Advanced