CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-cpp-signature

Use when writing C++ code with `axllm` for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.

Quality

69%

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

Quality

Content

46%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 front half of the body is a well-formed patterns guide with executable snippets, but the back half degenerates into dense, repetitive provider-reference prose that belongs in separate files, and every external file reference points to paths absent from the bundle. Structure exists, but progressive disclosure is effectively broken and the token budget is spent on material a referencing file should hold.

Suggestions

Move the Typesafe/Jev, OpenAI Decisions, and Google Gemini Decisions sections into separate reference files (e.g., references/typesafe.md, references/openai-decisions.md, references/gemini-decisions.md) and keep one-paragraph summaries with clearly signaled links in SKILL.md.

Either include the referenced bundle files (API.md, axir-api.json, axir-capabilities.json, examples/) in the bundle or remove/correct the references so navigation does not dead-end.

Convert the long constraint paragraphs into scannable bullet lists and deduplicate repeated facts (example paths stated four times, trueThreshold default restated three times), moving version-specific guidance like 'jev-1.14.0 or jev-preview' into a versions/compatibility section.

DimensionReasoningScore

Conciseness

Most sentences carry non-obvious package facts (e.g., "Choice allows 1–255 labels; Score requires 2–10 rubric levels"), so it is not padded with common knowledge — but it could be tightened considerably: dense unbroken paragraph walls where lists would serve, near-duplicate repetitions ("Runnable ... examples are under src/examples/cpp/generation/" appears four times; trueThreshold defaults restated in three sections), and version-sensitive details like "Use jev-1.14.0 or jev-preview" inline rather than in a deprecated/versions section. This matches anchor 3: mostly efficient with unnecessary repetition that could be trimmed.

3 / 5

Actionability

The Core Pattern and More Patterns sections give concrete, executable C++ snippets (axllm::s, axllm::ax, Core::record_new, validate_signature), but they cover only the top ~60 lines; the majority of the body — Decision evidence, Typesafe/Jev, OpenAI Decisions, and Gemini Decisions — is abstract constraint prose with no code or commands, deferring entirely to example directories. This lands between anchors 3 and 4: concrete guidance exists but is incomplete relative to the skill's stated scope.

3 / 5

Workflow Clarity

There is a rough implied sequence (start from examples, pick a pattern, validate_signature, render schema, pass to AxGen) and one explicit validation call ("Validate the native record, then render its output fields"), but no clearly sequenced multi-step workflow with checkpoints for the main flows; guardrails like "Start from package examples... before inventing a new call shape" are direction, not steps. Anchor 3 fits: steps/patterns present but validation checkpoints are implicit and scattered.

3 / 5

Progressive Disclosure

The bundle contains no files other than SKILL.md, yet the body points to API.md, axir-api.json, axir-capabilities.json, examples/, and src/examples/cpp/generation/ — none of which exist here, so navigation dead-ends. Meanwhile ~80 lines of provider-specific reference material (Typesafe/Jev, OpenAI Decisions, Gemini Decisions constraints) that clearly belongs in separate reference files is inlined wholesale. This matches anchor 2: content that belongs in separate files is inlined and the references are broken, though section headers keep it above anchor 1's monolithic wall.

2 / 5

Total

11

/

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 description: it opens with an explicit "Use when" trigger, enumerates five concrete capabilities, and pins a distinct niche via the C++/axllm pairing. The main improvement would be decoupling the when-clause from the what-list with user-facing trigger contexts and adding a few synonyms.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes" — which is multiple specific capabilities rather than vague language. It falls short of anchor 5 because major body capabilities (decision evidence, typesafe/Jev scoring, provider-specific decision APIs) are uncovered, leaving minor-to-moderate gaps in coverage.

4 / 5

Completeness

Both parts are explicitly present: the "what" is the enumerated capability list (signatures, field descriptors, JSON schema output, validation, tool argument shapes) and the "when" is the explicit "Use when writing C++ code with `axllm`" clause. It sits below anchor 5 because the when-clause is somewhat circular — it restates the capability list rather than naming distinct user contexts or mentions (compare the anchor-5 example's "when the user mentions PDFs, forms, or document extraction").

4 / 5

Trigger Term Quality

Terms like "C++ code", "string signatures", "JSON schema", "validation", and the package name "axllm" are phrases a user working in this domain would naturally say. It is not a 5 because there are no synonyms or variations (e.g., "Ax signatures", "input/output contracts", "score rubrics") and phrases like "typed tool argument shapes" lean technical.

4 / 5

Distinctiveness Conflict Risk

The combination of "C++ code", the package name "axllm", and "string signatures" carves out a clear niche with distinct triggers and minimal conflict risk; no other plausible skill would trigger on this description except perhaps a sibling axllm language skill, which the explicit "C++" qualifier already disambiguates.

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