okhp3-chatgpt-project-migration
Skill3 starsChanged 2 months agoMITView on GitHub
OverKill Hill P³ ChatGPT project migration. Use when migrating, preserving, extracting, inventorying, normalizing, reconciling, or incorporating ChatGPT project threads, conversation exports, or complete chat histories into a repository. Also activate when a user needs a lossless thread archive, project-to-export crosswalk, provenance ledger, or public-safe distillation workflow. This is the authoritative capture and reconciliation process for ChatGPT project material in this repo -- use it even when the user asks only to "save", "review", or "summarize" a large set of threads.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-decision-recordsSkill
- catalog-integritySkill
- frontend-designSkill
- okhp3-artifact-validationSkill
- okhp3-as-is-process-captureSkill
- okhp3-brand-style-registrySkill
- okhp3-capture-intakeSkill
- okhp3-custom-gpt-builderSkill
- okhp3-custom-gpt-readinessSkill
- okhp3-decision-model-authoringSkill
- okhp3-elicitation-interviewsSkill
- okhp3-equilibrium-reviewSkill
- okhp3-evidence-standardSkill
- okhp3-future-state-strategySkill
- okhp3-gpt-skill-conversion-planSkill
- okhp3-graduation-gateSkill
- okhp3-handoff-packagingSkill
- okhp3-notion-capture-routerSkill
- okhp3-outcome-modeling-coreSkill
- okhp3-overkill-hill-brandSkill
- okhp3-process-captureSkill
- okhp3-process-gap-analysisSkill
- okhp3-process-intake-and-scopeSkill
- okhp3-project-promotionSkill
- okhp3-replit-build-in-publicSkill
- okhp3-replit-canvas-boardSkill
- okhp3-replit-design-pipelineSkill
- okhp3-replit-free-mode-autonomySkill
- okhp3-replit-github-syncSkill
- okhp3-replit-multi-artifactSkill
- okhp3-replit-repl-janitorSkill
- okhp3-replit-repository-janitorSkill
- okhp3-replit-task-executorSkill
- okhp3-repository-janitorSkill
- okhp3-repository-organizerSkill
- okhp3-session-handoffSkill
- okhp3-skill-catalogerSkill
- okhp3-skill-discoverySkill
- okhp3-skill-foundrySkill
- okhp3-source-backed-researchSkill
- okhp3-thread-context-extractionSkill
- okhp3-thread-extract-chatgptSkill
- okhp3-thread-extract-claudeSkill
- okhp3-triage-and-fileSkill
- okhp3-vite-github-pagesSkill
- production-build-verificationSkill
- published-keyboard-recovery-checkSkill
- publish-health-checkSkill
- publishing-trigger-checkSkill
- static-route-validationSkill
- validation-smokeSkill
- vercel-react-best-practicesSkill
- web-design-guidelinesSkill
- okhp3-skill-promotionSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
Use a two-lane process:
- Distinctive: line 54
Do not substitute artifact-lane summaries for source-lane records.
- Distinctive: line 65
Use ChatGPT data export as the primary source when available.
- Very specific: line 70
If the account cannot export data, proceed with Browser-based recovery but mark the batch ui_capture_only and list its reduced-fidelity …
- Very specific: line 83
Create a disposable working copy under custom-gpts/ingestion/.
- Distinctive: line 123
Do not call a migration complete until all are true:
- Very specific: line 125
Every inventoried thread has a conversation_id and a disposition.
- Very specific: line 126
Every captured source has a raw_sha256 and a normalized-record hash.
- Very specific: line 128
Every unmatched thread, branch, message, or asset appears in exceptions.
- Distinctive: line 130
Every committed artifact links to a source reference, a review decision, or an explicit statement that it is an original new artifact.
- Distinctive: line 151
Use Notion only as an optional private Corpus Register for batch status, hashes, source locations, routing decisions, and review notes.
- Distinctive: line 155
When processing already captured Custom GPT material, use the existing corpus ledger and evidence-register conventions.
- Distinctive: line 192
When the user or verified target repository identifies an AskJamie or Glee-fully workflow, load only its bundled profile before applying …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
okhp3-chatgpt-project-migration
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Capture a ChatGPT project as evidence before transforming it. This skill keeps the source corpus intact, proves which threads and turns were captured, and only then routes reviewed material into durable repository artifacts.
Scope
| In scope | Out of scope |
| Exporting and indexing accessible ChatGPT project threads | Recovering deleted or permission-restricted content |
| Preserving every exported message node and content part | Treating an LLM summary as source preservation |
| Reconciling source material with repository artifacts | Publishing raw chats, credentials, or third-party private data |
| Optional Notion status register | Making Notion the authoritative raw archive |
Operating principle
Use a two-lane process:
- Source lane: immutable export, project inventory, normalized transcripts, hashes, and exception records. Keep it local and out of Git.
- Artifact lane: reviewed, classified, public-safe Markdown and structured artifacts committed to their proper repository locations.
Do not substitute artifact-lane summaries for source-lane records. A source record may be distilled many times without changing the original evidence.
Required inputs and first decision
Record the project URL, capture date, account/workspace type, intended archive location, and publication sensitivity. Treat repository visibility as unknown unless the owner has resolved it.
Use ChatGPT data export as the primary source when available. It is faster and more complete than manually copying UI text. Use Browser to enumerate the target project and verify it against the export. Use Computer only for UI actions that Browser cannot complete, such as a download dialog or desktop-only control.
If the account cannot export data, proceed with Browser-based recovery but mark
the batch ui_capture_only and list its reduced-fidelity limitations.
Capture procedure
1. Preserve the original
Store the downloaded export ZIP in an owner-controlled local archive outside the
repository. Do not rename, edit, or unpack the only copy. Calculate and record
raw_sha256 before working with it.
Create a disposable working copy under custom-gpts/ingestion/. That location
is Git-ignored, but it is a staging area, not the permanent archive.
2. Inventory the project UI
Enumerate every accessible thread in the target project. For each thread record the stable conversation ID from its URL, displayed title, project URL, observed last activity, attachments or images, and UI-capture status. Do not use title matching as the primary key.
Write project_capture_manifest.json following
references/source-manifest-schema.md. Assign each row one of: inventoried,
captured, normalized, reconciled, routed, exception.
3. Normalize without flattening
Parse every conversation record into a normalized transcript and retain the raw
JSON record. Preserve all nodes in the conversation mapping, including
regenerated alternatives and non-current branches. Do not serialize only the
current_node path.
For every message node retain: node ID, parent ID, child IDs, role, create and
update time, author metadata, content parts in order, attachments, tool or
citation metadata when present, and a source locator. Represent unavailable
fields as null; do not invent values.
4. Reconcile and recover exceptions
Match project inventory rows to normalized export records by conversation ID. Record a one-to-one match, one-to-many ambiguity, or no match. Do not silently drop unmatched rows.
For every no_match or missing asset, use Browser-based capture as the recovery
path. Preserve the URL, capture time, and reason for the exception. Keep the
exception open until it has a source record or the owner accepts the loss.
Completion gates
Do not call a migration complete until all are true:
- Every inventoried thread has a
conversation_idand a disposition. - Every captured source has a
raw_sha256and a normalized-record hash. - The parser counted all conversation
mappingnodes, not only visible turns. - Every unmatched thread, branch, message, or asset appears in
exceptions. - Raw source material remains outside tracked repository paths.
- Every committed artifact links to a source reference, a review decision, or an explicit statement that it is an original new artifact.
Report coverage as counts: threads inventoried/captured/reconciled, mapping
nodes retained, assets retained, and open exceptions. Do not claim 100%
unless the exception count is zero and the owner accepts the inventory boundary.
Integration and routing
Classify each candidate before writing to the repository:
| Class | Destination | Handling |
| Raw evidence | Local archive and ignored staging | Preserve verbatim; never commit by default |
| Historical reference | custom-gpts/proto/ or a clearly marked archive | Retain provenance and version context |
| Durable method | custom-gpts/consolidated/, docs/, or a skill | Distill, deduplicate, and cite source IDs |
| Operational artifact | Relevant schema, example, skill, or child-repo material | Add acceptance checks and ownership |
| Private or unsafe material | Local quarantine record | Redact, omit, or obtain explicit owner approval |
Use Notion only as an optional private Corpus Register for batch status, hashes, source locations, routing decisions, and review notes. Do not copy the entire source corpus into Notion merely to make it searchable.
When processing already captured Custom GPT material, use the existing corpus ledger and evidence-register conventions. Preserve disagreement and historical versions rather than making repetition appear authoritative.
Required handoff report
Return a concise report with:
Batch: <project name and capture date>
Source: export | ui_capture_only
Threads: <inventoried> inventoried / <captured> captured / <reconciled> reconciled
Nodes: <retained> retained
Assets: <retained> retained / <unavailable> unavailable
Exceptions: <count>
Artifact routing: <destinations and counts>
Owner decisions needed: <list or none>References
references/source-manifest-schema.md-- capture manifest, normalized transcript, and reconciliation record contracts.custom-gpts/ingestion/README.md-- local staging boundary for source files.custom-gpts/consolidated/CORPUS-LEDGER.md-- existing evidence-ledger model.custom-gpts/consolidated/EVIDENCE-REGISTER.md-- claim classification and source discipline.
Optional brand profiles
When the user or verified target repository identifies an AskJamie or Glee-fully workflow, load only its bundled profile before applying this shared procedure:
- AskJamie: workflow profile.
- Glee-fully: workflow profile.
For a neutral or unidentified target, use the shared procedure without a brand profile. An alias or previous package name alone does not establish the target brand. If the requested brand conflicts with the target evidence, resolve that conflict before applying a profile. Do not blend profiles or treat positioning as approved product canon. Profiles cannot weaken evidence, privacy, scope, or authorization requirements. Record the selected profile in the handoff.
Consolidation evidence
Version 1.1.0 bundles the former brand overlays as optional profiles as of 2026-09-19. Earlier evaluation designs and benchmark/results files retain their original versions and bytes as historical records; they do not validate this version or its profile selection. Profile regression cases are defined in the evaluation design and are not live runs. Structural validation is separate from behavioral or performance evidence.
About
Built by Jamie Hill · OverKill Hill P³ Published at github.com/OKHP3 Part of the OKHP3/skillz Agent Skill library. MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

