CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

77%

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-flow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The core flow patterns are excellent — executable, well-chosen Go examples that cover the main use cases. Quality drops in the back half: the Astra Session Work section is an impenetrable prose wall that should be split into a reference file, and the skill reads as a pattern dump rather than a guided workflow.

Suggestions

Move the 'Astra Session Work' section into a separate reference file (e.g. references/astra-sessions.md) and keep a 2–3 line summary with a clearly signaled link in SKILL.md, cutting the dense inline prose.

Add a short step sequence for typical usage (start from an example → adapt reads/writes → run with no-key transport to verify → switch to a real provider), making the existing guardrails explicit checkpoints.

Resolve the package-identifier inconsistency between `ax.NewFlow` in the examples and `axllm.NewFlow` in 'Relevant API Surface' so the copy-paste code matches the documented API.

DimensionReasoningScore

Conciseness

Mostly package-specific facts with no explanation of known concepts, but the 'Astra Session Work' section is a dense run-on prose wall with repeated 'as TypeScript does / as in TypeScript' hedging and redundant restatements of cancellation semantics that could be tightened considerably.

3 / 5

Actionability

The flow construction, Forward, StreamingForward, and caching examples are concrete, executable Go code covering the common cases. Minor gaps: the Astra session section is abstract prose with no code, and the body uses `ax.NewFlow` while 'Relevant API Surface' lists `axllm.NewFlow`, an unresolved inconsistency.

4 / 5

Workflow Clarity

The body is organized as a pattern library (core pattern → more patterns → Astra → guardrails) with implicit ordering ('Start from the complete programs under `examples/`'), but there is no explicit step sequence and validation checkpoints are only implicit via guardrails like using no-key examples for deterministic checks.

3 / 5

Progressive Disclosure

Header structure is good, but references to `API.md`, `axir-api.json`, `axir-capabilities.json`, and `examples/` are buried in a 'Package Facts' bullet list rather than clearly signaled navigation, and the entire Astra session section (~26 lines of dense detail) is inlined content that belongs in a separate reference file.

3 / 5

Total

13

/

20

Passed

Description

87%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: third-person trigger form, explicit 'Use when' clause tied to an exact package path, and a concrete capability list. The only weakness is that capabilities are named as noun topics rather than actions, which slightly limits natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the exact package domain and lists several concrete capability areas ("flows, nodes, program graphs, nested programs, dynamic options, caching, and optimizer components"), but presents them as topics rather than explicit actions, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

It explicitly answers both what (writing Go code with the package for a concrete list of subsystems) and when ("Use when writing Go code with `github.com/ax-llm/ax/packages/go`") with concrete trigger phrases; the 'when' is already fully explicit, so the score-4 caveat does not apply.

5 / 5

Trigger Term Quality

Natural terms like "Go code", "flows", "nodes", "caching", and "program graphs" give good keyword coverage, but common user variations such as "AxFlow", "workflow", or "agents" are missing.

4 / 5

Distinctiveness Conflict Risk

Triggering is pinned to one exact package import path, giving it a clear niche with minimal risk of firing for unrelated skills.

5 / 5

Total

18

/

20

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.

Validation — 15 / 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

Path

packages/go/skills/ax-go-flow/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.