Name: ax-go-flow
Rating: 66.4 (1 reviews)
Author: ax-llm

ax-go-flow

Use when writing Go code with `github.com/ax-llm/ax/packages/go` for flows, nodes, program graphs, nested programs, dynamic options, caching, and optimizer components.

Quality

80%

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

68%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 well-organized pattern catalog with concrete executable Go examples and clear pointers to deeper reference material. Weakened by an ax/axllm naming inconsistency, unhandled error returns, and references to bundle files that are not actually present.

Suggestions

Resolve the ax vs axllm symbol inconsistency (code uses ax.NewFlow while 'Relevant API Surface' lists axllm.NewFlow) and add the import block so examples are truly copy-paste ready.

Add a brief validation/error-handling step after Forward (check err before using output) to give the run-a-flow workflow an explicit checkpoint.

Either include the referenced files (API.md, axir-capabilities.json, examples/) in the bundle or reword the pointers so they clearly point to the external URL/source rather than missing local paths.

Dimension	Reasoning	Score
Conciseness	Lean body that assumes Go competence and avoids explaining concepts, but the five flow examples repeat near-identical NewFlow/Execute/Returns boilerplate that could be tightened, and 'When To Use' partially restates the description.	4 / 5
Actionability	Provides multiple concrete, near-copy-paste Go examples covering common patterns, but import statements are absent and there is an ax/axllm naming inconsistency between the code ('ax.NewFlow') and the API surface line ('axllm.NewFlow').	4 / 5
Workflow Clarity	Each pattern shows an ordered Execute sequence, but there is no overarching multi-step process with validation checkpoints or error-recovery guidance, and the Forward call's 'err' is not handled.	3 / 5
Progressive Disclosure	Well-structured sections with clearly signaled one-level-deep references (API.md, axir-api.json, axir-capabilities.json, examples/, external URL), but the referenced bundle files are not present, so navigation cannot be completed.	4 / 5
	Total	15 / 20 Passed

Description

92%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 tight, well-scoped description that pairs an explicit 'Use when' trigger with a comprehensive list of concrete capabilities tied to a specific package. Slight room to broaden natural-language synonyms beyond the technical capability terms.

Suggestions

Add a few plain-language trigger synonyms (e.g., 'AxFlow', 'Ax flows', 'workflow graph') so users not using the exact package path still match naturally.

Consider noting the primary verb form in third person (e.g., 'Composes ...') alongside the 'Use when' clause for clarity.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'flows, nodes, program graphs, nested programs, dynamic options, caching, and optimizer components' — giving comprehensive coverage of the package's surface rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both what (writing Go code for flows/nodes/etc. with the named package) and when via a concrete 'Use when writing Go code with ...' trigger clause.	5 / 5
Trigger Term Quality	Includes a strong natural trigger ('writing Go code with `github.com/ax-llm/ax/packages/go`') plus several capability keywords, but the remaining terms (program graphs, nested programs, optimizer components) lean technical and miss common synonyms a user might say.	4 / 5
Distinctiveness Conflict Risk	Scoped to a single named Go package import path, creating a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 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-flow/SKILL.md
Commit: dec4f9e

Reviewed: ~23 hours 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.