SkillAgentSearch skills...

fixing-claude-export-conversations

Fixes broken line wrapping in Claude Code exported .txt conversation files — rebuilds tables, paragraphs, paths and tool calls hard-wrapped at a fixed width.

Install / Use

npx skills add daymade/claude-code-skills --skill claude-export-txt-better

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Claude Code

Tags

Our assessment of fixing-claude-export-conversations

fixing-claude-export-conversations scores 89/100 on our quality scale, 1645th of 4,698 Development & Engineering skills we index (top 36%).

Its SKILL.md is 4.3 KB long, well organised into 10 sections with 5 code examples: a solid amount of guidance for an agent.

With 1,426 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so fixing-claude-export-conversations is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

fixing-claude-export-conversations compared with similar skills

All 4 of these similar skills score higher than fixing-claude-export-conversations; compare them before choosing.

SkillScoreStarsUpdatedFormat
fixing-claude-export-conversations (this skill)by daymade891.4k53d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install fixing-claude-export-conversations?
Run npx skills add daymade/claude-code-skills --skill fixing-claude-export-conversations. The install tabs above show the steps for each supported agent.
Which AI agents does fixing-claude-export-conversations work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is fixing-claude-export-conversations safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is fixing-claude-export-conversations still maintained?
The repository was last updated about 2 months ago, so fixing-claude-export-conversations is actively maintained.

name: fixing-claude-export-conversations disable-model-invocation: true description: >- Fixes broken line wrapping in Claude Code exported .txt conversation files — rebuilds tables, paragraphs, paths and tool calls hard-wrapped at a fixed width. Use for an export (YYYY-MM-DD-HHMMSS-*.txt) with broken tables, split paths, or mangled tool output, or "fix export" / "make export readable". Not for a live web conversation (use read-claude-web-conversation) or session history (use read-claude-code-history).

Fixing Claude Code Export Conversations

Reconstruct broken line wrapping in Claude Code exported .txt files.

Quick Start

# Fix and show stats
uv run <skill-path>/scripts/fix-claude-export.py <export.txt> --stats

# Custom output
uv run <skill-path>/scripts/fix-claude-export.py <export.txt> -o fixed.txt

# Validate the result (per-check PASS/FAIL with evidence; all must pass)
uv run <skill-path>/scripts/validate-claude-export-fix.py <export.txt> fixed.txt

Replace <skill-path> with the resolved path to this skill's directory. Find it with:

find ~/.claude -path "*/fixing-claude-export-conversations/scripts" -type d 2>/dev/null

Workflow

Copy this checklist and track progress:

- [ ] Step 1: Locate the exported .txt file
- [ ] Step 2: Run fix script with --stats
- [ ] Step 3: Run validation suite
- [ ] Step 4: Spot-check output (tables, CJK paragraphs, tool results)
- [ ] Step 5: Deliver fixed file to user

Step 1: Locate the file. Claude Code exports use the naming pattern YYYY-MM-DD-HHMMSS-<slug>.txt.

Step 2: Run the fix script.

uv run <skill-path>/scripts/fix-claude-export.py <input.txt> -o <output.txt> --stats

Review the stats output — typical results: 20-25% line reduction, 80+ table borders fixed, 160+ table cells fixed.

Step 3: Run the validation suite.

uv run <skill-path>/scripts/validate-claude-export-fix.py <input.txt> <output.txt>

All checks must pass. If any fail, investigate before delivering. Use --verbose for full details on passing checks too.

Step 4: Spot-check. Open the output and verify:

  • Tables have intact borders (box-drawing characters on single lines)
  • CJK/English mixed text has pangu spacing (Portal 都需要, not Portal都需要)
  • Tool result blocks (⎿) have complete content on joined lines
  • Diff output within tool results has each line number on its own line

Step 5: Deliver the fixed file to the user.

What Gets Fixed

The script handles 10 content types using a state-machine with next-line look-ahead:

  • User prompts (❯ prefix, dw=76 padding) — paragraph joins with pangu spacing
  • Claude responses (● prefix) — narrative, bullet, and numbered list joins
  • Claude paragraphs (2-space indent) — next-line look-ahead via _is_continuation_fragment
  • Tables — border reconstruction, cell re-padding with pipe-count tracking
  • Tool calls (● Bash( etc.) — path and argument reconstruction
  • Tool results (⎿ prefix) — continuation joins including deeper-indented fragments
  • Plan text (5-space indent) — next-line look-ahead via _is_plan_continuation_fragment
  • Agent tree (├─/└─) — preserved structure
  • Separators (────, ---) — never joined
  • Tree connectors (standalone │) — preserved

Key Design Decisions

Next-line look-ahead (not dw thresholds): Instead of asking "was this line wrapped?" (fragile threshold), the script asks "does the next line look like a continuation?" by examining its content patterns — lowercase start, CJK ideograph start, opening bracket, hyphen/slash/underscore continuation.

Pangu spacing: Inserts spaces between ASCII alphanumeric characters and CJK ideographs at join boundaries. Also triggers for %, #, +, : adjacent to CJK.

Mid-token detection: Joins without space when boundaries indicate identifiers (BASE_ + URL), paths (documents + /05-team), or hyphenated names (ready + -together). Exception: -- prefix gets a space (run + --headed).

Safety

  • Never modifies the original file
  • Marker counts verified: ❯, ●, ✻, ⎿, … must match input/output
  • Runaway join detection: warns if any line exceeds 500 display-width
  • Strict UTF-8 encoding — no silent fallbacks

Dependencies

Python 3.10+ via uv run — zero external packages (stdlib only: unicodedata, argparse, re, pathlib, dataclasses).

Related Skills

View on GitHub
GitHub Stars1.4k
CategoryDevelopment
Updated1mo ago
Forks219

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions