agent-skills-setup

name	agent-skills-setup
version	0.7.5
license	MIT
compatibility	Requires local Bash and filesystem read/write access for resolved migration targets. Python 3 is required for automatic MCP conversion and redaction. No network access.
permissions	["file_read","file_write","shell"]
description	Use when a user asks to migrate or transfer AI-assistant context between two named supported IDEs or agent products. Handle selected skills, rules, prompts, commands, or MCP configuration with a scoped, verifiable plan.

AI IDE Context Migration

Route

1. Resolve source, target, objects, scope, and workspace from the request and environment. Ask only when a missing choice would change the destination.
2. Resolve both IDs in ide-registry.md, then read only references/ides/.md and references/ides/.md. Use ide-paths.json or --print-path for paths.
3. Load only the needed reference:

Situation	Read
Before preview or apply	migration-safety.md
mcp, project-mcp, or --source-mcp-file	mcp-migration.md
Any other file-backed object	object-migration.md
Approved apply or proof	verification.md

The per-IDE reference describes product behavior; the script describes what is automated. Flag a mismatch before applying.

Execution

• Global scope defaults to skills. Project-backed objects require an explicit workspace in the command.
• Before copying a Skill, scan every source text file and reject literal credentials or links outside that Skill; leave both source and target intact.
• Existing rules and prompt targets follow --strategy: backup is the default, skip preserves them, and overwrite replaces or merges them.
• Keep whole config files and opaque project trees manual. Rebuild a documented setting or migrate a dedicated supported object.
• Never move secrets, OAuth/session state, runtime metadata, approval grants, chat history, databases, or generated memory. Use manual reconstruction when redaction or conversion is unclear.
• Claude Desktop app MCP in Settings → Extensions and Settings → Connectors is UI-managed; do not infer or rewrite it from legacy JSON.
• Use --dry-run to resolve the plan. If the user already requested the migration and the target is unambiguous, apply the same command with --yes --json in the same task; do not ask for redundant confirmation. Report evidence and native target discovery.

Commands

Run bash scripts/smart-ide-migration.sh --help for flags. Commands run from this Skill directory.

bash scripts/smart-ide-migration.sh --print-path cursor project-mcp

bash scripts/smart-ide-migration.sh \
  --source cursor --target claude --workspace /path/to/project \
  --objects skills,rules --scope project --dry-run