port-config

Generates equivalent agent configuration files for other AI coding hosts from current official documentation.

3|Updated May 2, 2026
One-click install
npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill port-config-juantrujillodev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: port-config
Source: https://github.com/JuanTrujilloDev/agent-config-template/tree/main/plugin/skills/port-config
Command: npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill port-config-juantrujillodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving a Claude Code configuration (rules, skills, commands, agents, hooks) to another AI coding host like Codex, OpenCode, Gemini CLI, Cursor, or Windsurf is error-prone because each host uses different file formats, paths, and frontmatter constraints that change frequently. ## Core Features & Use Cases - Docs-first research: Looks up the target host's current official documentation online before generating anything, never relying on memory of outdated formats. - Structured mapping: Maps principles, slash commands, subagents, and hooks to the target's equivalents (AGENTS.md, GEMINI.md, .cursorrules, SKILL.md skills), with role-adaptation notes where subagents are unsupported. - Validation before completion: Strictly parses every generated YAML/JSON/TOML frontmatter, confirms referenced paths exist, and reports what could not be ported. - Use Case: You want your spec-driven workflow on Codex; the skill researches Codex's current AGENTS.md and skills format, then generates equivalent files with validated manifests. ## Quick Start Ask the agent to port this configuration to Codex using its current official documentation and validate the generated files.

Frequently Asked Questions about port-config

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

FAQPage Schema
How do I port a Claude Code config to Codex or Cursor?▼

The skill researches the target host's current official documentation, maps each config piece (rules, skills, commands, agents) to the target's equivalent format, then generates and validates the files in the target's exact paths.

How to convert Claude Code skills and commands to other AI coding tools?▼

Slash commands like /spec and /feature become SKILL.md skills or native commands on the target host, while principles become always-on rules files such as AGENTS.md, GEMINI.md, or .cursorrules.

Can Claude Code subagents and hooks be ported to other hosts?▼

Most hosts have no subagent or hook equivalents. Subagents become role-adaptation notes where one agent plays pmo, judge, and security-reviewer in sequence, and hooks become written rules instead of enforced automation.

Why does generated skill frontmatter fail on some hosts?▼

An unquoted colon inside a YAML value silently breaks skill discovery on strict hosts. The skill defensively quotes values and strictly parses every generated YAML, JSON, or TOML manifest before declaring completion.

Does porting rely on memorized config formats?▼

No. Host formats change frequently, so the skill always searches the target's current official documentation first and treats those docs as the specification, preferring vendor docs over blog posts.