CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

74%

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-signature/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 first half is an excellent, executable guide to Ax signatures, but the second half degenerates into an inlined spec dump for three provider subsystems with no code examples and substantial repetition. Splitting the provider sections into reference files and adding runnable Java snippets would lift conciseness, actionability, and progressive disclosure together.

Suggestions

Move the Typesafe/Jev, OpenAI Decisions, and Gemini Decisions sections into separate reference files (e.g. references/typesafe.md, references/openai-decisions.md, references/gemini-decisions.md) and keep SKILL.md as an overview with one-line pointers, improving both progressive disclosure and token cost.

Add short executable Java snippets to the provider sections (e.g. building a Typesafe score question or an Ax.openaiDecisions call) so the second half is actionable rather than pure constraint prose.

De-duplicate repeated facts: state the trueThreshold 0.5 default, the 2-10 rubric level limit, the 'numeric bounds never define a rubric' rule, and the src/examples/java/generation/ path once each instead of restating them per section.

DimensionReasoningScore

Conciseness

The prose is dense and free of basic-concept padding, but spec-level facts repeat across sections: the trueThreshold 0.5 default appears three times (Typesafe/Jev, OpenAI Decisions, Gemini Decisions), 'Numeric bounds never define a Score rubric' twice, and the examples path 'src/examples/java/generation/' five times. It could be meaningfully tightened.

3 / 5

Actionability

The Core Pattern and More Patterns sections are copy-paste-ready Java ('Ax.s(...)', 'Ax.f().call().input(...)'), but the entire second half (Typesafe/Jev, OpenAI Decisions, Gemini Decisions) describes request shapes and validation rules in prose with no executable Java example, leaving key usage details unstated.

3 / 5

Workflow Clarity

The pattern sections imply a build-to-reuse progression and Guardrails give heuristics, but for a multi-subsystem skill there is no explicit step sequence and no validation checkpoints (e.g. how to verify a signature compiles or a schema validates before calling forward).

3 / 5

Progressive Disclosure

Section headers exist and 'Package Facts' signals API.md, axir-api.json, and examples/, but roughly 100 lines of Typesafe and provider API reference (constraint lists, request/response contracts) are inlined into SKILL.md when they clearly belong in separate reference files, matching the anchor-3 example of inlined API reference.

3 / 5

Total

12

/

20

Passed

Description

87%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 domain, lists concrete capabilities, and carries an explicit 'Use when' trigger tied to a specific package, making it highly discoverable and distinctive. Its only weakness is that the capability list understates the skill's scope (decision evidence, typesafe scoring, provider integrations are unmentioned).

DimensionReasoningScore

Specificity

Lists five concrete capability areas ('string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes'), matching the multiple-specific-actions anchor, but omits major skill topics (decision evidence, Typesafe/Jev, provider decisions) so coverage is not comprehensive.

4 / 5

Completeness

Explicitly answers both: the 'what' is the concrete capability list and the 'when' is the explicit trigger clause 'Use when writing Java code with dev.axllm:ax', mirroring the anchor-5 pattern of concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ('Java code', 'signatures', 'JSON schema', 'validation', plus the package coordinate 'dev.axllm:ax'), but a few natural variations users might say (e.g. 'AxGen', 'tool arguments', 'Ax signature') are missing.

4 / 5

Distinctiveness Conflict Risk

Anchored to a specific package coordinate and language ('Java code with dev.axllm:ax'), giving it a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

18

/

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