AGENT SKILL

gpt-5-4-prompting

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

License 许可
MIT
最近更新
2026-11-11
Stars
★ 33
Forks
3

01 前言 Front Matter

name
gpt-5-4-prompting
description
Internal guidance for composing Codex and GPT-5.4 prompts for coding, review, diagnosis, and research tasks inside the Codex Claude Code plugin
user-invocable
false

02 资源文件 3

03 SKILL.md 正文

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.

04 同仓库更多 Skills

KenSuh
KenSuh/open-agent-harness

typesafe-ai

Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives. Its System One models, including Jev, turn natural language and application state into typed judgments and probabilities that code can combine. Use when a feature needs programmable common sense, when brainstorming what AI could make possible in an app, or when an LLM prompt-and-parse step could become a structured decision. Applications include routing, ranking, extraction, verification, and interactive experiences; these are starting points, not the limits. Read live docs and cookbooks to find useful patterns and discover new combinations.

★ 33
KenSuh
KenSuh/open-agent-harness

skill-creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

★ 33
KenSuh
KenSuh/open-agent-harness

ponytail

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

★ 33
KenSuh
KenSuh/open-agent-harness

ponytail-review

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.

★ 33
KenSuh
KenSuh/open-agent-harness

ponytail-help

Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".

★ 33
KenSuh
KenSuh/open-agent-harness

ponytail-gain

Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".

★ 33