Name: ax-go-agent
Rating: 70.39999999999999 (1 reviews)
Author: ax-llm

ax-go-agent

Use when writing Go code with `github.com/ax-llm/ax/packages/go` for agents, child delegation, tools, MCP, citations, persistent playbook learning, stage instructions, runtime state, final typed responses, and direct-respond executor skipping.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%

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, actionable, and well-organized with concrete code and exact API symbols, but it lacks an explicit sequenced workflow with validation checkpoints for assembling an agent end-to-end.

Suggestions

Add a short ordered workflow (e.g. pick a starter example → wire tools/MCP → add citations/playbook → validate with a no-key transport) so multi-step agent assembly is sequenced.

Include a validation/check step for the scripted no-key transport so deterministic local checks are an explicit checkpoint rather than an implied option.

Dimension	Reasoning	Score
Conciseness	The body is lean and fact-driven — Package Facts, a small code example, API surface, and Guardrails — with no padding or explanation of concepts Claude already knows, so every section earns its place.	3 / 3
Actionability	Provides an executable Core Pattern snippet and names exact symbols ("axllm.NewAgent", "axllm.AxMCPClient", "axllm.AxMCPStreamableHTTPTransport") plus concrete guardrails, giving copy-paste-ready direction.	3 / 3
Workflow Clarity	When To Use and Guardrails give structure, but for a multi-capability skill there is no sequenced build-an-agent workflow and no validation checkpoints, so the sequence is present only implicitly.	2 / 3
Progressive Disclosure	At ~45 lines the skill is self-contained and well split into labeled sections (When To Use, Package Facts, Core Pattern, Relevant API Surface, Guardrails) with package artifacts clearly signaled in Package Facts, meeting the under-50-lines bar.	3 / 3
	Total	11 / 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.

The description is specific, complete, and distinctive with an explicit Use-when trigger, but it leans heavily on package-internal jargon rather than natural user phrasing for its trigger terms.

Suggestions

Reword the capability list around terms a user would actually say (e.g. "Go agents", "MCP clients in Go", "Ax Go SDK") rather than internal concepts like "direct-respond executor skipping" and "stage instructions".

Add common trigger phrasings such as "Ax Go", "RLM agent in Go", or "Go MCP client" so the skill surfaces for natural requests.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "agents, child delegation, tools, MCP, citations, persistent playbook learning, stage instructions, runtime state, final typed responses, and direct-respond executor skipping" — matching the anchor for listing several specific actions rather than naming only a domain.	3 / 3
Completeness	An explicit "Use when..." clause states when to invoke it and the capability list states what it does, satisfying both halves with explicit triggers.	3 / 3
Trigger Term Quality	Has a natural trigger ("Use when writing Go code") plus relevant keywords ("agents", "tools", "MCP"), but the bulk is internal jargon ("direct-respond executor skipping", "stage instructions", "playbook learning") that users would not naturally say, and common variations are missing.	2 / 3
Distinctiveness Conflict Risk	It is bound to a specific package path and unique capabilities (AxIR, playbook learning, direct-respond executor), giving it a clear niche unlikely to collide with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/go/skills/ax-go-agent/SKILL.md
Commit: 16c2119

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.