CtrlK
BlogDocsLog inGet started
Tessl Logo

website-md-language-docs

Use when changing Ax website language docs, language-specific snippets, examples, API symbol mappings, generated package capabilities, or adding a new website language route. Keeps the markdown-only Hugo site source-audited and generated from repo truth.

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.

A lean, highly actionable skill body with concrete commands, a sequenced workflow, and an explicit verification block; well organized with no padding.

DimensionReasoningScore

Conciseness

The body is dense and action-oriented with concrete paths and commands, does not explain concepts Claude already knows, and every section earns its place.

3 / 3

Actionability

Provides fully executable commands (e.g., 'npm run example -- list', 'npm run website:prepare'), specific file locations, and concrete JSON field names — copy-paste ready guidance.

3 / 3

Workflow Clarity

A clear numbered six-step workflow plus a dedicated Checks section with explicit verification commands forms a validate-then-confirm feedback loop for the surface being changed.

3 / 3

Progressive Disclosure

A short, self-contained skill (~50 lines) with no external references needed, organized into clearly labeled sections (Workflow, Feature sync, API Mapping, Checks) — appropriate for a single-purpose skill with empty bundle dirs.

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 description with an explicit Use-when trigger and a clear niche, weakened only by jargon-heavy trigger terms that a non-expert user would be less likely to voice.

Suggestions

Soften jargon in the trigger clause with user-facing phrasing (e.g., 'Use when updating the docs for a programming language on the Ax website').

Add common variations users might say, such as 'language docs', 'website examples', or 'install snippets'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'changing Ax website language docs, language-specific snippets, examples, API symbol mappings, generated package capabilities, or adding a new website language route' rather than vague language.

3 / 3

Completeness

Explicitly states both what ('Keeps the markdown-only Hugo site source-audited and generated from repo truth') and when ('Use when changing Ax website language docs...') with an explicit trigger clause.

3 / 3

Trigger Term Quality

Has relevant triggers ('Use when changing... docs, snippets, examples') but leans on codebase-internal jargon ('API symbol mappings', 'generated package capabilities') rather than natural terms a user would say, and misses common variations.

2 / 3

Distinctiveness Conflict Risk

The niche is tightly scoped to Ax website language docs and routes, with distinct triggers unlikely to fire 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: 2 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.