ax-java-signature

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

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, highly actionable, and clearly structured for a single-purpose code-generation skill. The main weakness is progressive disclosure: it leans on referenced files (API.md, axir-api.json, examples/) that are not bundled alongside the skill.

Suggestions

Ship the referenced materials (API.md, axir-api.json, axir-capabilities.json, and an examples/ directory) as bundle files under references/ or assets/ so the one-level-deep navigation is actually present.

Add a short pointer in the body to where each referenced file lives in the bundle (e.g., 'See references/API.md') so the path is explicit rather than implicit.

If bundle files are intentionally omitted, note that the API surface is documented inline in 'Relevant API Surface' to make the skill self-sufficient.

Dimension	Reasoning	Score
Conciseness	Lean throughout — short one-line intros followed by tight code blocks, assuming Claude's competence without explaining Java or JSON schema; every section earns its tokens.	3 / 3
Actionability	Provides fully executable Java code (Ax.s, toJsonSchema, the fluent Ax.f().call() builder, Ax.ax(signature)) plus an explicit 'Relevant API Surface' symbol list, all copy-paste ready.	3 / 3
Workflow Clarity	A single-purpose code skill with a clear When-To-Use → Core Pattern → More Patterns → Guardrails progression and explicit guidance to start from `examples/`; no destructive/batch operation requires validation checkpoints, so the clear organization scores 3.	3 / 3
Progressive Disclosure	Sections are well-organized and external materials (API.md, axir-api.json, examples/) are signaled one level deep in Package Facts, but those referenced files are not present in the provided bundle, so the navigation/splitting cannot be fully verified.	2 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: specific, third-person, with an explicit 'Use when' trigger and a clear package-anchored niche. It answers what and when concisely without padding.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes' — beyond just naming the domain, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (writing Java code with `dev.axllm:ax` for the listed capabilities) and when via the present 'Use when...' clause, satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Includes natural developer phrasing ('writing Java code', 'string signatures', 'JSON schema output', 'validation') anchored to the concrete package coordinate `dev.axllm:ax`, giving good coverage of terms users would say.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to a specific generated package and language (`dev.axllm:ax`, Java), giving it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: ax-llm/ax
Path: packages/java/skills/ax-java-signature/SKILL.md
Commit: fe8baf8

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.