CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-python-gepa

Use when writing Python code with `axllm` for GEPA, Pareto tradeoffs, reflection clients, metric budgets, optimizer state, and artifacts.

Quality

76%

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

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.

The body is admirably lean and dense with package-specific knowledge Claude would not already have, and its guardrails are unusually substantive. Its weaknesses are the non-executable Core Pattern skeleton, the absence of any ordered workflow or validation checkpoints for budget-consuming optimizer runs, and references to bundle files that are not actually present.

Suggestions

Replace the Core Pattern skeleton with one fully executable example that shows how reflection_client, request, and evaluator are actually constructed (e.g., drawn from the package examples), so the snippet is copy-paste ready.

Add a short numbered workflow for a typical GEPA run (set metric budget → bootstrap demos if needed → run optimize → inspect artifact metadata for baselineScore vs bestScore) with an explicit verification step on the resulting Pareto front.

Either ship the referenced files (API.md, axir-api.json, axir-capabilities.json, examples/) in the bundle or inline the minimal needed content, so the body's pointers resolve to real resources.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: bullet-style Package Facts, a four-line Core Pattern, and guardrails consisting entirely of non-obvious package semantics (baseline score placement, metric-budget accounting, demo freshness) that Claude could not know. Only trivial redundancy exists ("Language: Python" restating the description), which does not rise to the over-explanation of a 4.

5 / 5

Actionability

The Core Pattern is a skeleton with undefined placeholders — `AxGEPA(reflection_client)` and `engine.optimize(request, evaluator)` never show how to construct the reflection client or evaluator — so it functions as an API shape sketch rather than executable code. There is some concrete guidance (the API surface list and 'Start from package examples'), matching the pseudocode-with-missing-details anchor rather than the mostly-executable anchor at 4.

3 / 5

Workflow Clarity

Content is organized by topic (When To Use, Package Facts, Core Pattern, Guardrails) with no sequenced process and no validation checkpoints, despite covering budget-consuming optimizer runs where a checkpoint discipline would help. It is coherent with clear usage triggers — above the rough-sequence-with-many-gaps anchor at 2 — but the sequence-present-but-checkpoints-missing anchor at 3 is the best fit given guidance exists without an ordered flow.

3 / 5

Progressive Disclosure

Sections are well organized for a sub-50-line skill, but the referenced resources — "API.md and axir-api.json", "axir-capabilities.json", "examples/" — do not exist in the bundle, so the pointers cannot actually be followed. This lands on the some-structure-with-imperfectly-usable-references anchor at 3 rather than 4, since navigation to deeper detail is asserted but unverifiable.

3 / 5

Total

14

/

20

Passed

Description

78%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: it opens with an explicit 'Use when' trigger, names a highly specific niche, and enumerates concrete capability areas with terms the target user would naturally say. The main improvement would be separating the 'what' (distinct capability statements) from the 'when' trigger and adding a few synonymous trigger phrases.

DimensionReasoningScore

Specificity

The description names the domain ("writing Python code with `axllm`") and lists several concrete capability areas — "GEPA, Pareto tradeoffs, reflection clients, metric budgets, optimizer state, and artifacts" — giving specific coverage with only minor gaps. It falls short of a 5 because these are topic nouns rather than comprehensive concrete actions (e.g., 'Run the GEPA optimizer', 'Track metric budgets'), and above a 3 because it covers more than 1-2 concrete items.

4 / 5

Completeness

It has an explicit 'when' ("Use when writing Python code with `axllm` for...") and a 'what' conveyed through the enumerated capability areas, satisfying both halves. The 'what' is merged into the trigger clause rather than stated as distinct capabilities, so it is not the fully explicit what-and-when pairing of a 5; it is clearly above a 3 because the trigger guidance is explicit, not weakly implied.

4 / 5

Trigger Term Quality

Terms like "GEPA", "axllm", "Pareto tradeoffs", "reflection clients", and "metric budgets" are exactly the phrases a user of this package would naturally say, giving good keyword coverage. A few natural terms are missing (e.g., 'prompt optimization', 'DSPy', 'reflection'), so it does not reach the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche — the generated `axllm` Python package and its GEPA optimizer — with distinct triggers ("GEPA", "Pareto tradeoffs", "reflection clients") that minimal other skills would claim. Conflict risk with generic Python or optimization skills is minimal.

5 / 5

Total

17

/

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-gepa/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.