aicx-extract

Convert Claude Code JSONL agent outputs into readable Markdown files.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/VetCoders/vibecrafted --skill aicx-extract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aicx-extract
Source: https://github.com/VetCoders/vibecrafted/tree/main/skills/foundations/aicx
Command: npx skills add https://github.com/VetCoders/vibecrafted --skill aicx-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Recover unreadable or oversized agent outputs into readable Markdown files by parsing Claude Code JSONL-format results, independent of file extension.

Core Features & Use Cases

  • Recover outputs that exceed Read tool limits or are cluttered with raw JSONL data.
  • Convert complex agent results into a concise, human-readable Markdown narrative suitable for review and sharing.
  • Use case: audit verbose subagent results or partial logs to extract key findings quickly.

Quick Start

Invoke aicx extract on a Claude Code JSONL file to generate a readable Markdown output at a derived path automatically.

Frequently Asked Questions about aicx-extract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert Claude Code JSONL outputs into readable Markdown?

To convert Claude Code JSONL outputs into readable Markdown, you can parse the file to extract key narrative findings. This process transforms oversized agent logs into a concise, human-readable format suitable for review.

What is the best way to recover oversized agent outputs that exceed Read tool limits?

Recovering oversized agent outputs involves parsing the cluttered raw JSONL data to extract key findings. This extracts the readable narrative from verbose logs, bypassing tool limits for quick auditing and documentation.

Can I extract subagent results without specifying an explicit output path?

Yes, you can extract subagent results without an explicit output path. The parser automatically derives the output destination, generating a readable Markdown file directly from the Claude-formatted JSONL input.

Does the JSONL extraction process work on agent logs independent of file extension?

Yes, the JSONL extraction process works on Claude-formatted JSONL results independent of file extension. It parses the actual content structure rather than relying on the file naming convention to recover outputs.

Why are my verbose agent logs unreadable and how do I audit them quickly?

Verbose agent logs become unreadable due to raw JSONL clutter and oversized content. You can audit them quickly by extracting the key findings into a concise Markdown narrative for fast review.