بنقرة واحدة
portability-codex
// Guide for importing Codex workspace conventions into NeuDrive or exporting NeuDrive context back into Codex workflows.
// Guide for importing Codex workspace conventions into NeuDrive or exporting NeuDrive context back into Codex workflows.
Use neuDrive as the canonical hub for platform import, export, listing, and status workflows through MCP plus platform-native entrypoints.
Guide for importing ChatGPT data into NeuDrive or restoring NeuDrive data into ChatGPT-compatible structures.
Checklist-first guide for importing Claude data into NeuDrive and exporting NeuDrive context back into Claude-compatible materials.
Fallback guide for migrating data from platforms that do not yet have a dedicated NeuDrive portability manual.
| name | portability/codex |
| description | Guide for importing Codex workspace conventions into NeuDrive or exporting NeuDrive context back into Codex workflows. |
| when_to_use | Use when the user asks to migrate, back up, restore, import, or export Codex projects, prompts, tools, or automations. |
| tags | ["portability","migration","backup","codex","neudrive"] |
| source | system |
| read_only | true |
Use this skill when the user wants to move data between Codex and NeuDrive. Codex portability is manual-first: preserve workspace structure, conventions, prompts, tool configuration, and automation intent without claiming full feature parity.
Use this skill for:
workspace or project instructions -> /projects/<name>/context.md plus profile rules where stablereusable prompts -> skill-like reference material or project assetstools / MCP config -> tool metadata and connection metadataautomation manifests -> automation shadow recordssession transcripts or notes -> conversation archive and project logsCodex portability often produces reusable prompt bundles, scripts, or helper packages that should live under neuDrive /skills.
import_skill(name, files) for one text/code bundle whose full directory can be represented as map[path]string.scripts/run.py, prompts/review.txt, config/tool.yaml, and data/schema.xsd are allowed.SKILL.md; include the whole bundle directory and every text/code file it depends on.import_skill as the primary transport.import_skills_archive for multi-bundle imports, binary-heavy bundles, or any case where exact bytes matter.SKILL.md, scripts/..., prompts/..., assets/...skill-a/SKILL.md, skill-b/SKILL.md, and related files below each directorySKILL.md./skills/<name>/....cat base64(zip), paste archive base64 into chat, or otherwise emit long archive strings into the conversation, because that can crash the conversation session.prepare_skills_upload and present both the browser upload link and the curl command when available. Prefer the browser path for ordinary users and curl for terminal-comfortable users.Recommended order:
memory/profile./projects/<name>/context.md.write_file for imported data that should be preserved as files even when it does not fit a first-class neuDrive domain such as profile, memory, project, or skill. The agent may design a sensible custom directory structure for those files./skills, apply the skill/package rules above and preserve the full directory contents.When exporting NeuDrive data back into Codex:
Use or adapt this prompt when another agent needs to execute Codex portability work:
Read
/skills/portability/codex/SKILL.mdfirst. Separate stable workspace conventions from project-specific context. Write stable rules into NeuDrive profile, write true project context into NeuDrive projects, usewrite_filefor additional imported file-like data that should be preserved even when it does not fit a first-class neuDrive domain, and preserve tool and MCP configuration as metadata plus automation intent as recreation notes. If reusable prompt or script bundles should live under neuDrive/skills, useimport_skillfor one text/code directory with full contents. If the user asks for all skills, a workspace export, or any multi-bundle batch, do not useimport_skillas the primary transport; useimport_skills_archive/prepare_skills_uploadfor multi-skill, binary-heavy, or transport-limited archives instead. Do notcatbase64(zip), paste archive base64 into chat, or otherwise emit long archive strings into the conversation. When exporting back to Codex, produce manual-first setup instructions and clearly mark unsupported parity.
{{CURRENT_USER_SNAPSHOT}}