CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

75%

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

75%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.

An exemplarily lean, well-organized overview that assumes Claude's competence and wastes no tokens. Its weakness is executable completeness: the single code fragment depends on undefined variables, and the examples and API docs it directs the agent to are not actually present in the skill bundle.

Suggestions

Include one complete, copy-paste-ready example in the body — imports, LLM construction (including the no-key transport), and a full forward call — so the core pattern stands alone.

Bundle or inline the key material from the referenced files (API.md excerpts, a no-key example) since references/, scripts/, and assets/ are empty and the pointers currently lead nowhere within the skill.

Clarify where `API.md`, `axir-api.json`, and `examples/` live (package directory vs. skill bundle) so navigation to the deeper material is unambiguous.

DimensionReasoningScore

Conciseness

The ~45-line body is lean throughout: terse fact bullets ("Real network support: yes."), a two-line core pattern, and guardrails with zero padding or explanation of concepts Claude already knows. Every token earns its place, matching the top anchor.

5 / 5

Actionability

The core pattern is real Rust with an exact signature string ("question:string -> answer:string"), but it references undefined `llm` and `inputs` with no imports or setup, and "Start from package examples" points to an `examples/` directory that is not part of the skill bundle. This is concrete-but-incomplete guidance (anchor 3) — the gaps are more than minor, ruling out 4, while the real API names and specific example-selection guardrails keep it above 2.

3 / 5

Workflow Clarity

The body is cleanly organized (When To Use → Package Facts → Core Pattern → API Surface → Guardrails) with no destructive or batch operations, so the validation cap does not apply. It is not 5 because the path from loaded skill to working code has gaps (LLM/transport construction is undefined), and above 3 because the structure and guardrails give clear, mostly unambiguous direction.

4 / 5

Progressive Disclosure

A lean overview clearly signals deeper materials ("Package API docs: `API.md` and `axir-api.json`", "Capability manifest", "Runnable examples: `examples/`"), and nothing inlined should be split out. It is not 5 because those referenced files are absent from the skill bundle (no references/, scripts/, or assets/ exist) and their location relative to the skill is ambiguous; it is above 3 because the references are plainly listed rather than buried.

4 / 5

Total

16

/

20

Passed

Description

65%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 highly distinctive, well-targeted trigger description whose "when" guidance is explicit and rich with natural domain keywords. Its main weakness is that it is solely a trigger clause: what the skill actually does is only implied, and the only action verb is the generic "writing".

Suggestions

Add an explicit what-statement before the trigger, e.g., "Provides Rust API guidance, core patterns, and example routing for the generated axllm package. Use when..." so completeness reaches both what and when.

Convert some enumerated nouns into concrete actions (e.g., "Wire AxCodeRuntime sessions" or "Build RLM executor loops") to raise specificity beyond a single generic verb.

Include one or two additional natural variations users might say, such as "actor-code sessions" or "QuickJS runtime", to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description offers one generic action verb ("writing Rust code") but enumerates concrete technical targets ("RLM executor loops, AxCodeRuntime sessions, runtime envelopes, process runtimes, and optional runtime profiles"), matching the anchor for domain plus 1-2 concrete actions. It is not a 4 because it lists objects rather than several distinct concrete actions, and not a 2 because it goes beyond merely naming the domain.

3 / 5

Completeness

The description is entirely a "Use when..." clause, so the "when" is explicit and specific while the "what" is only implied by the trigger's scope — the mirror of the anchor for a clear element with the other weakly implied. It is not 4 because no separate explicit statement of what the skill does is present, and above 2 because the trigger is far more informative than "Use when working with documents".

3 / 5

Trigger Term Quality

Terms like "Rust code", "axllm", "AxCodeRuntime sessions", "runtime envelopes", and "runtime profiles" are exactly the phrases a user of this package would naturally say, giving good keyword coverage. It falls short of 5 because natural variations and synonyms (e.g., AxAgent, actor-code, QuickJS, sessions wording alternatives) are missing.

4 / 5

Distinctiveness Conflict Risk

Package-specific triggers ("axllm", "AxCodeRuntime", "RLM executor loops") carve out a clear niche that virtually no other skill would match, giving minimal conflict risk. Re-checking the anchor below (4, "minor overlap risk") confirms none applies — these API names are unique to this package.

5 / 5

Total

15

/

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/rust/skills/ax-rust-agent-rlm/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.