en | ja

---

SK / agent-skill-porter

A skill lifecycle management CLI for AI agents — Add and manage updates for any Skill, and convert formats across Claude Code and many other agents. Zero config, no extra files needed.

Installation

pnpm add -g agent-skill-porter

Quick Start

Add a skill from GitHub

# Add skills to your local project
sk add https://github.com/anthropics/skills

# Check for upstream updates
sk update -n

# Apply upstream updates
sk update

# Add a specific skill to a specific agent's directory (to ./.claude/skills/)
sk add https://github.com/anthropics/skills/tree/main/skills/skill-creator claude

# Place into user-level (global) directory (to ~/.claude/skills/)
sk add https://github.com/anthropics/skills/tree/main/skills/skill-creator claude -g

# Preview only, without downloading (dry run)
sk add https://github.com/anthropics/skills -n

Reformat and relocate skills for other agents

# Convert skill format and placement from Claude to Gemini
sk sync claude gemini

# Convert in both directions
sk sync gemini claude

# Convert skills in user-level (global) directories
sk sync gemini claude -g

# Preview changes before applying
sk sync gemini claude -n

Supported Agents

Agent	Skills	Commands	Placeholders
Claude Code	✓	✓	✓
Gemini CLI	✓	✓	✓
Codex CLI	✓	✓	✓
OpenCode	✓	✓	✓
GitHub Copilot	✓	✓	-
Cursor	✓	✓	-
Chimera Hub	✓	✓	✓

Features

• Add from GitHub — Fetch skills directly from GitHub repositories with sk add
• Update from Upstream — Check and apply upstream changes to downloaded skills with sk update, optionally pinning to the newest version at least N days old via --min-age
• List Skills — List all skills across agents with sk list
• Skill Info — View skill metadata and source links with sk info
• Provenance Tracking — add / download record the source in _from (as owner/repo@shortHash, 7-char SHA by default; use --full-hash for full 40-char SHA). For skills, sync preserves _from only when the source skill already has it; commands may still record source provenance. Disable writing or copying with --no-provenance
• Cross-Agent Conversion — Convert skill formats and placement across 7 agents, absorbing format differences automatically
• Placeholder Conversion — $ARGUMENTS ↔ {{args}}, file references, shell commands auto-converted
• Dry-Run Preview — Preview changes with -n before applying them
• Lossless Conversion — Chimera Hub — Preserves all agent-specific settings across round-trip conversions (details)

FAQ

What does _from mean, and when should I use --no-provenance?

_from records where a skill came from (typically owner/repo@shortHash) so you can trace local copies if an upstream public skill is later found to be compromised. add / download generate it from the upstream repository, while skill sync only copies an existing _from from the source skill. Command sync remains separate and may still record source provenance. Use --no-provenance when you do not want that metadata written or copied into frontmatter—for example, internal mirrors or policies that discourage embedding repository references.