agentjido
30 verified skills5,636 total stars
pr-review
Review a Pull Request for code quality, tests, merge conflicts, and readiness to merge.
development1,599
hex-release
Guides interactive Hex package release for AgentJido repos. Supports automated (GitHub Actions workflow_dispatch) and manual release flows. Uses git_ops for version bumping and changelog generation. Triggers on: release, hex publish, bump version, new release, publish package.
documentation1,599
pr-review
Review a Pull Request for code quality, tests, and merge readiness. Use when reviewing PRs, checking for merge conflicts, or providing feedback before merging.
development484
pr-harden
Take a pull request labeled needs_work, address blocking review findings, strengthen test coverage, rerun validation, and flip it to ready_to_merge when it is clean.
testing484
hex-release
Guides interactive Hex package release for AgentJido repos. Supports automated (GitHub Actions workflow_dispatch) and manual release flows. Uses git_ops for version bumping and changelog generation. Triggers on: release, hex publish, bump version, new release, publish package.
documentation168
unit-converter
Converts between common units of measurement including temperature, distance, and weight.
tools168
code-review
Reviews code changes for quality, security, and best practices.
development168
demo-code-review
Reviews changed files for correctness, safety, and test gaps in the skills runtime demo.
development42
demo-release-notes
Drafts concise release notes from a list of validated changes in the skills runtime demo.
testing42
jido
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 into working Elixir systems.
development42
jido-action
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.
development42
jido-memory
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.
development42
jido-signal
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 application code.
development42
jido-studio
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 without over-claiming undocumented UI capabilities.
tools42
builder-action-scaffold
Scaffolds a new Jido.Action with schema, tests, and workbench follow-up notes for ecosystem contributors.
development42
builder-agent-scaffold
Scaffolds a new Jido or Jido.AI agent with strategy, runtime policy, and workbench documentation follow-up.
development42
llm-db
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 `jido_ai`.
development42
jido-messaging
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.
development42
jido-browser
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.
tools42
jido-behaviortree
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.
development42
jido-otel
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.
development42
req-llm
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`.
development42
jido-skill-router
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 $jido-studio, or when a task spans several of them and needs a handoff order.
development42
builder-adapter-package
Plans or scaffolds a new adapter or integration package for provider, browser, MCP, or tooling interoperability.
tools42
demo-unit-converter
Converts temperature and distance inputs for the deterministic multi-skill orchestration demo.
tools42
ash-jido
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.
development42
builder-ecosystem-page-author
Authors or updates a workbench ecosystem package page with boundaries, features, limitations, and companion links.
development42
builder-example-tutorial-author
Turns package source material into a runnable example or tutorial plan for the workbench.
development42
builder-package-review
Reviews a Jido ecosystem package for boundaries, dependencies, testing gaps, and missing workbench documentation.
development42
builder-plugin-scaffold
Scaffolds a Jido plugin with signal routes, actions, and docs notes for workbench consumers.
tools42