Ax Signatures For Java

Use when writing Java code with dev.axllm:ax for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.

Install

Install only this skill for Java:

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

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

Source

• Source: packages/java/skills/ax-java-signature/SKILL.md
• Version: 22.0.3

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

• Declare input and output contracts with native generated-package APIs.
• Generate JSON-schema-compatible shapes for outputs, tools, prompts, and validation.
• Keep Standard Schema and TypeScript-only helper libraries out of generated-language code.

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

import dev.axllm.ax.*;

AxSignature sig = Ax.s("question:string -> answer:string");
var schema = sig.toJsonSchema("outputs", java.util.Map.of());

Relevant API Surface

• Signatures: Ax.s, Ax.f, AxSignature
• Tools: Ax.fn, Tool

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.