菜单
Builder-oriented guidance for the upstream `jido_messaging` package. Use when Codex needs to plan or review messaging adapters, bridge Jido signals onto external transports, or keep delivery semantics, retries, and routing boundaries explicit for Jido-based systems.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Builder-oriented guidance for the upstream `ash_jido` package. Use when Codex needs to expose Ash actions as Jido actions, wire Ash resources into agent workflows, emit or consume signals around Ash changes, or review boundary decisions between Ash domains and Jido agents.
Builder-oriented guidance for the upstream `jido_action` package. Use when Codex needs to scaffold or review `Jido.Action` modules, validate action inputs and outputs, compose actions into agent workflows, or turn action docs into runnable Elixir examples.
Builder-oriented guidance for the upstream `jido_behaviortree` package. Use when Codex needs to model agent decision trees, selectors, sequences, or fallback paths in Jido, or when it needs to turn sparse behavior-tree docs into a concrete runnable example without inventing unsupported runtime features.
Builder-oriented guidance for the upstream `jido_browser` package. Use when Codex needs to build browser-backed Jido automations, wrap navigation or extraction flows in actions, turn browser docs into runnable examples, or review `jido_browser` boundaries versus `req_llm` and app-specific scraping code.
Builder-oriented guidance for the upstream `jido_memory` package. Use when Codex needs to add memory spaces, retrieval flows, summarization or recall hooks, or review memory boundaries in Jido applications that also use `jido`, `jido_ai`, and external storage backends.
Builder-oriented guidance for the upstream `jido_otel` package. Use when Codex needs to add OpenTelemetry tracing to Jido applications, implement a tracer backend for Jido observability hooks, or review how spans, correlation ids, and exported telemetry should cross package boundaries.
| name | jido-messaging |
| description | Builder-oriented guidance for the upstream `jido_messaging` package. Use when Codex needs to plan or review messaging adapters, bridge Jido signals onto external transports, or keep delivery semantics, retries, and routing boundaries explicit for Jido-based systems. |
jido_messaging is the upstream Hex package name.
Use this skill when the task is about moving Jido signals across external transports such as queues, brokers, or pub/sub systems.
Good triggers:
jido_messaging or jido_signal."Public docs for this package are thin. Require a concrete target transport or integration before getting specific, and keep any unsupported transport behavior explicit as an assumption.
jido-signal.jido-messaging.