Name: ax-go-signature
Rating: 62.4 (1 reviews)
Author: ax-llm

ax-go-signature

Use when writing Go code with `github.com/ax-llm/ax/packages/go` for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/go/skills/ax-go-signature/SKILL.md

Quality

Content

65%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 concise, actionable pattern reference with good code examples, weakened by an API-surface naming inconsistency and by referencing bundle files (API.md, examples/, manifests) that are not present. It reads as a catalog rather than a sequenced workflow.

Suggestions

Resolve the import-alias inconsistency: the examples use `ax.` while "Relevant API Surface" lists `axllm.S`, `axllm.FieldType`, `axllm.AxSignature`, `axllm.Fn`, `axllm.Tool` — pick one prefix and apply it everywhere.

Either ship the referenced bundle files (API.md, axir-api.json, axir-capabilities.json, examples/) or remove the references so progressive disclosure points to real, navigable material.

Add a brief ordered "how to approach a new signature" sequence (pick a pattern from examples → declare fields → render JSON schema → attach to AxGen → Forward) so the workflow is explicit rather than implied.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with one-line intros followed by code, but a few lines like "A class field constrains the model to a known label set" and the Package Facts list contain minor over-explanation that could be trimmed.	4 / 5
Actionability	Multiple concrete, largely copy-paste-ready Go snippets cover the common cases, but the "Relevant API Surface" uses an `axllm.` prefix that conflicts with the `ax` import alias used in the examples, and Forward references undefined ctx/client/inputs.	4 / 5
Workflow Clarity	The content is organized as a pattern catalog (Core Pattern, More Patterns, examples) with a loose suggested order, but there is no explicit sequenced workflow with validation checkpoints; this is a non-destructive code skill so the destructive cap does not apply.	3 / 5
Progressive Disclosure	The SKILL.md itself is well-sectioned and signals one-level-deep references (API.md, axir-api.json, axir-capabilities.json, examples/), but no bundle directories or referenced files actually exist, so the disclosure chain is broken and navigation to the detail material would fail.	3 / 5
	Total	14 / 20 Passed

Description

83%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 specific, well-scoped description that names concrete capabilities and an explicit Use-when trigger tied to a particular package. It could enumerate more natural trigger variations to fully reach the top of the trigger-term and completeness anchors.

Suggestions

Add synonymous trigger phrases users might actually say (e.g. "Ax signatures", "Go signature parsing", ".go signature contracts") to broaden trigger-term coverage.

Split the single "Use when" clause into a few distinct scenarios (declaring contracts, generating JSON schemas, validating tool args) so the when-guidance is more explicit.

Dimension	Reasoning	Score
Specificity	The description enumerates five concrete capabilities — "string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes" — giving comprehensive coverage of the package's actions rather than vague language.	5 / 5
Completeness	Both the what (the listed capabilities) and the when ("Use when writing Go code with github.com/ax-llm/ax/packages/go") are present, but the trigger is a single combined clause rather than multiple distinct concrete trigger phrases.	4 / 5
Trigger Term Quality	Terms like "writing Go code", "string signatures", "JSON schema output", and "validation" are natural developer keywords with good coverage, but no synonyms or file extensions are included, so it falls short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The trigger is scoped to a specific generated package path (github.com/ax-llm/ax/packages/go), establishing a clear niche with minimal risk of firing for unrelated skills.	5 / 5
	Total	18 / 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-signature/SKILL.md
Commit: 781623e

Reviewed: 2 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.