Index of every page on this site: llms.txt
All skills
openai avatar

/gpt-5-4-prompting

@db52e28
by openaiopenai/codex-plugin-cc35k stars
2,453
Run it yourself

Internal guidance for composing Codex and GPT-5.4 prompts for coding, review, diagnosis, and research tasks inside the Codex Claude Code plugin

Use this Skill: https://skilld.dev/gh/openai/codex-plugin-cc/gpt-5-4-prompting

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈41 tokens for metadata: the name and description. ≈858 when used: this file. ≈2.5k more on demand in 3 files.

Description uses 2.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈163 characters, or 2.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

GPT-5.4 Prompting

Use this skill when codex:codex-rescue needs to ask Codex or another GPT-5.4-based workflow for help.

Prompt Codex like an operator, not a collaborator. Keep prompts compact and block-structured with XML tags. State the task, the output contract, the follow-through defaults, and the small set of extra constraints that matter.

Core rules:

  • Prefer one clear task per Codex run. Split unrelated asks into separate runs.
  • Tell Codex what done looks like. Do not assume it will infer the desired end state.
  • Add explicit grounding and verification rules for any task where unsupported guesses would hurt quality.
  • Prefer better prompt contracts over raising reasoning or adding long natural-language explanations.
  • Use XML tags consistently so the prompt has stable internal structure.

Default prompt recipe:

  • <task>: the concrete job and the relevant repository or failure context.
  • <structured_output_contract> or <compact_output_contract>: exact shape, ordering, and brevity requirements.
  • <default_follow_through_policy>: what Codex should do by default instead of asking routine questions.
  • <verification_loop> or <completeness_contract>: required for debugging, implementation, or risky fixes.
  • <grounding_rules> or <citation_rules>: required for review, research, or anything that could drift into unsupported claims.

When to add blocks:

  • Coding or debugging: add completeness_contract, verification_loop, and missing_context_gating.
  • Review or adversarial review: add grounding_rules, structured_output_contract, and dig_deeper_nudge.
  • Research or recommendation tasks: add research_mode and citation_rules.
  • Write-capable tasks: add action_safety so Codex stays narrow and avoids unrelated refactors.

How to choose prompt shape:

  • Use built-in review or adversarial-review commands when the job is reviewing local git changes. Those prompts already carry the review contract.
  • Use task when the task is diagnosis, planning, research, or implementation and you need to control the prompt more directly.
  • Use task --resume-last for follow-up instructions on the same Codex thread. Send only the delta instruction instead of restating the whole prompt unless the direction changed materially.

Working rules:

  • Prefer explicit prompt contracts over vague nudges.
  • Use stable XML tag names that match the block names from the reference file.
  • Do not raise reasoning or complexity first. Tighten the prompt and verification rules before escalating.
  • Ask Codex for brief, outcome-based progress updates only when the task is long-running or tool-heavy.
  • Keep claims anchored to observed evidence. If something is a hypothesis, say so.

Prompt assembly checklist:

  1. Define the exact task and scope in <task>.
  2. Choose the smallest output contract that still makes the answer easy to use.
  3. Decide whether Codex should keep going by default or stop for missing high-risk details.
  4. Add verification, grounding, and safety tags only where the task needs them.
  5. Remove redundant instructions before sending the prompt.

Reusable blocks live in references/prompt-blocks.md. Concrete end-to-end templates live in references/codex-prompt-recipes.md. Common failure modes to avoid live in references/codex-prompt-antipatterns.md.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill is a collection of internal prompt engineering guidelines and templates. It provides structured XML-based patterns for composing tasks for large language models, focusing on clarity, grounding, and verification loops. No security issues were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at db52e28. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 8 months ago
user-invocable
false

README badge

README badge for openai/codex-plugin-cc/gpt-5-4-prompting