Skip to main content

agentjido/jido_run

SkillsMP has collected 23 skills from agentjido/jido_run. Open a skill to review its source and details.

Latest recorded source activity
SkillsMP catalog refreshed
skills collected
23
GitHub stars
49
GitHub forks
21

Skills in this repository

3 occupation categories · 100% classified

Showing 23 of 23 collected skills.

occupation
Software Developers
description

Builder-oriented guidance for the upstream `llm_db` package. Use when Codex needs to model provider and model catalogs, select models by capability or price, wire catalog lookups into Elixir code, or review `llm_db` boundaries versus `req_llm`, `jido`, and…

updated
occupation
Software Developers
description

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…

updated
occupation
Software Developers
description

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.

updated
occupation
Software Developers
description

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…

updated
occupation
Software Developers
description

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…

updated
occupation
Software Developers
description

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…

updated
occupation
Software Developers
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…

updated
occupation
Software Developers
description

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…

updated
occupation
Software Developers
description

Builder-oriented guidance for the upstream `jido_signal` package. Use when Codex needs to define signal schemas, route or dispatch events, bridge Jido signals to buses or transports, or review `jido_signal` boundaries versus `jido`, `jido_messaging`, and…

updated
occupation
Software Developers
description

Builder-oriented guidance for the upstream `jido` package. Use when Codex needs to design or review Jido agents, directives, action pipelines, runtime loops, or example applications that compose `jido_action`, `jido_signal`, memory, and AI-facing packages…

updated
occupation
Software Developers
description

Meta-skill for routing Jido ecosystem work to the right package skills. Use when Codex needs to choose between $jido, $jido-action, $jido-signal, $req-llm, $llm-db, $ash-jido, $jido-browser, $jido-memory, $jido-behaviortree, $jido-messaging, $jido-otel, or…

updated
occupation
Software Developers
description

Builder-oriented guidance for the upstream `jido_studio` package. Use when Codex needs to plan or review Jido operator tooling, workbench pages, demos, or Studio-facing integrations, especially when turning ecosystem package material into concrete examples…

updated
occupation
Software Developers
description

Builder-oriented guidance for the upstream `req_llm` package. Use when Codex needs to configure providers, shape LLM requests, implement streaming or structured outputs, or review `req_llm` boundaries versus `llm_db`, `jido`, and `jido_ai`.

updated
occupation
Software Developers
description

Scaffolds a new Jido.Action with schema, tests, and workbench follow-up notes for ecosystem contributors.

updated
occupation
Software Developers
description

Plans or scaffolds a new adapter or integration package for provider, browser, MCP, or tooling interoperability.

updated
occupation
Software Developers
description

Scaffolds a new Jido or Jido.AI agent with strategy, runtime policy, and workbench documentation follow-up.

updated
occupation
Web Developers
description

Authors or updates a workbench ecosystem package page with boundaries, features, limitations, and companion links.

updated
occupation
Software Developers
description

Turns package source material into a runnable example or tutorial plan for the workbench.

updated
occupation
Software Developers
description

Reviews a Jido ecosystem package for boundaries, dependencies, testing gaps, and missing workbench documentation.

updated
occupation
Software Developers
description

Scaffolds a Jido plugin with signal routes, actions, and docs notes for workbench consumers.

updated
occupation
Software Developers
description

Converts temperature and distance inputs for the deterministic multi-skill orchestration demo.

updated
occupation
Software Developers
description

Reviews changed files for correctness, safety, and test gaps in the skills runtime demo.

updated
occupation
Technical Writers
description

Drafts concise release notes from a list of validated changes in the skills runtime demo.

updated
Showing 23 of 23 collected skills.