Ax Signatures For Go

Use when writing Go code with github.com/ax-llm/ax/go for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.

Install

Install only this skill for Go:

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

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

Source

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

Skill Instructions

This skill helps an agent write Go code with the generated Ax package github.com/ax-llm/ax/go. 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: Go.
• Package: github.com/ax-llm/ax/go.
• 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-goja.

Core Pattern

import ax "github.com/ax-llm/ax/go"

sig := ax.NewSignature("question:string -> answer:string")
schema := sig.ToJSONSchema(nil)

Relevant API Surface

• Signatures: axllm.S, axllm.FieldType, axllm.AxSignature
• Tools: axllm.Fn, axllm.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.