Claude Skill

data-export

Export Claude Code session and analytics data in JSON, CSV, or Markdown formats. Supports exporting sessions, events, costs, and analytics for external analysis or reporting. Use for data backup or integration.

LLM Mart · 0 points · 8 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download hoangsonww-claude-code-agent-monitor-plugins_ccam-devtools_skills_data-export-83d4df5.zip · 1 KB

hoangsonww/claude-code-agent-monitor 1014 238 forks MIT Updated 21h ago

Part of hoangsonww/claude-code-agent-monitor — 86 skills

Install

skills CLI

npx skills add https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-devtools/skills/data-export

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install hoangsonww-claude-code-agent-monitor@llmmart

Git git clone https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole hoangsonww/claude-code-agent-monitor collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Data Export

Export Agent Monitor data in various formats.

Input

The user provides: $ARGUMENTS

This may be:

A data type: "sessions", "events", "analytics", "costs", "all"
A format: "json", "csv", "markdown" (default: json)
A filter: "last 7 days", "session ", "completed only"
Combined: "sessions csv last 30 days"

Procedure

Parse the request to determine:
- Data scope: which data to export
- Format: output format
- Filters: time range, status, session ID
Fetch data from http://localhost:4820:
- Sessions: GET /api/sessions?limit=1000
- Events: GET /api/events?limit=5000
- Analytics: GET /api/analytics
- Costs: GET /api/pricing/cost
- Full export: GET /api/settings/export

Transform to requested format:

JSON Format

Pretty-printed JSON with metadata header:

{
  "export": {
    "source": "Claude Code Agent Monitor",
    "exported_at": "2025-04-11T12:00:00Z",
    "filters": { "type": "sessions", "range": "last 7 days" },
    "count": 42
  },
  "data": [...]
}

CSV Format

Standard CSV with headers, proper quoting, and ISO timestamps:

id,name,status,model,started_at,ended_at,duration_minutes,cost_usd

Markdown Format

Human-readable tables with summary statistics:

# Agent Monitor Export — Sessions (Last 7 Days)
| ID | Name | Status | Model | Duration | Cost |
|...
**Total: 42 sessions, $12.34 cost**

Output the data:
- For small exports (<100 rows): output directly
- For large exports: save to file and report the path
- Include row count and any filter notes

Output Format

Deliver the exported data in the requested format. Always include:

Export metadata (when, what, filters applied)
Row/record count
Suggested filename for saving

Files (claude-code-agent-monitor)

agents

openai.yaml 262 B

interface:
  display_name: "Data Export"
  short_description: "Export Claude Code session and analytics data in JSON, CSV,..."
  default_prompt: "Use $data-export to inspect CCAM data and complete this workflow safely."
policy:
  allow_implicit_invocation: true

SKILL.md 2.1 KB

---
name: data-export
description: >
  Export Claude Code session and analytics data in JSON, CSV, or Markdown
  formats. Supports exporting sessions, events, costs, and analytics
  for external analysis or reporting. Use for data backup or integration.
---

# Data Export

Export Agent Monitor data in various formats.

## Input

The user provides: **$ARGUMENTS**

This may be:
- A data type: "sessions", "events", "analytics", "costs", "all"
- A format: "json", "csv", "markdown" (default: json)
- A filter: "last 7 days", "session {id}", "completed only"
- Combined: "sessions csv last 30 days"

## Procedure

1. **Parse the request** to determine:
   - Data scope: which data to export
   - Format: output format
   - Filters: time range, status, session ID

2. **Fetch data** from `http://localhost:4820`:
   - Sessions: `GET /api/sessions?limit=1000`
   - Events: `GET /api/events?limit=5000`
   - Analytics: `GET /api/analytics`
   - Costs: `GET /api/pricing/cost`
   - Full export: `GET /api/settings/export`

3. **Transform to requested format**:

   ### JSON Format
   Pretty-printed JSON with metadata header:
   ```json
   {
     "export": {
       "source": "Claude Code Agent Monitor",
       "exported_at": "2025-04-11T12:00:00Z",
       "filters": { "type": "sessions", "range": "last 7 days" },
       "count": 42
     },
     "data": [...]
   }
   ```

   ### CSV Format
   Standard CSV with headers, proper quoting, and ISO timestamps:
   ```
   id,name,status,model,started_at,ended_at,duration_minutes,cost_usd
   ```

   ### Markdown Format
   Human-readable tables with summary statistics:
   ```markdown
   # Agent Monitor Export — Sessions (Last 7 Days)
   | ID | Name | Status | Model | Duration | Cost |
   |...
   **Total: 42 sessions, $12.34 cost**
   ```

4. **Output the data**:
   - For small exports (<100 rows): output directly
   - For large exports: save to file and report the path
   - Include row count and any filter notes

## Output Format

Deliver the exported data in the requested format. Always include:
- Export metadata (when, what, filters applied)
- Row/record count
- Suggested filename for saving