Thin Codex skill shim for node_adversarial_pipeline_orchestrator. Use when running the adversarial plan-to-ticket pipeline through runtime truth.
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./plugins/onex/skills/adversarial-pipeline/SKILL.mdThis skill is a thin Codex runtime adapter shim over the OmniMarket
node_adversarial_pipeline_orchestrator node. The node owns design-to-plan,
hostile-review gating, and ticket creation orchestration. Do not add background
agent CLI calls, Linear API calls, handler imports, or local pipeline logic to
this skill.
This section is generated from the Codex adapter contract and the target node contract. Keep the two surfaces distinct:
adversarial_pipeline_orchestratorscripts/run_codex_runtime_request.pyonex.cmd.omnimarket.pattern-b-dispatch.v1onex.evt.omnimarket.pattern-b-dispatch-completed.v1--compile-only to validate the request and binding
without publishing an event or starting a runtime. This is adapter preflight,
not evidence that a target runtime executed the command.runtime_evidence.runtime_observation and
runtime_evidence.adapter_dispatch_binding; compile-only is UNOBSERVED
with reason compile_only.runtime_evidence.schema_version is
runtime-evidence/v2; v2 requires runtime_observation and carries the
resolved node contract under adapter_dispatch_binding.node_contract.adapter_dispatch_binding reports
adapter_command_topic, requested_response_topic,
selected_terminal_topic, and terminal_selection (NODE_CONTRACT,
DIRECT_DELEGATE_SKILL_CONTRACT, or EXPLICIT_RESPONSE_OVERRIDE); its
node_contract is the resolved, typed contract binding.node_adversarial_pipeline_orchestratornode_adversarial_pipeline_orchestratoronex.cmd.omnimarket.adversarial-pipeline-start.v1onex.evt.omnimarket.adversarial-pipeline-completed.v1The skill must use the request wrapper for dispatch. It must not publish the target node command topic directly as its generic adapter transport; the target topics above are contract metadata selected by the runtime adapter.
| Argument | Description | Default |
|---|---|---|
topic | Design topic or problem statement | Required |
plan_path | Existing plan path; skips design stage when set | Omitted |
min_findings_gate | Minimum hostile-review findings required | 3 |
linear_project | Refused when set: new tickets are created in the Backlog with no project (OMN-17427) | Omitted |
no_launch | Skip browser launch in design stage | false |
dry_run | Run without creating tickets | false |
target_runtime_address | Optional runtime://... runtime target | Uses ONEX_TARGET_RUNTIME_ADDRESS when set |
Run from the omnimarket repo or an omnimarket worktree:
env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py \
--command-name "adversarial_pipeline_orchestrator" \
--payload '<json-payload>' \
--timeout-ms 300000If the user supplies a runtime://... target, add
--target-runtime-address '<runtime-address>' to the request command. If the
argument is omitted, the wrapper uses ONEX_TARGET_RUNTIME_ADDRESS when set.
For event-bus-free preflight, add --compile-only. This validates the payload,
command topic, response topic, correlation id, timeout, and target runtime
address without publishing to Kafka or starting a runtime.
Map user inputs into a JSON payload using the same field names:
topicplan_pathmin_findings_gatelinear_projectno_launchdry_runIf ok is true and output_payloads is present, treat output_payloads[0]
as the primary node result.
If ok is false, surface error.code and error.message directly. A
node_not_implemented response is the current explicit stop state, not
permission to call legacy agent or Linear paths from this skill.
src/omnimarket/nodes/node_adversarial_pipeline_orchestrator/scripts/run_codex_runtime_request.pyadversarial_pipeline_orchestratoronex.cmd.omnimarket.adversarial-pipeline-start.v1onex.evt.omnimarket.adversarial-pipeline-completed.v1Prefer output_payloads[0]. Render stage_reached, gate_passed,
findings_count, tickets_created, and any created ticket identifiers. All
pipeline behavior is owned by node_adversarial_pipeline_orchestrator.
OmniNode-ai/omnimarket
13a7e30
Also appears in
since Nov 7, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.