CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-python-ai

Use when writing Python code with `axllm` for named deployment profiles, generic provider clients, model selection, OpenAI-compatible calls, Responses, Gemini, Anthropic, routers, and balancers.

Quality

72%

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/python/skills/ax-python-ai/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.

An extremely information-dense reference that reliably delivers non-obvious package facts without padding, undermined by a near-total absence of executable code (one 3-line snippet), no sequenced workflows or validation checkpoints for the complex processes it describes, and monolithic inlining of per-provider detail that belongs in separate reference files. The compressed run-on prose also makes sections hard to scan despite their accuracy.

Suggestions

Add copy-paste-ready code examples for the most common tasks (profile selection, structured output, router/balancer setup) instead of a single 3-line core-pattern snippet, since the referenced example paths are not part of the skill bundle.

Split the per-provider sections (Typesafe/Jev, OpenAI Decisions, Gemini Decisions) and the per-model pricing/sampling minutiae into separate reference files linked from a concise overview, keeping SKILL.md to the core pattern, when-to-use guidance, and guardrails.

Convert key multi-step processes (adaptive balancing setup, credential callbacks, Vertex configuration) into explicitly numbered steps with verification points, e.g., validate routing with scripted no-key fixtures before live calls.

DimensionReasoningScore

Conciseness

Nearly every sentence carries package-specific facts Claude cannot know ("retryableStatusCodes, by default 500, 408, 429, 502, 503, 504 and 529", "16 MiB per decoded image, 32 MiB per request", exact pricing and thresholds), with no padding or explanation of known concepts — matching anchor 4. It is not 5 because long multi-clause run-on sentences (e.g., the sampling rules paragraph) could be tightened, and not 3 because nothing explains concepts Claude already knows.

4 / 5

Actionability

Only one executable snippet exists ("llm = ai(\"openai\", api_key=os.environ[\"OPENAI_API_KEY\"])"); the rest is declarative rules with exact option names and error semantics but no copy-paste-ready code for the many covered scenarios, and referenced example paths (src/examples/python/generation/, examples/adaptive_balancer_no_key) are not in the bundle. This matches anchor 3 (concrete but incomplete guidance); it exceeds anchor 2 because the decision rules are highly specific, and falls short of anchor 4 because a coding skill with a single 3-line snippet has more than minor gaps.

3 / 5

Workflow Clarity

The body is a topic-organized reference rather than a sequenced workflow; rough sequences exist ("Start with `examples/adaptive_balancer_no_key` for store/reducer syntax, then use the cataloged provider-backed adaptive-balancer example") but complex processes like session work, caching, and balancing lack explicit steps, checkpoints, or feedback loops, matching anchor 3. It is not 4 because validation checkpoints are absent or implicit, and not 2 because section structure and decision rules provide genuine orientation.

3 / 5

Progressive Disclosure

Sixteen header sections give structure, but roughly 200 lines of per-provider API detail (Typesafe/Jev, OpenAI Decisions, Gemini Decisions, per-model pricing and sampling rules) are inlined in SKILL.md — content that clearly belongs in separate reference files — and mentions of API.md and examples/ are scattered rather than clearly signaled navigation, with no bundle files present. This matches anchor 3; it is not 4 because major referenceable content is inline, and not 2 because the headers provide real, navigable structure.

3 / 5

Total

13

/

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 solid description with an explicit use-when trigger, a specific package anchor, and broad concrete coverage of the package's feature areas. Its main weakness is that the 'what' is only implied by the feature list — it never states what the skill itself provides (API docs, examples, manifests) — and the items are feature nouns rather than concrete actions.

DimensionReasoningScore

Specificity

The description enumerates many concrete capability areas ("named deployment profiles, generic provider clients, model selection, OpenAI-compatible calls, Responses, Gemini, Anthropic, routers, and balancers"), matching anchor 4's several specific items with minor gaps. It falls short of anchor 5 because the items are feature nouns rather than concrete actions, and beyond anchor 3 because coverage is comprehensive rather than 1-2 items.

4 / 5

Completeness

An explicit "Use when writing Python code with axllm..." clause answers 'when' directly, and the 'what' (writing Python code with axllm for the listed features) is embedded in the same clause, matching anchor 4. It is not 5 because the 'what' is thin — the description never states what the skill provides (API docs, manifests, examples) — and not 3 because the trigger guidance is explicit rather than weakly implied.

4 / 5

Trigger Term Quality

Natural domain terms like "Python", "OpenAI-compatible", "Gemini", "Anthropic", "routers", and "balancers" match what a user of this package would say, fitting anchor 4's good coverage with a few missing terms. It is not 5 because common variations such as "chat completions", "failover", or "LLM" are absent, and not 3 because keyword coverage is broad and domain-appropriate.

4 / 5

Distinctiveness Conflict Risk

Anchoring to the specific package `axllm` gives a clear niche with mostly distinct triggers, fitting anchor 4. It is not 5 because generic provider names (Gemini, Anthropic, OpenAI-compatible) create minor overlap risk with general provider-API skills, and not 3 because the package anchor keeps conflict risk low.

4 / 5

Total

16

/

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/python/skills/ax-python-ai/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.