Runtime Behavior Probe

Overview

Use this skill to investigate real runtime behavior, not to restate code or documentation. Start by planning the investigation, then execute a case matrix, record observed behavior, and report both the findings and the method used to obtain them.

Core Rules

• Treat this skill as manual-only. Do not rely on implicit invocation.
• For openai-agents-js, treat this skill as a disposable-probe workflow, not a repository implementation workflow.
• Unless the user explicitly asks for a reusable repository artifact, the allowed write scope is limited to:
  • a temporary directory used for probe scripts or artifacts
  • .agents/skills/runtime-behavior-probe/** when the user is editing this skill itself
• For disposable probes in openai-agents-js, do not modify examples/**, packages/**, any package.json, README.md, workspace config, or build config.
• If your draft plan would touch a disallowed path, stop and rewrite the plan before editing anything.
• A baseline success or smoke case is often the right entry point, but do not stop there when the real question involves edge cases, drift, or failure behavior.
• Plan before running anything. Write the case matrix first, then fill it in with observed results. The matrix can live in a scratch note, a temporary file, or the probe script header.
• Default to local or read-only probes. Consider a live service only when it is clearly relevant, then apply the lightweight gates below before you run it.
• Size the probe to the decision. Start with the smallest matrix that can disqualify or validate the current hypothesis, then expand only when uncertainty remains.