Export

v1.0.1

Export a Codex session JSONL from ~/.codex/sessions into a clean Markdown transcript in ~/Documents/Exports. Use when the user wants to export, save, or conv...

⭐ 0· 55·1 current·1 all-time

by@bestisblessed

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for bestisblessed/export.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Export" (bestisblessed/export) from ClawHub.
Skill page: https://clawhub.ai/bestisblessed/export
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install export

ClawHub CLI

Package manager switcher

npx clawhub@latest install export

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

medium confidence

✓

Purpose & Capability

The included script reads files from ~/.codex/sessions and writes Markdown files to ~/Documents/Exports, matching the skill name and description.

ℹ

Instruction Scope

SKILL.md instructs running scripts/export_conversation.py and describes expected I/O. The runtime instructions and script remain within the stated purpose (reading local session files and producing Markdown). The SKILL.md explicitly requires the ~/Documents/Exports directory to exist before running.

✓

Install Mechanism

No install spec — instruction-only skill with an included script; nothing is downloaded or installed. This is low-risk from an install perspective.

Credentials

The registry metadata lists no required environment variables, but the script will read os.environ['CODEX_THREAD_ID'] when no session-id argument is passed. SKILL.md mentions using the Codex thread id from the environment, but the skill metadata did not declare this env var. This mismatch can cause runtime failures and is an undeclared dependency on a potentially sensitive env var.

✓

Persistence & Privilege

The skill is not always-enabled and does not attempt to modify other skills or system-wide settings. It only reads and writes files under the user's home directories.

Assessment

This script appears to do exactly what it claims: convert local Codex session JSONL to Markdown. Before running it: (1) ensure ~/Documents/Exports exists (the script will not create it); (2) prefer invoking the script with an explicit session id (scripts/export_conversation.py <session-id>) because if you rely on the default behavior the script expects CODEX_THREAD_ID to be set in the environment — that env var is referenced by the code but not declared in the skill metadata; (3) review the contents of ~/.codex/sessions for any sensitive information before exporting or moving files; (4) note the filename construction uses match.stem[28:], which may produce unexpected or truncated filenames — verify outputs after a test run. No network calls or external installs are present, so the skill operates locally. If you want higher assurance, run the script manually on a non-sensitive session first or inspect it in a sandbox.

Like a lobster shell, security has layers — review code before you run it.

latestvk97fq8dad5my3w3xshwdvm00as85jfqz

55downloads

0stars

2versions

Updated 2d ago

v1.0.1

MIT-0

Export Conversation

Run scripts/export_conversation.py.

This exports the current chat by default using the Codex thread id from the environment.

To export a different conversation, pass a raw session id, for example:

scripts/export_conversation.py 019dc927-dac9-7f23-b313-917d776d189e

The script reads from ~/.codex/sessions and writes:

~/Documents/Exports/<session-id>.md

Print the saved path after running it.

Make sure ~/Documents/Exports already exists before running the script.

Comments

Loading comments...