Name: ax-go-signature
Rating: 54.400000000000006 (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

61%

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%

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 and pattern-rich with executable Go snippets, but it is undercut by an inconsistent API-surface listing, the absence of any sequenced workflow with validation, and references to bundle files that are not actually provided.

Suggestions

Reconcile the API surface with the import alias: use ax.-prefixed symbols (e.g. ax.NewSignature, ax.AxSignature) and demonstrate axllm.S/axllm.Fn/axllm.Tool in an example or drop them.

Add a short end-to-end workflow (declare signature → render schema → attach to AxGen → forward) with a validation/compile check step before proceeding.

Either bundle the referenced files (API.md, axir-api.json, axir-capabilities.json, examples/) or reword the references so the skill is self-contained.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward, with one-line rationales per pattern and no explanation of Go or library concepts Claude already knows; every section earns its place.	3 / 3
Actionability	Concrete Go examples are present, but the "Relevant API Surface" lists axllm.S, axllm.Fn, and axllm.Tool with an axllm. prefix that contradicts the ax import alias and is never demonstrated in any example, leaving key details incomplete.	2 / 3
Workflow Clarity	Patterns and guardrails are listed and a loose "start from examples, then browse the gallery" order exists, but there is no sequenced multi-step workflow or validation checkpoint for the generation flow.	2 / 3
Progressive Disclosure	Sections are well-organized and references (API.md, axir-api.json, axir-capabilities.json, examples/) are signaled, but no bundle files exist, so the referenced detailed materials are absent and the disclosure promise is unfulfilled.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 well-scoped to a distinct niche and carries an explicit trigger, but it leads with an imperative clause and lacks a third-person action statement, leaving the "what" only implied and the trigger terms partly jargon-laden.

Suggestions

Lead with a third-person action clause before the trigger, e.g. "Generates string signatures, field descriptors, and JSON schemas in Go using …"

Soften framework jargon ("field descriptors", "typed tool argument shapes") or pair each with a natural synonym a user would actually say.

Split the single sentence into a clear "what" statement plus a separate "Use when …" trigger clause.

Dimension	Reasoning	Score
Specificity	The description lists concrete capabilities ("string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes"), but it is framed as an imperative "Use when writing Go code…" with no third-person action statement, so the voice penalty applies.	2 / 3
Completeness	The "when" is explicit ("Use when writing Go code with …"), but the "what" is only implied through the capability list rather than stated as a clear action, so it does not clearly answer both.	2 / 3
Trigger Term Quality	"Go code", "JSON schema", and "validation" are natural user terms, but "field descriptors" and "typed tool argument shapes" are Ax-specific jargon a user would rarely say unprompted, leaving common variations uncovered.	2 / 3
Distinctiveness Conflict Risk	It is tightly scoped to the Go Ax package for signature/schema work and explicitly excludes TypeScript-only APIs, giving it a clear niche unlikely to trigger the wrong skill.	3 / 3
	Total	9 / 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-signature/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.