req-llm

Configure Req_llm provider adapters for Elixir-based LLM calls.

48|21|Updated Jan 25, 2025
One-click install
npx skills add https://github.com/agentjido/jido_run --skill req-llm-agentjido
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: req-llm
Source: https://github.com/agentjido/jido_run/tree/main/priv/skills/arrowcircle-jido-skills/skills/req-llm
Command: npx skills add https://github.com/agentjido/jido_run --skill req-llm-agentjido

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides builder-oriented guidance for configuring and using the ReqLLM Elixir package, helping developers set up provider adapters, shape LLM requests, enable streaming or structured outputs, and reason about boundaries with related projects like llm_db, jido, and jido_ai.

Core Features & Use Cases

  • Configure providers cleanly and separate API keys, base URLs, and defaults at the edge.
  • Build model invocation flows for one-shot, streaming, and tool-enabled calls with explicit request shaping and error handling.
  • Turn docs into runnable examples and clarify package boundaries among req_llm, llm_db, jido, and jido_ai.

Quick Start

Configure a basic ReqLLM provider with a minimal one-shot Elixir example to illustrate provider adapter usage.

Frequently Asked Questions about req-llm

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

FAQPage Schema
How do I configure Elixir LLM provider adapters for streaming and synchronous calls?

Configure Elixir LLM provider adapters by separating API keys, base URLs, and defaults at the edge to standardize synchronous, asynchronous, and streaming model invocations while keeping request shaping portable and testable.

What is the best way to handle provider differences when making LLM calls in Elixir?

Handle provider differences in Elixir LLM calls by enforcing strict separation of concerns across provider transport, request shaping, and response normalization, ensuring implementations remain portable across different LLM providers.

Does req_llm work with jido and jido_ai for building agentic workflows?

ReqLLM works alongside jido, jido_ai, and llm_db by clarifying package boundaries, ensuring provider transport, request shaping, and response normalization do not overlap with agentic or database responsibilities.

How do I set up a basic one-shot LLM request using ReqLLM in Elixir?

Set up a basic one-shot LLM request in Elixir by configuring a minimal ReqLLM provider adapter with explicit request shaping and error handling to execute a single synchronous model invocation.

Can I use ReqLLM for structured outputs and tool-enabled calls in Elixir?

Use ReqLLM to build model invocation flows for tool-enabled calls and structured outputs in Elixir, applying explicit request shaping and error handling for both streaming and one-shot scenarios.

When should I separate provider transport from response normalization in Elixir LLM applications?

Separate provider transport from response normalization when configuring Elixir LLM applications to ensure implementations remain portable and testable across synchronous, asynchronous, and streaming invocation scenarios.