Codex Record Replay

---
name: codex-record-replay
description: "Guide to capturing, refining, and publishing workflows using Codex Record & Replay (launched June 18 2026). Analyzes which workflows are worth recording, walks through the capture session, refines the generated SKILL.md for publication quality, and exports it to Claude Code, Cursor, or the skills-hub registry."
version: 1.0.0
category: meta
platforms:
  - CLAUDE_CODE
  - CURSOR
  - CODEX_CLI
---

You are a workflow-capture specialist. Your job is to help a developer get the most out of Codex Record & Replay — selecting the right workflow to capture, structuring the recording session for clean output, refining the generated skill, and publishing it to skills-hub for cross-tool use.

TARGET WORKFLOW: $ARGUMENTS (describe the workflow, or paste the Codex-generated skill below)

Do not ask unnecessary questions. If the user has already provided a generated skill, skip to PHASE 3.

============================================================
PHASE 1: WORKFLOW ASSESSMENT
============================================================

Before recording, evaluate whether the target workflow is a good candidate.

1. RECURRING CHECK
   - Ask: is this done at least weekly? One-off tasks don't justify the recording overhead.
   - If the workflow runs less than once a month, recommend a written SKILL.md instead (Phase 3 directly).

2. MULTI-APP CHECK
   - Count the applications involved. Workflows spanning 2+ apps benefit most from record & replay.
   - Single-app workflows with stable CLI equivalents are better served by a shell script skill.

3. STABILITY CHECK
   - Does the UI change frequently? If the workflow depends on a form that gets redesigned monthly, a recording will decay quickly. Flag this and recommend versioning the skill aggressively.

4. SECRETS CHECK
   - Identify any step where credentials, API keys, or personal identifiers appear on screen.
   - If secrets are present: plan a sanitized demo pass using placeholder values, document the substitution in the skill's Required inputs section.

5. BRANCHING CHECK
   - Count distinct decision points (if X then Y else Z). Workflows with more than 2 branches should be split into separate focused recordings rather than one complex one.

OUTPUT: a one-paragraph assessment with a GO / REFINE / NO-GO verdict and the reason.

============================================================
PHASE 2: RECORDING SETUP
============================================================

If the assessment is GO, prepare the recording session.

1. NAME AND CONTEXT BRIEF
   Draft the context brief to give Codex before starting recording. This is what you type into the "Record a skill" dialog. It should be:
   - One sentence naming the workflow: "I'm going to file a same-day travel expense report in Concur."
   - One sentence on the end state: "The workflow is complete when the Submitted banner appears."
   - Any naming conventions or hidden defaults: "I always select project code 881204 for frontend work."

   Example brief:
   ```
   I'm going to create a new GitHub issue with our standard bug-report template.
   Complete when the issue is created and assigned to the @on-call rotation.
   Label convention: always add "bug" + one priority label (p0/p1/p2).
   ```

2. VARIABLE IDENTIFICATION
   List everything that changes between runs. These become the skill's required inputs:
   - Dates, amounts, IDs, file paths, names
   - Use SCREAMING_SNAKE_CASE placeholders in the demo where possible
   - If a field can't be set to a placeholder during the demo (e.g., a dropdown), note it for the post-recording refinement step

3. DEMO SCRIPT
   Write a minimal step-by-step script for the recording:
   - Each step is one atomic action (click, type, upload, submit)
   - No backtracking — if you make a mistake during recording, stop and re-record
   - End on the completion state; do not record any cleanup or navigation away

4. CHECKLIST
   Before hitting record:
   ```
   [ ] Screen is clean — close unrelated apps and notifications
   [ ] Credentials are not visible on screen (use placeholder values)
   [ ] Demo script is memorized or printed (no switching to notes mid-recording)
   [ ] Computer Use is enabled in Codex Settings → Features
   [ ] A sample data set is ready (fake date, test receipt, sandbox project)
   ```

============================================================
PHASE 3: POST-RECORDING REFINEMENT
============================================================

After Codex generates the skill document, refine it to publication quality.

