icfpc-session-archive

Scan, sanitize, verify, and upload Codex or Claude Code session exports to S3.

1|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/d-experts/public-icfpc-2026 --skill icfpc-session-archive-d-experts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: icfpc-session-archive
Source: https://github.com/d-experts/public-icfpc-2026/tree/main/.agents/skills/icfpc-session-archive
Command: npx skills add https://github.com/d-experts/public-icfpc-2026 --skill icfpc-session-archive-d-experts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sharing AI agent session history from a contest repository risks leaking credentials, private content, and machine-local paths; this Skill enforces a scan-export-verify-review-upload pipeline so only sanitized, hash-verified session exports reach the team S3 archive. ## Core Features & Use Cases - Sanitized session export: Scans Codex and Claude Code sessions for a date range, exports them under the canonical proxy submittedBy identity, and flags credential-risk files. - Mechanical verification and review: Validates file hashes, allowed event fields, and absence of credential patterns or absolute paths, then requires a full REVIEW.md content check before upload. - Team impact report: Aggregates all members' exports from an S3 prefix into one HTML timeline of verified score improvements and concurrent session activity. - Use Case: After the contest, run the export for the full date range, verify and review the output, then upload to the team S3 prefix and generate the shared TEAM_TIMELINE.html report. ## Quick Start Use the icfpc-session-archive skill to scan, export, verify, review, and upload my contest sessions for the full contest period.

Frequently Asked Questions about icfpc-session-archive

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

FAQPage Schema
How do I export and upload Claude Code or Codex sessions to S3?▼

Run pnpm session:scan for the date range, then pnpm session:export, then pnpm session:verify on the export directory. After reviewing REVIEW.md, preview with pnpm session:upload --dry-run and finally upload with --confirm-reviewed.

How do I aggregate team AI session exports into one HTML report?▼

Sync the shared S3 prefix into a local inbox with aws s3 sync, then run pnpm session:report with --exports-dir and --out to generate one HTML timeline. It keeps only official full-pass updates that strictly lowered the running team proxy score.

Does the session export include raw session files?▼

No. Raw agent session files stay local and are never inspected or uploaded. The uploader writes only manifest.json, REVIEW.md, and sanitized sessions/* files to the S3 prefix.

What identity is used as the submittedBy member name?▼

The export loads member-18/.env like the judge and chooses SUBMITTED_BY, then USER, then LOGNAME. The manifest.json submittedBy value is treated as the canonical member name, with member accepted for older manifests.

What happens if verification finds credentials or private content?▼

Stop before upload and identify the problematic session. Resolve the issue and re-export rather than hand-editing the reviewed export, because file hashes must remain valid for verification to pass.