CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-agent-rlm

This skill helps an LLM generate correct AxAgent RLM/runtime code using @ax-llm/ax. Use when the user asks about RLM code execution, AxJSRuntime, contextFields, contextPolicy, liveRuntimeState, promptLevel, stage prompt controls, executorModelPolicy, maxRuntimeChars, agent.test(...), llmQuery(...), recursionOptions, or long-running agent runtime behavior.

Quality

80%

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 ./website/static/typescript/.well-known/agent-skills/ax-agent-rlm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, library-specific rulebook with executable examples and explicit error-recovery guidance throughout. Its weaknesses are repetition of preset/model-selection guidance across sections and a monolithic single-file structure that inlines API-reference material instead of splitting it into reference files.

Suggestions

Consolidate the preset-selection guidance (checkpointed/adaptive/lean/full recommendations) into a single decision table in "Choosing Presets, Prompt Level, And Model Size" and drop the duplicated practical rules from "Use These Defaults" and "Context Policy Presets".

Move the AxJSRuntime permission enum, options quick reference, and dynamic truncation algorithm into a references/ file (e.g. references/runtime-security.md) and keep only the default-hardening summary and the "do not grant permissions unless asked" rule in SKILL.md.

Replace the "Do Not Generate" section's restated rules with a short pointer to "RLM Actor Code Rules" (or delete the duplicates), keeping only the items not already covered such as the llmQuery and [ERROR] pitfalls.

DimensionReasoningScore

Conciseness

The rules are dense, imperative, and library-specific (nothing Claude already knows), but preset-selection guidance ("Start with checkpointed + balanced ... Use adaptive ... Use lean only when ...") is repeated across three sections ("Use These Defaults", "Context Policy Presets", "Choosing Presets, Prompt Level, And Model Size"), and "Do Not Generate" restates rules already given verbatim in "RLM Actor Code Rules" ("Do not write a full multi-step RLM actor program in one turn", "Do not combine console.log(...) with final(...)").

3 / 5

Actionability

Guidance is fully executable: a canonical TypeScript option shape, correct/incorrect actor-turn code pairs with stated reasons ("Reason: turn 2 reuses customers from the persistent runtime"), a complete importable agent.test(...) harness with fn().namespace().arg().returns().handler() chains, runtime permission recipes, and llmQuery call forms covering single, object, and batched usage.

5 / 5

Workflow Clarity

The three-stage pipeline ("distiller (RLM actor) -> executor (RLM actor) -> responder (synthesizer)") and sequenced actor-turn rules ("Inspect what already exists before recomputing it ... console.log ... stop immediately") give a clear sequence, with explicit recovery loops ("Errors ... appear in Action Log; inspect them and fix the code on the next turn"; "If a result starts with [ERROR], inspect or branch on it"). It stops short of anchor 5 because there is no consolidated step-by-step checklist tying the stages, defaults, and actor rules into one ordered procedure.

4 / 5

Progressive Disclosure

Headers are well-organized and the external example links ("Fetch these for full working code") are clearly signaled one level deep, but the ~500-line body inlines substantial API-reference material — the option layout quick reference, AxJSRuntime permission enum and options list, dynamic truncation algorithm, and llmQuery forms — that belongs in separate reference files, matching the anchor-3 pattern of reference content kept inline with no bundle files provided.

3 / 5

Total

15

/

20

Passed

Description

82%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 with an explicit "Use when..." clause and a comprehensive list of library-specific trigger identifiers that users would naturally type. The only weakness is that the "what" side is a single action verb rather than a broader coverage of capabilities.

DimensionReasoningScore

Specificity

"generate correct AxAgent RLM/runtime code" plus "using @ax-llm/ax" names the domain and one concrete action, but no other actions are listed, matching the 1-2-concrete-actions anchor rather than the several-actions anchor at 4.

3 / 5

Completeness

It explicitly answers both: what ("helps an LLM generate correct AxAgent RLM/runtime code using @ax-llm/ax") and when ("Use when the user asks about ... or long-running agent runtime behavior") with concrete trigger phrases, matching the anchor-5 example pattern; the anchor-4 caveat ("'when' could be more explicit") does not apply.

5 / 5

Trigger Term Quality

Thirteen enumerated triggers ("AxJSRuntime, contextFields, contextPolicy, liveRuntimeState, promptLevel, ... llmQuery(...), recursionOptions") are exactly the identifiers a user of this library would type, but a few natural surface terms are missing (e.g. contextMap, autoUpgrade, directResponse, AxCodeRuntime), so it falls just short of the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

Triggers are niche API identifiers specific to this runtime subsystem (AxJSRuntime, executorModelPolicy, maxRuntimeChars), and the body explicitly routes sibling concerns (ax-agent, ax-agent-observability, ax-agent-memory-skills) elsewhere, giving a clear niche with minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (505 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

ax-llm/ax

Path

website/static/typescript/.well-known/agent-skills/ax-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.