CtrlK
BlogDocsLog inGet started
Tessl Logo

axir-language-backend

Use when adding or changing generated AxIR language backends in this repo, including target registration, codegen templates, package metadata, examples, conformance, and verification. This is a repo-maintainer skill and must not be emitted into generated Ax packages.

74

Quality

92%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary instruction-only skill body: lean, highly actionable with real file paths and verification commands, clearly sequenced with explicit acceptance gates, and cleanly sectioned. It adds only repo-specific knowledge Claude would not already have.

DimensionReasoningScore

Conciseness

The body is dense but not padded — every line is a repo-specific rule or path, with no boilerplate explaining concepts Claude already knows; it assumes competence and lets each token earn its place.

3 / 3

Actionability

Guidance is concrete and copy-ready: named files ("tools/axir/internal/axir/codegen.go", "verify.go", "runtime_model.go"), named commands ("npm run test:axir", "axir verify --targets python,java,cpp,<new-target>"), and an enumerated default-suite list.

3 / 3

Workflow Clarity

A clear sequence runs First Checks → Implementation Rules → Required Touchpoints → Acceptance Bar → Avoid, and the Acceptance Bar provides explicit validation gates (test:axir passes, axir verify passes across named suites) with guard rules for what disqualifies a target.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the content is organized into well-labeled sections of appropriate depth with no nested/deep references, satisfying the simple-skill allowance for progressive disclosure.

3 / 3

Total

12

/

12

Passed

Description

85%

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, specific, well-scoped description with an explicit Use-when trigger and clear conflict resistance. The only weakness is trigger-term breadth: it leans on compiler-internal jargon and omits the concrete language names a maintainer would actually say.

Suggestions

Add the concrete target languages a maintainer would name (e.g., "Python, Java, C++, Go, or Rust backends") to broaden natural trigger coverage.

Consider leading with the maintainer-facing action phrase ("Use when adding a new language backend…") before the internal enumeration so the trigger reads more naturally.

DimensionReasoningScore

Specificity

"adding or changing generated AxIR language backends" is unpacked into a concrete enumeration — "target registration, codegen templates, package metadata, examples, conformance, and verification" — listing multiple specific actions rather than vague language.

3 / 3

Completeness

It states both what (adding/changing backends across registration, codegen, metadata, examples, conformance, verification) and when ("Use when adding or changing generated AxIR language backends"), with an explicit trigger clause.

3 / 3

Trigger Term Quality

"adding or changing generated AxIR language backends" is a natural maintainer phrase, but the remaining keywords (codegen templates, target registration, conformance) are internal jargon and common variations like the actual language names (Python, Java, Go, Rust) are absent.

2 / 3

Distinctiveness Conflict Risk

"generated AxIR language backends in this repo" plus the repo-maintainer scoping clause carves a narrow, clearly distinct niche unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

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

referenced_paths_exist

Referenced path issues: 1 missing

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.