history-portability — Claude Code skill: move CCAM history
Pulls in Claude or Claude history and shifts whole CCAM datasets between machines. Useful when you switch laptops or need a restore.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill history-portability -a claude-codeWhat history-portability does
Two jobs sit inside this skill. The first is provider history: it reads the paths and limits for the provider you name, rescans that provider's home directory, or walks a folder you point it at by absolute path. Files and archives go up through the app or the dashboard_upload_history_files MCP tool.
The second job is a full dashboard backup. Run ccam export ccam-export.json, then ccam import-data ccam-export.json. Restores are idempotent and leave existing data alone: sessions already present are skipped as a whole, while new ones carry agents, events, token usage and workflows with them. Run, rule and pricing rows are inserted only where they are missing.
Once the restore finishes, the skill walks through what should have survived: session counts, a few transcripts, token totals, cost, workflow runs, alert rules, and pricing for both Claude and Claude. Skip that pass and a mismatch in tokens or pricing tends to surface later, on live reports.
What it helps with
- move Claude history to a new machine
- import a copied provider history directory
- upload JSONL or an archive through the dashboard
- back up a CCAM dataset and restore it
- confirm tokens, workflows and pricing survived the move
Example prompts for the agent
- Rescan my Claude history and tell me what turned up
- Import the folder
/Users/me/old-ccamas Claude history - Export the dataset and restore it from
ccam-export.json
How to install history-portability
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill history-portability -a claude-code2Manually: put the files in place
~/.claude/skills/history-portability/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/history-portability/
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill history-portability -a codex2Manually: put the files in place
.agents/skills/history-portability/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill history-portability -a cursor2Manually: put the files in place
.cursor/skills/history-portability/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hoangsonww/Claude-Code-Agent-Monitor history-portability2Manually: put the files in place
.github/skills/history-portability/SKILL.md1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill history-portability -a gemini-cli2Platform CLI
gemini skills install https://github.com/hoangsonww/Claude-Code-Agent-Monitor --path plugins/ccam-platform/skills/history-portabilityManually: put the files in place
.devin/skills/history-portability/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill history-portability -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about history-portability
How do I install history-portability in Claude Code?
Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill history-portability -a claude-code. The skill lands at ~/.claude/skills/history-portability/SKILL.md.
What does history-portability do?
It imports Claude or Claude history and moves CCAM datasets between machines. That covers rescanning a provider home, scanning an existing directory, uploading files and archives, and exporting or restoring a backup.
What should I check after restoring a backup?
Session counts, representative transcripts, token totals and cost, workflow runs, alert rules, and pricing for Claude and Claude. Because the restore is idempotent, sessions that already exist are skipped whole, so nothing gets duplicated.
Source text
SKILL.md · MIT
--- name: history-portability description: > Import Claude Code or Codex history and move complete CCAM datasets between machines. Use when rescanning provider history, importing a copied directory, uploading JSONL or archives, exporting a backup, restoring it idempotently, or verifying that tokens, workflows, runs, rules, and pricing survived. --- # History Portability ## Provider History 1. Read provider-specific paths and limits: `ccam import guide --provider claude|codex`. 2. Rescan the configured provider home: `ccam import rescan --provider <provider>`. 3. Scan an existing directory: `ccam import path /absolute/path --provider <provider>`. 4. For file or archive upload, use the app or MCP `dashboard_upload_history_files`. ## Full Dashboard Backup ```bash ccam export ccam-export.json ccam import-data ccam-export.json ``` Restore is idempotent and non-destructive. Existing sessions are skipped as a whole. New sessions bring agents, events, token usage, and workflows. Independent run, rule, and pricing rows are inserted only when absent. Verify session counts, representative transcripts, token totals, cost, workflow runs, alert rules, and both Claude and GPT pricing after restore.
© hoangsonww · MIT · hoangsonww/Claude-Code-Agent-Monitor
