jido-action

Scaffold and validate Jido.Action modules with explicit input contracts and runnable examples.

7|Updated Mar 8, 2026

Search Tags:#documentation #validation #scaffolding #elixir #action #jido-action

Ready to run

npx skills add https://github.com/arrowcircle/jido-skills --skill jido-action

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jido-action
Source: https://github.com/arrowcircle/jido-skills/tree/main/skills/jido-action
Command: npx skills add https://github.com/arrowcircle/jido-skills --skill jido-action

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Jido.Action scaffolding and validation to ensure consistent input contracts, predictable execution, and runnable examples across agent workflows.

Core Features & Use Cases

Scaffold new Jido.Action modules with explicit input contracts and output shapes.
Validate actions for schema correctness and execution boundaries, ensuring best practices and reusability.
Turn action docs into runnable Elixir examples to illustrate usage and integration.

Quick Start

Scaffold a Jido.Action module with a clear input contract, validated outputs, and a runnable example to demonstrate usage.

Frequently Asked Questions about jido-action

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I scaffold a Jido.Action module with explicit input contracts in Elixir?▼

Scaffolding a Jido.Action module requires defining explicit input schemas and deterministic execution boundaries to ensure predictable behavior across agent workflows. This approach validates schema correctness and enforces clear separation between action logic and orchestration.

What is action validation and why do I need it for Elixir agent workflows?▼

Action validation checks schema correctness and execution boundaries to ensure consistent input contracts and reusability. It prevents unpredictable execution by requiring deterministic action logic and explicit output shapes within your agent workflows.

How do I turn Jido.Action documentation into runnable Elixir examples?▼

You can turn action documentation into runnable Elixir examples by scaffolding modules with validated input contracts and clear output shapes. This process illustrates usage and integration while ensuring the examples execute deterministically across workflows.

Can I use jido-action validation for reviewing schemas in existing Elixir actions?▼

Yes, schema validation applies to reviewing existing actions by checking input contracts and execution boundaries. It ensures best practices and reusability by validating schema correctness and maintaining clear separation between action logic and orchestration.

What are the boundaries between action logic and orchestration in Jido workflows?▼

Boundaries require explicit input schemas and deterministic execution for action logic, while orchestration remains separate. This separation ensures consistent input contracts, predictable outputs, and reusability across agent workflows within the Jido ecosystem.

Do I need explicit input schemas for every Jido.Action module I scaffold?▼

Yes, explicit input schemas are required for every scaffolded Jido.Action module. They ensure consistent input contracts, enable schema validation correctness, and support deterministic execution with clear boundaries between action logic and orchestration.