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

/codex-result-handling

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

Internal guidance for presenting Codex helper output back to the user

Use this Skill: https://skilld.dev/gh/openai/codex-plugin-cc/codex-result-handling

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈23 tokens for metadata: the name and description. ≈397 when used: this file.

Description uses 1.2% 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 ≈93 characters, or 1.2%.

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.

Codex Result Handling

When the helper returns Codex output:

  • Preserve the helper's verdict, summary, findings, and next steps structure.
  • For review output, present findings first and keep them ordered by severity.
  • Use the file paths and line numbers exactly as the helper reports them.
  • Preserve evidence boundaries. If Codex marked something as an inference, uncertainty, or follow-up question, keep that distinction.
  • Preserve output sections when the prompt asked for them, such as observed facts, inferences, open questions, touched files, or next steps.
  • If there are no findings, say that explicitly and keep the residual-risk note brief.
  • If Codex made edits, say so explicitly and list the touched files when the helper provides them.
  • For codex:codex-rescue, do not turn a failed or incomplete Codex run into a Claude-side implementation attempt. Report the failure and stop.
  • For codex:codex-rescue, if Codex was never successfully invoked, do not generate a substitute answer at all.
  • CRITICAL: After presenting review findings, STOP. Do not make any code changes. Do not fix any issues. You MUST explicitly ask the user which issues, if any, they want fixed before touching a single file. Auto-applying fixes from a review is strictly forbidden, even if the fix is obvious.
  • If the helper reports malformed output or a failed Codex run, include the most actionable stderr lines and stop there instead of guessing.
  • If the helper reports that setup or authentication is required, direct the user to /codex:setup and do not improvise alternate auth flows.

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 provides operational guidelines for presenting output from an internal helper tool. It includes safety-oriented instructions that prevent automatic code modifications and ensure that the agent remains within defined boundaries during error states.

  • 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/codex-result-handling