Help us improve
Share bugs, ideas, or general feedback.
Use when Codex needs to get a deep ChatGPT/GPT Pro review, audit, proposal, implementation plan, risk assessment, or strategy analysis for any project by serving curated context through a temporary HTTPS text endpoint and interacting with chatgpt.com via Browser Use. Triggers include requests to package context for GPT Pro, ask Pro to analyze a codebase/system/document set, serve project context from a reachable host, monitor a Pro response, or follow up with Pro using browser automation.
npx claudepluginhub adrianleb/gpt-pro-context-handoff-skill --plugin gpt-pro-context-handoffHow this skill is triggered — by the user, by Claude, or both
Slash command
/gpt-pro-context-handoff:gpt-pro-context-handoffThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Lead with **plain readable text over HTTPS**, not ZIP upload and not ZIP-primary links.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Lead with plain readable text over HTTPS, not ZIP upload and not ZIP-primary links.
ZIP files, tarballs, and large archives are backup artifacts only. The reliable handoff is a .txt or .md context file that GPT Pro can browse/fetch/read directly, with optional evidence links for deeper material.
HTTP 200 on an archive as proof GPT Pro read it. Confirm by the visible response and, when available, server logs for the plaintext context.Before touching the browser, write down the task in operational terms:
Preserve the user's framing for the current domain. Do not silently replace a project-specific goal with generic advice, and do not turn an execution request into a broad strategy memo unless that is what the user asked for.
Create one primary file named like:
gpt-pro-context-YYYYMMDDTHHMMSSZ.txt
Make it self-contained enough that GPT Pro can start without downloading archives. Include:
REQUEST: exact desired analysis/proposal format.PROJECT ORIENTATION: project purpose, repo/path, runtime, architecture, important components, and glossary terms GPT Pro needs.CURRENT STATE: current status, metrics, incidents, open blockers, deployment/runtime state, or other domain-specific facts relevant to the request.RECENT CHANGES: what changed since the last review and what was verified.EVIDENCE INDEX: HTTPS links to text mirrors first; optional archive links second.KEY FILE EXCERPTS: concise excerpts or full contents for the most relevant source, prompts, configs, docs, and test output.RAW OUTPUTS: command output, logs, data summaries, status snapshots, and other request-relevant evidence.QUESTIONS FOR GPT PRO: direct, ranked questions.CONSTRAINTS: what not to suggest, compatibility requirements, dependencies that must remain enabled, risk posture, timing, and decision criteria.Choose evidence for the current project rather than following a fixed domain checklist. Good inputs often include architecture docs, README files, key source files, prompts, schema or API definitions, config excerpts, test output, logs, diffs, performance traces, incident timelines, screenshots rendered to text descriptions, and prior decisions.
Do not include secrets. Redact keys, tokens, private keys, session cookies, production credentials, proprietary customer data, and private personal data. Prefer summaries over dumping secret-bearing config files.
Use a user-approved or workspace-appropriate HTTPS host. If no host is already available, create a random-token directory on a reachable host or local tunnel that can serve static plaintext over HTTPS.
Requirements:
Content-Type: text/plain; charset=utf-8 for .txt;Accept-Ranges: bytes for large optional artifacts;curl -I from local machine returns 200;curl of the plaintext URL returns readable text;404.Do not assume any host, path convention, account, repository, deployment environment, or organization-specific workflow.
Archive links may be listed below the text URL, but mark them optional.
Open or reuse chatgpt.com with Browser Use. Select GPT Pro/Extended Pro if available.
Prompt shape:
Please browse/fetch and read this plaintext project context first:
<TEXT_CONTEXT_URL>
Use it as the evidence of record for <specific requested review/audit/proposal>.
If any linked artifact is unavailable, say exactly which URL failed and continue from the plaintext context. Use optional archive links only if you need rawer context.
Focus on <user goal>. Be direct, cite evidence from the context, identify missing evidence, and produce prioritized actions with expected impact, risk, effort, confidence, and verification steps.
If the project has strong constraints, state them explicitly in the prompt. Example:
Do not recommend a rewrite unless the context shows a concrete blocker that cannot be solved incrementally. Rank proposals by impact, effort, risk, confidence, and how each would be verified in this project.
After sending:
.txt follow-up file, not another ZIP attempt.When Pro finishes:
If continuing the same Pro thread, use follow-up plaintext files for corrected data, diffs, or compact patch bundles.
# GPT Pro Context Handoff
Created UTC: <timestamp>
Project: <name/path/repo/host>
Primary goal: <goal>
Domain: <product/domain/system type>
## REQUEST
<exact output wanted from GPT Pro>
## USER CONSTRAINTS
- <constraint>
- <constraint>
## PROJECT ORIENTATION
<purpose, architecture, runtime, key components, glossary, important paths>
## CURRENT STATE
<status, metrics, blockers, deployment/runtime state, recent behavior, open risks>
## VERIFIED FACTS
- <fact with command/source>
## RECENT CHANGES AND TESTS
<git diff summary, rollout status, test commands/results>
## EVIDENCE INDEX
Primary plaintext context:
- <this URL>
Additional plaintext evidence:
- <URL>
Optional archives only if needed:
- <URL>
## KEY SOURCE AND PROMPT EXCERPTS
<paths + excerpts or full relevant files>
## RAW OUTPUTS
<CLI/API/DB/log outputs>
## QUESTIONS FOR GPT PRO
1. <question>
2. <question>
## FAILURE MODES TO CHECK
- <risk>
- <risk>
## OUT OF SCOPE
- <thing GPT Pro should not spend time on>
gpt-pro-context-followup-<stamp>.txt with the exact missing content.curl.curl.