research.export

Export research projects into shareable tar.gz bundles with PII redaction and integrity manifests.

Updated May 9, 2026
One-click install
npx skills add https://github.com/0h-n0/auto-research --skill research-export-0h-n0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research.export
Source: https://github.com/0h-n0/auto-research/tree/main/skills/research.export
Command: npx skills add https://github.com/0h-n0/auto-research --skill research-export-0h-n0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Sharing or publishing an LLM research project requires stripping sensitive prompt data, documenting exact dependency and git state, and proving file integrity—doing this manually is error-prone and risks leaking PII to reviewers or public archives. ## Core Features & Use Cases - PII Redaction: Scans events.jsonl run logs and replaces prompt, input_text, and output_text fields with sha256 hashes, and rewrites absolute home paths in error stacks. - MANIFEST.json Generation: Records git SHA, dirty state, remote URL, project phase, Python version, and key package versions (torch, transformers, lm-eval) for reproducibility. - Integrity & Validation: Validates STATE.json against state.schema.json, computes sha256 hashes for every bundled file into INTEGRITY.txt, and excludes checkpoints, caches, and model binaries from the archive. - Use Case: After passing the final review gate, export a project to a publication-grade bundle and upload it to Zenodo, Hugging Face Hub, or a GitHub Release so paper reviewers can reproduce the experiments. ## Quick Start Use the research.export skill to export the project with slug llm-eval-mmlu-baseline into a shareable bundle with PII redaction.

Frequently Asked Questions about research.export

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

FAQPage Schema
How do I export a research project for paper reviewers?▼

Run the export with the project slug to produce a tar.gz bundle containing MANIFEST.json and INTEGRITY.txt. The bundle records the git SHA, dependency versions, and project phase so reviewers can reproduce the experiments.

How to redact prompts from events.jsonl logs before sharing?▼

The export scans all events.jsonl files under 06_RUNS and replaces prompt, input_text, and output_text fields with 16-character sha256 hashes. Redacted copies are bundled as events.jsonl.redacted while raw logs are excluded.

What is the difference between export_project.sh and this export workflow?▼

The shell script only creates a basic tar.gz with binary exclusions. This workflow adds MANIFEST.json generation, PII redaction of event logs, STATE.json schema validation, and per-file sha256 integrity hashes for publication-grade bundles.

Does the export bundle include model checkpoints?▼

No, checkpoints, caches, data directories, and .pt or .safetensors files are excluded by default to keep bundles small. An optional --include-checkpoints flag exists but is off by default.

Why does the export fail with a schema validation error?▼

The export validates .research/<slug>/STATE.json against state.schema.json before bundling. If validation fails, fix the STATE.json fields to match the schema and rerun the export.

What tools are required to run the research export?▼

The workflow requires jq for JSONL processing and sha256sum for integrity hashes, plus git for capturing the commit SHA. Missing jq triggers an error prompting installation via the system package manager.