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.

66

Quality

80%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 token-efficient, well-structured quick-reference that assumes Claude's competence and points to the right package artifacts. It could be improved by adding one or two fuller executable examples and signaling file references as links.

Suggestions

Add one or two complete executable examples (e.g., an AxGen signature + call) beyond the minimal Core Pattern so common cases are copy-paste ready.

Convert referenced artifacts (API.md, axir-api.json, examples/) into markdown links so navigation is explicit, and consider trimming the inline API surface list since API.md already exists.

DimensionReasoningScore

Conciseness

Lean bullet-style reference with no padding or explanation of concepts Claude already knows (no 'what is an LLM/C++' filler); every section — When To Use, Package Facts, Core Pattern, API Surface, Guardrails — earns its tokens.

5 / 5

Actionability

Provides a copy-paste-ready Core Pattern snippet and concrete file paths (API.md, axir-api.json, examples/), but the bulk of the body is an enumerated API symbol list rather than executable examples covering common cases, leaving minor gaps.

4 / 5

Workflow Clarity

No destructive/batch operation is present, so the validation cap does not apply; directional guidance ('Start from package examples', guardrails) gives a clear procedural skeleton, though there is no explicit sequenced multi-step workflow with checkpoints.

4 / 5

Progressive Disclosure

Well-organized into clear sections under 50 lines, with references to API.md, axir-api.json, and examples/; not a 5 because references are signaled only via backticks (not links) and the long inline Relevant API Surface list overlaps with the separately-referenced API.md.

4 / 5

Total

17

/

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, distinctive description with an explicit 'Use when...' trigger and a concrete list of the package's resources. It would reach the top level by framing the listed items as concrete actions and adding a few natural synonym triggers.

DimensionReasoningScore

Specificity

Lists several specific concrete items — 'factory functions, package docs, examples, and API reference' — alongside the core action 'writing C++ code with axllm', giving broad coverage; not a 5 because the listed items are resources/objects rather than distinct concrete actions.

4 / 5

Completeness

Explicitly answers both what ('using the generated Ax package, factory functions, package docs, examples, and API reference') and when ('Use when writing C++ code with axllm'); not a 5 because the 'when' is a single trigger and the 'what' is a resource list rather than concrete actions, and the 'using...for using' phrasing is slightly redundant.

4 / 5

Trigger Term Quality

The phrase 'writing C++ code with axllm' is a natural trigger a user would actually say, plus package-specific keywords (Ax package, factory functions, API reference); not a 5 because common synonyms/variations (e.g., LLM, Ax, C++ LLM) are absent.

4 / 5

Distinctiveness Conflict Risk

The unique package name 'axllm' plus the C++ language pin define a clear niche with a distinct trigger, making conflict with other skills minimal.

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.

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