CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-cpp-gen

Use when writing C++ code with `axllm` for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.

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

An information-dense, accurate-feeling API reference that assumes Claude's competence and gives highly concrete, package-specific guidance, anchored by one executable pattern and exact identifiers. Its weaknesses are monolithic structure (provider-by-provider detail inlined rather than split into reference files), repeated boilerplate phrases, and no end-to-end worked workflow with validation steps.

Suggestions

Split the per-provider sections (OpenAI Decisions, Google Gemini Decisions, Astra Session Work) into one-level-deep reference files (e.g., references/decisions-openai.md, references/astra-sessions.md) and keep a short overview with clearly signaled links in SKILL.md.

Factor out the repeated boilerplate ("as in TypeScript", "set on the constructor or the forward (the forward's wins)", "the forward's wins") into a single conventions section, and convert dense option prose like the parseDates and retry paragraphs into compact tables or bullet lists.

Add one complete, copy-paste-ready example program per "When To Use" bullet (signature + tool + multi-sampling with a result picker), each ending with an explicit verification step such as running the no-key scripted transport example.

DimensionReasoningScore

Conciseness

The body almost entirely avoids explaining things Claude already knows — every sentence carries package-specific facts ("trueThreshold ... defaults to 0.5, is finite in [0,1], and uses an inclusive comparison") — but it is not lean: phrases like "as in TypeScript" and "set on the constructor or the forward (the forward's wins)" are repeated verbatim many times, and multi-hundred-word paragraphs (e.g., the parseDates and retry sections) could be tightened or tabulated. It fits the 3 anchor (mostly efficient but could be tightened) rather than 2, since there is no conceptual padding, and not 4, given the duplicated boilerplate and paragraph bulk.

3 / 5

Actionability

Concrete, near copy-paste guidance dominates: an executable core pattern, exact identifiers and signatures ("streaming_forward(client, values, options, handler)", "auto cache = axllm::caching_function(fn);" with the options key), specific defaults and exact error strings ("Generate failed: Max steps reached: N"). It stops short of 5 because only one complete example program exists inline — tool attachment, multi-sampling, and streaming are described in prose while runnable shapes are deferred to package examples that are not part of this skill bundle.

4 / 5

Workflow Clarity

"When To Use" gives entry points, "Guardrails" gives decision ordering ("Start from package examples ... before inventing a new call shape"), and "Core Pattern" gives a starting step, but there is no explicit multi-step sequence or validation checkpoint for common tasks (e.g., build a program with tools, add a picker, verify output). This matches the 3 anchor (sequence implicit, checkpoints missing) rather than 2, since the sections do impose a coherent rough order, and not 4, because no section walks through a task end-to-end with checks.

3 / 5

Progressive Disclosure

The body has real section structure and points to package artifacts ("API.md", "axir-capabilities.json", "examples/"), but no bundle files exist and ~90 lines of dense per-provider behavioral detail (OpenAI Decisions, Gemini Decisions, Astra session semantics) are inlined in SKILL.md where the rubric expects them in one-level-deep reference files. This is the 3 anchor (structure present, but content that should be separate is inline) rather than 2, since headers and a clear facts section exist, and not 4, because the monolithic inlining is substantial, not minor.

3 / 5

Total

13

/

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, niche-specific description with an explicit "Use when" trigger and a dense list of concrete capabilities. Its main weaknesses are jargon-heavy trigger phrases that users may not say naturally and the absence of a separate, explicit statement of what the skill does.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing" — going well beyond a generic domain statement. It falls short of a 5 because the items are terse API-surface nouns rather than fully articulated actions (e.g., it never says what the skill actually does with them, like "write" or "generate"), and not above the 3 anchor, which covers only 1-2 concrete actions.

4 / 5

Completeness

The "when" is explicit ("Use when writing C++ code with `axllm` for...") and the capability list conveys the "what", so both are present. It is below the 5 anchor because "what" and "when" are merged into a single clause — there is no standalone statement of what the skill does (e.g., "Write C++ structured-generation programs using axllm"), leaving the what only implied by the trigger list.

4 / 5

Trigger Term Quality

Strong domain keywords a user of this package would naturally say: "C++ code", "axllm", "AxGen", "forward calls", "streaming", "tools", "output parsing". It is not a 5 because several phrases are API jargon users would rarely utter verbatim ("indexed multi-sampling", "result pickers", "traces") and common synonyms like "structured output" or "LLM calls" are absent.

4 / 5

Distinctiveness Conflict Risk

"C++ code with `axllm` for AxGen programs" carves out a clear niche with distinct, package-specific triggers; no other skill would plausibly fire on these phrases. It clearly matches the 5 anchor (clear niche, distinct triggers, minimal conflict risk) and not the 4 anchor, which requires some overlap risk with closely related 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/cpp/skills/ax-cpp-gen/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.