OmniNode-ai /onex:plan_to_tickets — one command, one typed result
Skill ID: onex:plan_to_tickets · Command: uv run onex skill plan_to_tickets (omnibase_infra) · Backing node: node_plan_to_tickets (omnimarket)
A dispatch skill IS one CLI call. Payload construction, node dispatch, and
result extraction all live in the onex skill entrypoint (declarative
skill_mapping.yaml registry) — there is no procedure to learn here. The
command prints exactly one typed ModelSkillResult[ModelPlanToTicketsResult] JSON to
stdout carrying the FULL handler result; RuntimeLocal logs and intermediate
context go to a capture file + the artifact store, never to you.
See prompt.md for the one command and how to present the typed result.
What this skill does NOT do
- Construct a payload file,
cdanywhere, orcata workflow_result.json (all internal toonex skill) - Run any inline scan, probe, or orchestration — the backing node owns all logic
- Contain executable logic in this directory — markdown only
Related
- CLI entrypoint:
omnibase_infra/src/omnibase_infra/cli/cli_skill.py - Skill→node mapping:
omnibase_infra/src/omnibase_infra/cli/skill_mapping.yaml - Result model:
omnimarket.nodes.node_plan_to_tickets.handlers.handler_plan_to_tickets.ModelPlanToTicketsResult