CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-python-playbook

Use when writing Python code with `axllm` for the playbook() context-engineering surface, agent-bound verified evolution, run-end learning, online updates, and rendering a playbook into a program.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./packages/python/skills/ax-python-playbook/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 terse, well-organized body that respects the token budget and sets useful guardrails. Its main weaknesses are placeholder-laden code that is not copy-paste executable and the absence of explicit validation/rollback checkpoints for the evolve workflow it promotes.

Suggestions

Make the Core Pattern executable by showing how 'llm', 'examples', and 'metric_fn' are constructed (e.g. via a no-key example) or by pointing to one specific runnable example file path.

Add a short numbered workflow for evolve/refine/render with an explicit validation checkpoint (e.g. 'only accept evolved rules when verification passes; otherwise rely on exact rollback').

Give each optimizer name in 'Relevant API Surface' a one-line role, or move the list into a pointer to a specific API.md section.

DimensionReasoningScore

Conciseness

The body is lean and fact-dense ('Language: Python.', 'Package: `axllm`.') with no explanations of concepts Claude already knows and no padding. Every section earns its tokens.

5 / 5

Actionability

The Core Pattern shows real call shapes but relies on undefined placeholders ('llm', 'examples', 'metric_fn'), making it pseudocode-like rather than executable. It defers executable detail to external package examples instead of including it, matching the 3 anchor better than the 'minor gaps' 4 anchor.

3 / 5

Workflow Clarity

The Core Pattern implies a rough sequence (ax -> playbook -> evolve) and 'When To Use' enumerates tasks, but no explicit checkpoints or validation/rollback guidance is given for the risky evolve operation. Sequence present with implicit checkpoints, matching the 3 anchor.

3 / 5

Progressive Disclosure

The ~44-line body is cleanly sectioned and the skill ships no bundle files, but detail pointers ('API.md', 'axir-api.json', 'examples/') name package files rather than clearly-signaled one-level-deep skill references, and the 'Relevant API Surface' is a bare inline name list. Good structure with minor organization gaps — the 4 anchor.

4 / 5

Total

15

/

20

Passed

Description

71%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 distinctive, explicitly triggered description with several concrete capabilities, held back by jargon-heavy trigger terms. Users who need it would likely match on 'axllm' or 'playbook', but natural-language synonyms are thin.

Suggestions

Add natural trigger phrases users would actually type, e.g. 'when the user wants to evolve, optimize, or refine an axllm program or playbook'.

Soften internal jargon ('agent-bound verified evolution', 'run-end learning') with user-facing wording such as 'learning from failed runs' or 'verified prompt/rules evolution with rollback'.

Include one or two synonyms for the core surface (e.g. 'context engineering', 'prompt optimization') to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('playbook() context-engineering surface', 'agent-bound verified evolution', 'run-end learning', 'online updates', 'rendering a playbook into a program') rather than vague language. Minor gaps in coverage keep it below the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both: 'what' via the enumerated capability list and 'when' via the leading 'Use when writing Python code with axllm' clause. Not a 5 because the 'when' is generic and lacks concrete trigger phrases a user would actually say.

4 / 5

Trigger Term Quality

'Python code', 'axllm', and 'playbook' are relevant keywords a user might say, but phrases like 'agent-bound verified evolution' and 'run-end learning' are internal jargon users would not naturally utter. Missing common variations and synonyms, matching the 3 anchor rather than the good-coverage 4 anchor.

3 / 5

Distinctiveness Conflict Risk

Names a specific package ('axllm') and function ('playbook()'), carving out a clear niche with distinct triggers and minimal risk of firing for unrelated skills.

5 / 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-playbook/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.