CtrlK
BlogDocsLog inGet started
Tessl Logo

ax-cpp-llm

Use when writing C++ code with `axllm` for using the generated Ax package, factory functions, package docs, examples, and API reference.

61

Quality

77%

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

Quality

Content

75%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 an efficient, well-structured quick reference with executable core-pattern code and concrete guardrails. Its main gaps are the absence of call shapes for the primary program APIs and references to package files (API.md, examples/) that are not part of the bundle.

DimensionReasoningScore

Conciseness

The body is lean bullet-list reference material with no concept padding, but the intro sentence and "When To Use" bullets duplicate the frontmatter description, and the flat ~40-symbol API list inlines internals (tracers, meters, rate limiters) alongside core entry points that could be trimmed.

4 / 5

Actionability

The "Core Pattern" snippet is real executable C++ and the guardrails are concrete decision rules, but only client creation is shown — the primary program APIs (`axllm::ax`, `axllm::agent`, `axllm::flow`, `axllm::optimize`) are listed by name with no call shapes, leaving gaps beyond the delegating pointer to `examples/`.

4 / 5

Workflow Clarity

As a reference skill under 50 lines, the content is unambiguous and the guardrails act as decision checkpoints (start from examples before inventing call shapes; provider-api only with credentials; no-key for deterministic checks), though the usage sequence is implicit rather than explicitly ordered.

4 / 5

Progressive Disclosure

Sections are well organized and references are one level deep and clearly signaled ("Package API docs: `API.md` and `axir-api.json`", "Runnable examples: `examples/`"), but those referenced files are not present in the skill bundle, so navigation cannot be verified against the actual bundle structure.

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

The description has a clear, explicit trigger ("Use when writing C++ code with `axllm`") and good natural keywords for its niche. Its main weakness is that it enumerates resources (package docs, examples, API reference) rather than concrete capabilities, leaving the what-side of the description under-specified.

Suggestions

Replace the resource list with concrete actions, e.g. "Write C++ programs with the generated `axllm` package: build LLM clients, signatures, generators, agents, flows, and optimizers using its factory functions and examples."

State what the skill does with the listed resources (e.g. "look up exact native call shapes and API signatures") so the what-side answers are as explicit as the when-clause.

DimensionReasoningScore

Specificity

The description names the domain ("writing C++ code with `axllm`") and one action, but "factory functions, package docs, examples, and API reference" lists resources rather than concrete actions, matching the anchor for naming a domain with 1-2 actions rather than listing several specific actions.

3 / 5

Completeness

An explicit when-clause is present ("Use when writing C++ code with `axllm`"), and a what is present ("using the generated Ax package, factory functions, package docs, examples, and API reference"), but the what is vague about what is actually done with those resources, so it falls short of clearly and concretely answering both.

4 / 5

Trigger Term Quality

Terms like "C++ code", "`axllm`", "Ax package", and "API reference" are natural phrases a user of this generated package would say, though common variations like "Ax LLM" or "LLM programming in C++" are missing.

4 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to C++ and the `axllm` package, but the phrase "generated Ax package" implies sibling skills for other languages of the same framework, creating minor overlap risk with closely related skills.

4 / 5

Total

15

/

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