CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-java-typesafe

Use when writing Java code with `dev.axllm:ax` for Typesafe Jev image inputs, boolean/class/rubric score/box signatures, decision evidence and provenance, native Noul/Choice/Score/Box, structured criteria and hybrid generation.

Quality

70%

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-typesafe/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 a dense, factually rich API reference with good section organization, a correct executable core pattern, and useful guardrails, but it behaves as a monolithic dump of constraint detail rather than a navigable skill. It would score substantially higher by splitting reference material into real bundle files and leading with runnable examples for each major operation.

Suggestions

Move the constraint catalogs (probability validation tolerances, byte/pixel limits, key-format rules, the full API surface list) into a reference file in references/ and keep SKILL.md as an overview with one-level-deep, clearly signaled links.

Add small complete Java examples inline for the major operations beyond the basic pattern — evidence-bearing decisions, image localization, and the two-program hybrid — instead of only deferring to src/examples/java/generation/.

Give multi-step tasks (e.g., reranking: define score rubric, evaluate pairs, sort by relevance.value) an explicit numbered sequence with a validation checkpoint so the workflow is followable without reading prose paragraphs.

DimensionReasoningScore

Conciseness

The body avoids explaining known concepts, but it inlines exhaustive constraint detail ("sum to one within an inclusive 0.01 tolerance", "16 MiB per decoded image, 32 MiB per request", pixel ranges, balancer propagation rules, a ~60-symbol API surface list) that is more than minor trimmable over-explanation. Anchor 3 fits: mostly efficient but could be tightened considerably by moving reference-grade detail out.

3 / 5

Actionability

One complete executable snippet exists (the Core Pattern) plus concrete inline signature syntax like `boolean(true "Core task blocked", false "Routine request")`, but most operations (image localization, native criteria, two-program hybrid) have no complete example and are deferred to src/examples/java/generation/. Anchor 3: concrete guidance present but incomplete; not 4 because the gaps are not minor.

3 / 5

Workflow Clarity

The content is a topic-organized API reference rather than a sequenced workflow; the core pattern (model, signature, forward) is unambiguous, but multi-part tasks like reranking, localization, and hybrid generation have no step sequence or validation checkpoints. Anchor 3 fits: organized and coherent but without explicit checkpoints; not 2 because nothing is incoherent or missing a rough order.

3 / 5

Progressive Disclosure

Sections are clearly headered, but all reference-grade material (the full API surface list, Google Gemini Decisions details, constraint catalogs) is inlined monolithically, and the referenced files (API.md, axir-api.json, axir-capabilities.json, examples/) do not exist in the bundle. Anchor 3 fits: structure present but content that should be split into separate files is inline; not 2 because section organization is solid, not 4 because references are neither real bundle files nor clearly signaled.

3 / 5

Total

12

/

20

Passed

Description

78%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, highly targeted description with an explicit 'Use when' trigger and a concrete enumeration of the package's capability areas. Its weaknesses are the feature-noun phrasing instead of explicit actions and missing coverage of the Gemini/OpenAI decisions providers that the body documents.

Suggestions

State the skill's function as an explicit third-person action (e.g., 'Guides writing Java code with...') so the 'what' is stated rather than implied by a feature list.

Mention the google-gemini-decisions and openaiDecisions providers covered in the body so trigger coverage matches actual skill scope.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ("Typesafe Jev image inputs", "boolean/class/rubric score/box signatures", "decision evidence and provenance", "native Noul/Choice/Score/Box", "structured criteria and hybrid generation") rather than generic language. Not a 5 because these are feature nouns rather than explicit actions, and providers covered in the body (google-gemini-decisions, openaiDecisions) are omitted.

4 / 5

Completeness

Explicitly answers 'when' with "Use when writing Java code with `dev.axllm:ax` for..." and the 'what' is conveyed through the enumerated feature areas. Not a 5 because the 'what' is a feature list implying coverage rather than a clear explicit statement of what the skill does.

4 / 5

Trigger Term Quality

Contains natural terms a user of this package would say ("Java code", "Typesafe", "Jev", "dev.axllm:ax", "signatures", "criteria") with good coverage of the domain vocabulary. Not a 5 because common synonyms and variations ("axllm", "AxGen", "Gemini decisions", "OpenAI decisions") are missing.

4 / 5

Distinctiveness Conflict Risk

The package coordinate "dev.axllm:ax" plus unique terms like "Typesafe Jev", "Noul/Choice/Score/Box" establish a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

17

/

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-typesafe/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.