CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

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

Quality

Content

50%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 body starts strong with a clear core pattern and concrete Go snippets, then degrades into dense, repetitive prose spec dumps for the decision-evidence and provider sections with no code, no guided workflow, and no actual reference files to offload detail to. It reads as a compacted API reference rather than a skill that steers an agent toward correct usage.

Suggestions

Move the Typesafe/Jev, OpenAI Decisions, and Google Gemini Decisions sections into separate reference files (e.g. references/typesafe.md, references/openai-decisions.md) and keep only a short summary plus a one-line pointer in SKILL.md, ensuring the referenced files actually exist in the bundle.

Replace the repeated prose restatements of shared behavior (evidence/refusal-return semantics, trueThreshold default, probability normalization rules, no token streaming) with a single shared section that each provider section references.

Add short executable Go snippets for the provider sections (e.g. constructing an axllm.OpenAIDecisions request and reading the answer) and a brief decision guide for when to use each provider, mirroring the concrete style of the Core Pattern section.

DimensionReasoningScore

Conciseness

The prose is dense and assumes Claude's intelligence (no padding with known concepts), but the same facts are restated across provider sections: "(evidence, refusal return) for an answered/refused union" appears three times, the trueThreshold 0.5 default three times, "probabilities...never normalized" three times, and "Numeric bounds never define a score rubric" twice. Not 4 because this repetition and the volume of inline edge-case constraints (image byte limits, pixel bounds) could be meaningfully tightened or moved out.

3 / 5

Actionability

The early sections give concrete Go snippets ("sig := ax.NewSignature(...)", "program.Signature = signature"), but roughly the last 60% of the body (Decision evidence, Typesafe/Jev, OpenAI Decisions, Google Gemini Decisions) is prose-only with no executable code, and the snippets that do exist are fragments without imports or complete programs. Not 2 because the guidance includes specific API names and call shapes rather than high-level hints only.

3 / 5

Workflow Clarity

Section structure per subsystem exists and Guardrails give some decision guidance ("Start from package examples...before inventing a new call shape"), but there is no sequenced workflow or decision path for choosing among the four provider subsystems, and the doc is reference material rather than a guided process. Not a simple single-task skill, so the simple-skill exception does not apply.

3 / 5

Progressive Disclosure

Headers organize the content and reference files are named ("Package API docs: `API.md` and `axir-api.json`", "Runnable examples: `examples/`"), but no bundle files exist, so those references are dangling, and the long provider spec sections are inlined where separate reference files clearly belong. Not 2 because structure and signaled references are present; not 4 because the bulk of the content is not appropriately split.

3 / 5

Total

12

/

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, concise, with an explicit "Use when" trigger naming the exact package and a concrete list of capabilities. Its only weakness is that the capability list under-represents the decision-evidence and provider-decisions content that dominates the skill body.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ("string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes") tied to a named package. Not 5 because the description omits the decision-evidence, Typesafe/Jev, and provider-decisions work that makes up most of the skill body, so coverage gaps exceed minor.

4 / 5

Completeness

Explicitly answers both: what ("string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes") and when ("Use when writing Go code with `github.com/ax-llm/ax/packages/go`") with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Includes natural terms users would say ("Go code", "signatures", "JSON schema", "validation") plus the package path. Not 5 because common synonyms and variations like "Ax", "axllm", or "schema generation" are missing; not 3 since keyword coverage is good rather than partial.

4 / 5

Distinctiveness Conflict Risk

Scoped to a single specific package path, giving it a clear niche with distinct triggers and minimal conflict risk against generic Go or schema 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-signature/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.