Thin Codex skill shim for node_local_review. Use to run the OmniMarket local review loop through the runtime adapter.
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/local-review/SKILL.mdThis skill is a thin Codex runtime adapter shim over the OmniMarket
node_local_review node. The node owns the review, fix, commit,
clean-check, and completion loop. Do not add review heuristics, file scanning,
fix logic, commit logic, or shell loops to this skill.
This section is generated from the Codex adapter contract and the target node contract. Keep the two surfaces distinct:
local_reviewscripts/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_local_reviewlocal_reviewonex.cmd.omnimarket.local-review-start.v1onex.evt.omnimarket.local-review-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 |
|---|---|---|
correlation_id | UUID v4 correlation id for the review run | Generate when omitted |
max_iterations | Maximum review-fix cycles before stopping | 10 |
required_clean_runs | Consecutive clean runs required before done | 2 |
dry_run | Run without side effects | false |
requested_at | ISO-8601 request timestamp | Current UTC time |
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 "local_review" \
--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.
Build the payload with this shape:
{
"correlation_id": "<uuid-v4>",
"max_iterations": 10,
"required_clean_runs": 2,
"dry_run": false,
"requested_at": "<utc-iso-8601-timestamp>"
}Map user inputs into the same field names. Generate correlation_id and
requested_at when the user does not supply them.
If 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.
src/omnimarket/nodes/node_local_review/scripts/run_codex_runtime_request.pylocal_reviewonex.cmd.omnimarket.local-review-start.v1onex.evt.omnimarket.local-review-completed.v1Prefer output_payloads[0]. Render final_phase, iteration_count,
issues_found, issues_fixed, and error_message. For dry runs, report the
planned review-loop state without inventing findings or fixes.
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.