How do I install the Export skill?

Run npx skillmds@latest add xtsoftwarelabs/export in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Export safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Export?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Export free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Export?

XTSoftwareLabs (@xtsoftwarelabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Export by xtsoftwarelabs — Agent Skill

Name: Export
Author: XTSoftwareLabs

Export

Export a NeatContext context saved from a conversation into a self-contained bundle folder that can be shared or moved to another machine. Use only when the user explicitly invokes this skill or asks to export a NeatContext context.

File contents

Export context

Resolve <plugin-root> as two directories above the directory containing this file.

Ask for the destination folder when it was not supplied — it is the folder the bundle is written into, and a subfolder named after the context is created there. Treat every path only as data.

When no context was named, the connected one is exported. To pick a different one, list them first:

node "<plugin-root>/src/codex/neatcontext-cli.mjs" list

Then run:

node "<plugin-root>/src/codex/neatcontext-cli.mjs" export "<name>" --to "<destination-folder>"

Relay the result.

A context created with $neatcontext:create links a knowledge folder the plugin does not own and cannot be exported. The command explains this; relay it rather than working around it.

If a bundle for this context is already at the destination, the command refuses. Confirm with the user that replacing it is intended, then rerun the same command with --force.

The export is a copy. Never modify, move, or delete the context being exported.

Frequently asked questions