Name: ax-go-flow
Rating: 68 (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

82%

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

80%

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

The content is concise and actionably code-forward with several executable patterns, but it lacks explicit validation checkpoints and references bundle files that are not present. Tightening the workflow guidance and reconciling broken references would raise it.

Suggestions

Add an explicit validation/verification checkpoint (e.g., build the flow, run a no-key example, confirm it compiles) so the workflow has a concrete feedback loop rather than pointing at a missing examples/ directory.

Reconcile the API surface naming: the code uses the `ax.` package prefix while 'Relevant API Surface' lists `axllm.NewFlow`/`axllm.AxFlow`, which is inconsistent and could mislead.

Either provide the referenced bundle files (API.md, axir-api.json, axir-capabilities.json, examples/) or remove those references so navigation does not point to non-existent resources.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward with short sections and no padding explaining Go or library basics; every section earns its place, matching the lean-and-efficient anchor.	3 / 3
Actionability	It provides multiple complete, executable Go code blocks (NewAx, NewFlow, Execute, Returns, and a Forward call with ctx/client) that are copy-paste ready, matching the fully-executable anchor.	3 / 3
Workflow Clarity	The Core Pattern → More Patterns → Run a flow sequence is clear, but there are no explicit validation checkpoints or feedback loops, and the guidance to validate against `examples/` points to a non-existent bundle.	2 / 3
Progressive Disclosure	Sections are well organized, but the body references `API.md`, `axir-api.json`, `axir-capabilities.json`, and `examples/` that do not exist in the bundle, so the signaled one-level-deep references are not actually realized.	2 / 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.

The description is comprehensive and well-triggered, covering a clear niche with explicit when/what guidance. Its main weakness is heavy reliance on technical jargon rather than natural user phrasing for its trigger terms.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete capabilities — "flows, nodes, program graphs, nested programs, dynamic options, caching, and optimizer components" — matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	It explicitly answers both what (writing Go code with the named package for the listed capabilities) and when (the explicit "Use when writing Go code with ..." trigger), matching the anchor for clearly answering both with explicit triggers.	3 / 3
Trigger Term Quality	"Use when writing Go code" is a natural trigger, but the capability terms ("program graphs", "nested programs", "dynamic options", "optimizer components") and the package import path are technical jargon a user would not naturally say, so common natural variations are missing.	2 / 3
Distinctiveness Conflict Risk	Scoping to the specific import path `github.com/ax-llm/ax/packages/go` and AxFlow concepts gives it a clear niche unlikely to trigger for unrelated skills, matching the distinct-triggers anchor.	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-flow/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.