Audio Use when writing Java code with `dev.axllm:ax` for audio input/output, OpenAI Responses audio mapping, realtime event folding, and generated package audio examples. java skills skill-audio packages/java/skills/ax-java-audio/SKILL.md skill Audio

Ax Audio And Realtime For Java

Use when writing Java code with dev.axllm:ax for audio input/output, OpenAI Responses audio mapping, realtime event folding, and generated package audio examples.

Install

Install only this skill for Java:

Shell
npx skills add https://ax-llm.github.io/ax/java/ --skill 'ax-java-audio'

Published skill file: ax-java-audio/SKILL.md.

Source

Skill Instructions

This skill helps an agent write Java code with the generated Ax package dev.axllm:ax. Use the generated package API, examples, and manifests; do not import TypeScript-only APIs unless you are editing the TypeScript package.

When To Use

  • Map speech, transcription, or realtime events through the generated provider surface.
  • Use no-key examples for event folding and provider request mapping.
  • Keep live provider calls behind explicit credentials and provider-api examples.

Package Facts

  • Language: Java.
  • Package: dev.axllm:ax.
  • Package API docs: API.md and axir-api.json.
  • Capability manifest: axir-capabilities.json.
  • Runnable examples: examples/.
  • Real network support: yes.
  • Scripted no-key transport support: yes.
  • Runtime profiles: javascript-quickjs, python-pyodide.

Core Pattern

Java
import dev.axllm.ax.*;

var llm = Ax.ai("openai", java.util.Map.of("apiKey", System.getenv("OPENAI_API_KEY")));

Relevant API Surface

  • AxAI: Ax.ai, OpenAICompatibleClient, OpenAIResponsesClient, GoogleGeminiClient, AnthropicClient, AxBalancer, MultiServiceRouter, ProviderRouter

Guardrails

  • Start from package examples for exact native syntax before inventing a new call shape.
  • Use provider-api examples only when the user explicitly has provider credentials available.
  • Use no-key examples for deterministic local checks and provider request mapping.
  • Treat AxIR as the source of generated package truth: if package docs disagree with source code, update the compiler and regenerate packages.
  • Do not copy repo-maintainer skills from tools/*/skills/ into user packages.
Docs