ax-python-signature

Use when writing Python code with `axllm` for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

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

Quality

Content

75%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 well-structured, mostly lean code skill with executable patterns, clear guardrails, and sensible external references. It is strong across all dimensions; the main gaps are an undefined-variable final example and references to files not present in the bundle.

Dimension	Reasoning	Score
Conciseness	Lean section intros each earn their place (e.g. "Use the string form when field names and types are enough.") and avoid explaining concepts Claude already knows; a few framing sentences like "Python exposes the native fluent builder..." could be trimmed slightly.	4 / 5
Actionability	Provides concrete, executable Python across Core Pattern and all More Patterns subsections with the real `axllm` API, but the final reuse snippet references undefined `client` and `inputs`, leaving a minor gap.	4 / 5
Workflow Clarity	Guardrails give clear decision guidance ("Start from package examples", "Use no-key examples for deterministic local checks") and the body directs starting from `examples/`, supplying a clear sequence for a single-purpose skill with only minor checkpoint gaps.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and one-level-deep references signaled in Package Facts ("API.md", "axir-api.json", "examples/"), though those referenced files are not present in the skill bundle, leaving a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

75%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 focused, well-structured description that names the package, lists concrete capabilities, and includes an explicit "Use when" trigger. It is strong across all dimensions with only minor room for more user-natural trigger phrasing.

Dimension	Reasoning	Score
Specificity	Names the package and lists several concrete capabilities ("string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes"), giving broad coverage with only minor gaps (e.g. tools are only implied via "typed tool argument shapes").	4 / 5
Completeness	Explicitly states both what (writing Python code with axllm for the listed capabilities) and when ("Use when writing Python code with `axllm`..."), but the trigger is somewhat self-referential to the package rather than naming external user situations.	4 / 5
Trigger Term Quality	Includes natural terms a user in this domain would say ("Python code", "JSON schema", "validation", "signatures", "tool arguments"), though "field descriptors" and "typed tool argument shapes" lean slightly technical and a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Tying triggers to the specific `axllm` package and signature/schema concepts gives a clear niche with minimal conflict risk, with only minor overlap against general Python-coding skills.	4 / 5
	Total	16 / 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/python/skills/ax-python-signature/SKILL.md
Commit: 3951b05

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.