القائمة
Plans or scaffolds a new adapter or integration package for provider, browser, MCP, or tooling interoperability.
التثبيت باستخدام 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_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.
| name | builder-adapter-package |
| description | Plans or scaffolds a new adapter or integration package for provider, browser, MCP, or tooling interoperability. |
| license | Apache-2.0 |
| compatibility | Jido.AI >= 2.0 |
| allowed-tools | read_file write_file grep draft_package_layout map_boundaries update_docs |
| metadata | {"author":"agent-jido-workbench","version":"1.0.0","host_repo":"jido.run","intended_runtimes":"Jido.AI, jido_skill, Codex","boundary":"package repo owns adapter logic; workbench owns narrative, examples, and ecosystem inventory"} |
| tags | ["builder","adapter","integration","package"] |
Use this skill when the work is a new adapter or integration package for provider tooling, MCP, browser flows, or workbench interoperability.
