CtrlK
BlogDocsLog inGet started
Tessl Logo

ax-rust-agent-rlm

Use when writing Rust code with `axllm` for RLM executor loops, AxCodeRuntime sessions, runtime envelopes, process runtimes, and optional runtime profiles.

64

Quality

78%

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/rust/skills/ax-rust-agent-rlm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 concise and well-structured with an executable core pattern, but it lacks an explicit multi-step workflow and its referenced API files/examples are not present in the bundle.

Suggestions

Add a short sequenced workflow (e.g., pick profile -> write agent -> forward -> verify output) with a validation checkpoint to raise workflow clarity.

Either ship the referenced bundle files (API.md, axir-api.json, examples/) or remove/qualify the references so progressive disclosure navigation is real rather than dangling.

Include concrete signatures or one more complete example for the listed API surface symbols to make guidance fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and sectioned (Package Facts, Core Pattern, Guardrails) with no padding or explanation of concepts Claude already knows, so every token earns its place per the 5 anchor.

5 / 5

Actionability

An executable Core Pattern code block is provided, but the 'Relevant API Surface' only lists symbol names without signatures or call shapes, leaving minor gaps versus copy-paste-ready 5.

4 / 5

Workflow Clarity

It lists 'When To Use' bullets and guardrails but presents no sequenced multi-step workflow with validation checkpoints, matching the 'steps listed but checkpoints missing' anchor; the skill is not destructive/batch so the cap does not apply.

3 / 5

Progressive Disclosure

Content is under 50 lines and well-organized into clear sections, but the referenced bundle files (API.md, axir-api.json, examples/) do not exist in the skill bundle, so navigation signaling is good but not fully realized, landing at 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

80%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 is well-formed with an explicit 'Use when' trigger and concrete capabilities in a distinct niche. Its main weakness is trigger-term quality: several named capabilities are internal jargon a user would not naturally utter.

Suggestions

Add user-natural synonyms to the trigger (e.g., 'writing Rust agents', 'RLM loops', 'runtime sessions') so it matches phrasings users actually say.

Consider mentioning the file extension or concrete artifact types users reference (e.g., Cargo crate, .rs source) to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the Rust/axllm domain plus several concrete capabilities ('RLM executor loops, AxCodeRuntime sessions, runtime envelopes, process runtimes, and optional runtime profiles'), matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.

4 / 5

Completeness

It explicitly answers both what (writing Rust code with axllm for the listed capabilities) and when ('Use when writing Rust code with axllm...'), matching the anchor requiring concrete trigger phrases for both.

5 / 5

Trigger Term Quality

'Use when writing Rust code with axllm' is a natural trigger, but terms like 'AxCodeRuntime sessions' and 'runtime envelopes' are technical jargon users would rarely say, and common synonyms are missing, so it lands at 'some relevant keywords but missing variations' rather than 4.

3 / 5

Distinctiveness Conflict Risk

The niche Rust/axllm/RLM domain with runtime-profile triggers carves a clear niche with minimal overlap risk against general skills.

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.