CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-cpp-typesafe

Use when writing C++ code with `axllm` 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

73%

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/cpp/skills/ax-cpp-typesafe/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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, information-rich reference that respects Claude's intelligence — no filler or basic-concept explanations — and gives concrete API constraints throughout. Its weaknesses are structural: monolithic inline detail that belongs in reference files, an implicit workflow with no validation checkpoints, and only one executable code example.

Suggestions

Move bulk constraint detail (Box/native request limits, probability validation rules, the Google Gemini Decisions section) into a reference file and keep a short summary with a clearly signaled link in SKILL.md.

Add 2–3 short executable C++ snippets for the common cases — evidence-bearing signatures, a score rubric, a Box localization — instead of only describing their rules in prose.

Make the usage sequence explicit in 'When To Use' or 'Core Pattern' (define signature → configure model → forward → handle refusal), including a checkpoint for verifying output shape before consuming results.

DimensionReasoningScore

Conciseness

No explanations of concepts Claude already knows; every paragraph carries package-specific constraints (e.g. "Choice allows 1–255 labels; Score requires 2–10 rubric levels"). Not 5 because the example-path pointer "Runnable ... examples are under src/examples/cpp/generation/" is repeated three times and several sentences cram unrelated rules together.

4 / 5

Actionability

One complete executable code block (Core Pattern) plus exact API names and concrete constraints ("trueThreshold ... finite value in [0,1], default 0.5") and a fallback guardrail ("Start from package examples for exact native syntax"). Not 5 because most sections state declarative rules without executable snippets for the common cases (evidence, Box, Gemini).

4 / 5

Workflow Clarity

"When To Use" gives high-level routing and the Core Pattern implies create-model → define-signature → forward, but there is no explicit step sequence, no validation checkpoints, and no error-recovery loop beyond the refusal-handling note. Matches 'sequence present but checkpoints missing or implicit'; not 4 since checkpoints are entirely implicit.

3 / 5

Progressive Disclosure

Sections are organized and external materials are named ("API.md", "axir-capabilities.json", "examples/"), but ~90 lines of dense inline rule collections (pixel/byte limits, probability tolerances, the full Gemini Decisions section) are detail the rubric expects in separate reference files, and no bundle files exist to offload it. Fits 'some structure; content that should be separate is inline', short of the well-split structure of level 4.

3 / 5

Total

14

/

20

Passed

Description

71%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 distinctive, well-scoped description that explicitly states when to use the skill and enumerates concrete capabilities. Its main weakness is jargon density: many listed terms are internal API nouns rather than natural user trigger phrases, which limits keyword matching.

Suggestions

Add one or two natural-language trigger phrases users would actually say (e.g. 'when building decision/triage flows in C++ with axllm') alongside the technical term list.

Trim internal jargon like 'Noul' or 'provenance' from the description, or pair each with a plain-language synonym so the description matches how users phrase requests.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — "boolean/class/rubric score/box signatures", "decision evidence and provenance", "structured criteria and hybrid generation" — that map directly to the body's coverage. Not 5 because they are jargon-heavy noun phrases rather than a comprehensive set of plainly stated actions.

4 / 5

Completeness

Explicitly answers both: 'when' via "Use when writing C++ code with `axllm`" and 'what' via the feature list. Not 5 because the 'when' clause is a single terse condition without broader trigger phrases (e.g. 'when the user mentions...').

4 / 5

Trigger Term Quality

"C++ code", "axllm", and "Typesafe Jev" are terms a user of this package would actually say, but most of the description is API-internal jargon ("Noul", "provenance", "hybrid generation") with no natural synonyms or variations. Fits 'some relevant keywords but missing common variations', not the good coverage of level 4.

3 / 5

Distinctiveness Conflict Risk

The named package `axllm`, "Typesafe Jev", and "Noul/Choice/Score/Box" form a clear niche with near-zero overlap risk — no generic skill would match this trigger set.

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

packages/cpp/skills/ax-cpp-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.