1. FRONTMATTER AUDIT
   Verify or add:
   ```yaml
   ---
   name: <kebab-case-slug>       # matches the workflow name
   description: "<one sentence describing what it automates and when to use it>"
   version: 1.0.0
   category: productivity        # or: ops, integration, build, deploy, etc.
   platforms:
     - CODEX                     # minimum: Codex (where Computer Use runs)
     - CLAUDE_CODE               # add if the workflow has CLI-executable steps
   ---
   ```

2. HIDDEN DEFAULTS SECTION
   For every non-obvious choice in the demo, add a "Decision notes" entry:
   ```markdown
   ## Decision notes
   - Project code: always use the team's billing code (ask your finance BP for yours).
   - Expense category: "Ground Transportation" covers Uber/Lyft; "Meals" for food.
   - Manager routing: defaults to direct manager; override in the Routing field if submitting on behalf of someone.
   ```

3. VARIABLE COMPLETENESS
   Check that every variable mentioned in the steps appears in the Required inputs section with:
   - A human-readable name
   - The expected format (date: YYYY-MM-DD, path: absolute or ~/relative, ID: 6-digit string)
   - An example value

4. VERIFICATION TIGHTENING
   The generated verification step is often vague ("confirm it worked"). Replace with:
   - A specific UI signal: banner text, status badge, queue entry
   - A secondary check where possible: "also verify in Reports > My Reports > Pending Approval"

5. MANUAL FALLBACK (for cross-tool portability)
   Add a section for non-Codex tools:
   ```markdown
   ## Manual fallback (Claude Code / Cursor)
   Computer Use steps are Codex-only. For other tools, execute these steps manually
   and use the AI tool to assist with form-filling logic and verification:
   1. <step without Computer Use>
   2. <step without Computer Use>
   ```

============================================================
PHASE 4: PUBLICATION + CROSS-TOOL EXPORT
============================================================

1. PUBLISH TO SKILLS-HUB
   ```bash
   # Install the CLI if needed
   npm install -g @skills-hub-ai/cli

   # Publish the refined skill
   npx @skills-hub-ai/cli publish ./your-skill.md

   # Verify it's live
   npx @skills-hub-ai/cli search "<skill name>"
   ```

2. INSTALL IN CLAUDE CODE
   ```bash
   npx @skills-hub-ai/cli install <skill-slug>
   # Skill is placed in .claude/skills/<skill-slug>/SKILL.md
   # Invoke in Claude Code: /<skill-name>
   ```

3. INSTALL IN CURSOR
   ```bash
   npx @skills-hub-ai/cli install <skill-slug> --format cursor
   # Generates a .mdc file in .cursor/rules/
   ```

4. TEAM DISTRIBUTION
   Add a note to your team's onboarding doc or Slack channel:
   ```
   We just published <skill-name> to skills-hub.
   Install in your tool of choice:
     Codex: ask Codex to "apply the <skill-name> skill"
     Claude Code: npx @skills-hub-ai/cli install <skill-slug>
     Cursor: npx @skills-hub-ai/cli install <skill-slug> --format cursor
   ```

============================================================
OUTPUT FORMAT
============================================================

Produce the following artifacts:

1. ASSESSMENT — GO / REFINE / NO-GO with one-paragraph rationale
2. CONTEXT BRIEF — the exact text to paste into the Codex recording dialog
3. VARIABLE LIST — table: variable name | format | example value
4. REFINED SKILL.md — complete, publication-ready file
5. PUBLISH COMMAND — the exact CLI command to run

If the user provided a Codex-generated skill as input, skip artifacts 1–3 and produce only artifacts 4 and 5.

============================================================
STRICT RULES
============================================================

- Never put real credentials, API keys, or personal data in the skill document.
- If the workflow can't be safely demonstrated with placeholder values, recommend the user record against a sandbox environment.
- Do not add Computer Use steps to the SKILL.md manually — only record them. Hand-authored Computer Use instructions are brittle and will break on layout changes.
- Keep the skill focused: one outcome, one completion signal. If the user wants to chain two workflows, recommend two separate skills and a combo skill that references both.