CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-java-flow

Use when writing Java code with `dev.axllm:ax` for flows, nodes, program graphs, nested programs, dynamic options, caching, and optimizer components.

Quality

72%

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-flow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 strong, code-first pattern catalog for flow construction with concrete Java examples and useful guardrails. Its weaknesses are the long, dense 'Astra Session Work' section that reads as inlined reference documentation, the absence of every referenced file from the actual bundle, and the lack of an explicit ordered workflow with validation checkpoints.

Suggestions

Move the 'Astra Session Work' section into a separate reference file (e.g. references/astra-sessions.md) and keep a 3-5 line summary with a clear pointer in SKILL.md.

Ship the referenced files (API.md, axir-api.json, axir-capabilities.json, examples/) in the bundle or reword Package Facts to make clear they live in the package repo, not the skill.

Add a short ordered workflow (start from examples → compose flow → verify with no-key transport → run with provider) so validation checkpoints are explicit rather than implied by Guardrails.

DimensionReasoningScore

Conciseness

The flow-pattern sections are lean and code-first, but the ~40-line 'Astra Session Work' section is dense reference prose (e.g. 'Queued and applied are different states', per-language registration calls, WebSocket adapter behavior) that could be significantly tightened or moved to a reference file. It is mostly efficient with some clearly compressible material, matching anchor 3 rather than anchor 2 since nothing explains concepts Claude already knows.

3 / 5

Actionability

Concrete, realistic Java snippets cover the common cases (Ax.flow(...).execute(...).returns(...), forward with caching options) and Guardrails give executable direction ('Use `no-key` examples for deterministic local checks'). Minor gaps keep it from anchor 5: several examples reference undefined variables (research, audience, join, client, cache), so they are not fully copy-paste ready.

4 / 5

Workflow Clarity

Patterns progress sensibly (core pattern → variants → run → cache) and the Guardrails section supplies quasi-checkpoints, but there is no explicit ordered workflow (e.g. check examples → write flow → verify with no-key transport) and no validation feedback loop. This matches anchor 3: sequence present, checkpoints implicit; it does not reach anchor 4 because the checkpoints are scattered rather than integrated into a clear process.

3 / 5

Progressive Disclosure

Section headers are clear and references are prominently signaled in 'Package Facts' (API.md, axir-api.json, examples/), giving real structure. However, the bundle contains none of the referenced files — API.md, axir-capabilities.json, and examples/ do not exist in the skill directory — and the Astra Session Work reference material is inlined rather than split out, matching anchor 3 (structure present, but content that should be separate is inline and navigation targets are questionable).

3 / 5

Total

13

/

20

Passed

Description

75%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 well-scoped, appropriately concise description that pins a distinct niche (Java + dev.axllm:ax) with an explicit 'Use when' trigger and a broad feature list. Its main weakness is that the 'what' enumerates feature nouns rather than concrete actions, which slightly blurs what the skill actually does.

Suggestions

Lead with one or two concrete verbs describing what the skill does (e.g. 'Compose typed LLM workflow graphs in Java using dev.axllm:ax') before the feature list.

Add the natural product name 'AxFlow' and a common synonym like 'workflow' to improve trigger-term coverage.

Trim jargon-heavy items like 'dynamic options' and 'optimizer components' in favor of phrases users would actually say.

DimensionReasoningScore

Specificity

The description names the domain ("writing Java code with `dev.axllm:ax`") and lists several concrete capability areas ("flows, nodes, program graphs, nested programs, dynamic options, caching, and optimizer components"), matching the anchor for several specific items with minor gaps. It falls short of anchor 5 because these are feature nouns rather than explicit concrete actions, and above anchor 3 because coverage goes well beyond 1-2 items.

4 / 5

Completeness

Both parts are present: an explicit when ("Use when writing Java code with `dev.axllm:ax`") and a what-scoping feature list. It does not reach anchor 5 because the 'what' is a feature enumeration without concrete action verbs, and it exceeds anchor 3 because the trigger clause is explicit rather than implied.

4 / 5

Trigger Term Quality

Includes natural terms a user of this stack would say — "Java code", "flows", "nested programs", "caching" — plus the distinctive package identifier `dev.axllm:ax`. A few natural terms are missing (e.g. "AxFlow", "workflow", "Ax"), keeping it below the comprehensive-synonyms anchor 5 and clearly above the sparse anchor 3.

4 / 5

Distinctiveness Conflict Risk

Scoping to a specific language plus a specific generated package ("Java code with `dev.axllm:ax`") creates a clear niche with minimal conflict risk. Generic component terms like "caching" and "optimizer components" leave minor overlap risk with closely related sibling skills, so it sits between anchors 4 and 5, noticeably above the midpoint.

4 / 5

Total

16

/

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