CtrlK
BlogDocsLog inGet started
Tessl Logo

ax-go-agent-rlm

Use when writing Go code with `github.com/ax-llm/ax/packages/go` for RLM executor loops, AxCodeRuntime sessions, runtime envelopes, process runtimes, and optional runtime profiles.

65

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

Quality

Content

72%

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

A compact, well-structured reference skill that assumes competence and points to detail files cleanly. Its main weakness is actionability: the lone code example is incomplete and inconsistent with the documented API surface, and there is no sequenced workflow for the multi-part tasks it covers.

Suggestions

Make the Core Pattern snippet self-contained and executable: add the import line, define or stub `llm`, and reconcile `ax.NewAgent` vs `axllm.NewAgent` with the Relevant API Surface list.

Add a short sequenced workflow (e.g. pick example -> adapt signature -> run with no-key transport -> validate output) with an explicit validation/check step for the runtime-profile and actor-code tasks.

For each When-To-Use bullet, pair the goal with the exact entry point and a one-line runnable command or example file path so guidance is directly actionable.

DimensionReasoningScore

Conciseness

The body is a lean cheat sheet of short bullets and one minimal code snippet with no padding or explanations of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

It provides concrete API identifiers, file pointers, and a Core Pattern snippet, but the code is not copy-paste ready (undefined `llm`, no imports) and `ax.NewAgent` conflicts with the listed `axllm.NewAgent`, so key details are missing.

2 / 3

Workflow Clarity

There is no sequenced multi-step workflow or validation checkpoint; the Guardrails offer mild procedural ordering ('Start from package examples... before inventing a new call shape') but the skill spans several sub-tasks rather than one unambiguous action.

2 / 3

Progressive Disclosure

The SKILL.md is a clear overview with well-signaled one-level-deep references (API.md, axir-api.json, axir-capabilities.json, examples/) listed in Package Facts, and content is appropriately split into organized sections under 50 lines.

3 / 3

Total

10

/

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 trigger and a highly distinct package-scoped niche. The only soft spot is trigger-term quality, which leans on technical identifiers rather than broader natural phrasings.

DimensionReasoningScore

Specificity

It lists multiple concrete targets ('RLM executor loops, AxCodeRuntime sessions, runtime envelopes, process runtimes, and optional runtime profiles') tied to a specific package, matching the multiple-specific-actions anchor.

3 / 3

Completeness

It opens with an explicit 'Use when' clause giving the trigger and names the package plus concrete capabilities, clearly answering both what and when.

3 / 3

Trigger Term Quality

It includes the natural phrase 'writing Go code' and the exact package path, but the remaining triggers are API type names / jargon with thin coverage of common natural variations a user might say.

2 / 3

Distinctiveness Conflict Risk

The pinned import path `github.com/ax-llm/ax/packages/go` plus domain-specific runtime identifiers carve a clear 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

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.