CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-typesafe

Use Typesafe Jev models with @ax-llm/ax in TypeScript. Covers images, box outputs, and boolean/class/rubric score signatures with decision evidence, value descriptions, provider trueThreshold, native Noul/Choice/Score questions, structured criteria, probability-based decisions, and explicit hybrid generation.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./website/static/typescript/.well-known/agent-skills/ax-typesafe/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A dense, highly actionable reference with executable examples and exact API constraints, weakened mainly by monolithic structure: everything lives in SKILL.md with no one-level-deep reference files, and minor duplication plus inline version pins slightly hurt token efficiency. Splitting provider-specific and native-client detail into references/ would materially improve progressive disclosure.

Suggestions

Move the Google Gemini Decisions section into a references/ file (e.g. references/gemini-decisions.md) and keep a short pointer plus one snippet in SKILL.md.

Extract the native-client transport/diagnostics detail (models, endpoints, credential callbacks) into a reference file, leaving the settings table inline.

De-duplicate the TYPESAFE_API_KEY guard snippet (shown identically in two sections) and centralize version requirements like "Box needs Jev 1.14" in one place.

DimensionReasoningScore

Conciseness

Nearly every sentence delivers non-obvious API specifics (e.g. "each side 256–1568 pixels, total area at least 78,400 pixels", validation tolerances like "sum to one within an inclusive 0.01 tolerance") with no explanation of concepts Claude already knows. It stays at 4 rather than 5 because the API-key guard snippet is duplicated in two sections and version-sensitive pins ("jev-1.14.0") appear inline rather than in a dedicated section.

4 / 5

Actionability

Complete executable TypeScript examples with imports and env-var handling, runnable commands ("npm run tsx src/examples/typescript/generation/typesafe.ts"), a decision table for choosing the interface, and exact constraints and headers. Copy-paste-ready guidance covers all the common cases (boolean/class, evidence, box, native client, hybrid, Gemini).

5 / 5

Workflow Clarity

The "Choose the Interface" table gives an explicit selection path up front, each interface has its own worked section, and validation guidance is present ("Test wording and decision thresholds against representative labeled inputs", "Assert response contracts in live checks"). Not 5 because there is no end-to-end sequenced workflow with explicit checkpoints; not 3 because selection and validation guidance is concrete and clearly organized.

4 / 5

Progressive Disclosure

The body is a ~400-line monolithic file with no bundle files at all (references/, scripts/, assets/ do not exist); content that clearly belongs in separate files is inlined, notably the entire Google Gemini Decisions provider section (~60 lines) and native-client transport details. Structure and section headers are good and external doc links are clearly signaled, which keeps it above 2.

3 / 5

Total

16

/

20

Passed

Description

70%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 highly specific, distinctive description that clearly states what the skill covers, but it lacks any explicit when-to-use trigger guidance and omits the Gemini Decisions capability that the body documents. Adding a "Use when..." clause would raise completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when integrating Typesafe/Jev decision models (booleans, classifications, rubric scores, box localization) into an @ax-llm/ax TypeScript program."

Mention Google Gemini Decisions in the description, since it is a major documented capability and a likely user search term.

Trim abstract tail phrases like "probability-based decisions, and explicit hybrid generation" in favor of one or two natural user phrasings.

DimensionReasoningScore

Specificity

Enumerates many concrete capabilities ("images, box outputs, and boolean/class/rubric score signatures with decision evidence, value descriptions, provider trueThreshold, native Noul/Choice/Score questions"), matching the several-specific-actions anchor. It stays at 4 rather than 5 because capabilities are named as covered features rather than actions and notable body topics (Gemini Decisions, transport/diagnostics) are omitted.

4 / 5

Completeness

The "what" is clear and detailed, but there is no "Use when..." clause or equivalent explicit trigger guidance; the only when-signal is the weakly implied "in TypeScript". Per the rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good keyword coverage with the natural terms of this niche ("Typesafe", "Jev", "@ax-llm/ax", "TypeScript", "boolean/class", "rubric score"), but a few natural terms are missing, e.g. the Google Gemini Decisions provider that occupies a large section of the body. Not 3: the terms present are exactly what a user of this library would say, not generic.

4 / 5

Distinctiveness Conflict Risk

Names a specific library, model family, and language ("Typesafe Jev models with @ax-llm/ax in TypeScript"), giving it a clear niche with distinct triggers and minimal risk of firing for unrelated skills.

5 / 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

website/static/typescript/.well-known/agent-skills/ax-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.