CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-java-gen

Use when writing Java code with `dev.axllm:ax` for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/java/skills/ax-java-gen/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Weight 40%Scale 1-5

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

The body is an information-dense API reference with accurate, package-specific detail, but it is organized as a monolithic wall of prose: one code example, no sequenced workflows or validation checkpoints, and provider-specific material that should live in separate reference files. The knowledge is valuable; the structure wastes it.

Suggestions

Split per-provider sections (OpenAI Decisions, Gemini Decisions, Astra Session Work) into one-level-deep reference files under references/ and keep SKILL.md as a concise overview with clearly signaled links.

Add a few complete, executable Java examples (a basic AxGen forward, a tool attachment, a streaming forward with try-with-resources) instead of describing the call shapes in prose.

Tighten the run-on paragraphs: state each option once with its preferred spelling, and replace the repeated 'as in TypeScript' qualifiers with a single note that the Java API mirrors TypeScript unless stated otherwise.

DimensionReasoningScore

Conciseness

Almost every fact is package-specific behavior Claude would not know, so there is little padding — but the body is dominated by 100+ word run-on paragraphs (e.g. the streamingForward, cachingFunction, and parseDates sections), roughly twenty repeated "as in TypeScript" qualifiers, and dual-spelling option listings ("maxSteps / max_steps") that could be substantially tightened. This sits between 'noticeably verbose' (2) and 'efficient' (4): the material is dense rather than padded, but well beyond 'minor instances' of trimming.

3 / 5

Actionability

Option names, defaults, error messages, and method signatures are stated concretely (e.g. "maxSteps / max_steps (default 25)", "Generate failed: Max steps reached: N"), but only one small code snippet (the three-line Core Pattern) appears in ~140 lines; the rest describes API behavior rather than giving executable Java the agent can copy. This is more concrete than pseudocode-level guidance (anchor 3's example) but falls short of 'mostly executable guidance with minor gaps' (4).

3 / 5

Workflow Clarity

Sections are coherent and the 'When To Use' bullet list plus 'Guardrails' give orientation, but no multi-step process is ever sequenced and no validation checkpoints or feedback loops appear anywhere — e.g. 'Start from package examples for exact native syntax' is a pointer, not a step with a check. The document is a reference, not a workflow, which fits anchor 3's 'sequence present but checkpoints missing' level at best.

3 / 5

Progressive Disclosure

Section headers exist and referenced materials (API.md, axir-capabilities.json, examples/) are named, but those paths belong to the generated package, not to a skill bundle — no references/, scripts/, or assets/ directories exist. A ~30KB monolith inlines whole per-provider topics (OpenAI Decisions, Gemini Decisions, Astra Session Work) that clearly belong in one-level-deep reference files, matching anchor 3: 'content that should be separate is inline' with structure present.

3 / 5

Total

12

/

20

Passed

Description

92%Weight 40%Scale 1-5

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: it names the exact package, lists its concrete capabilities, and gives an explicit 'Use when' trigger in a single tight sentence. The only weakness is missing a few natural synonym phrases such as 'structured generation' that users might say.

DimensionReasoningScore

Specificity

The description enumerates many concrete capability areas — "AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing" — giving comprehensive coverage of the package surface rather than generic language.

5 / 5

Completeness

An explicit trigger clause ("Use when writing Java code with `dev.axllm:ax` for…") answers 'when' with concrete trigger conditions, and the enumerated capability list clearly answers 'what' the skill covers.

5 / 5

Trigger Term Quality

Good keyword coverage with terms a user of this package would naturally say ("Java", "AxGen", "dev.axllm:ax", "streaming", "tools"), but a few natural variations are missing — notably "structured generation", "Ax", or "LLM" phrasing that the body's own title uses.

4 / 5

Distinctiveness Conflict Risk

The description is pinned to one specific artifact (the generated Java package `dev.axllm:ax`) and its named features, so it occupies a clear niche with minimal risk of triggering for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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-gen/SKILL.md

Reviewed

Table of Contents

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.