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.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add XTSoftwareLabs/neatcontext-plugins --skill export --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Export?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/xtsoftwarelabs-export)More formats (shields.io, HTML) on the badges page.
---
name: export
description: 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.
---
# 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:
```text
node "<plugin-root>/src/codex/neatcontext-cli.mjs" list
```
Then run:
```text
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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.