CtrlK
BlogDocsLog inGet started
Tessl Logo

ax-rust-playbook

Use when writing Rust 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.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 concise and well-structured with concrete code and an explicit API surface. Its main weakness is workflow clarity: the evolve/refine flow lacks explicit validation checkpoints and feedback loops despite involving verified evolution and rollback.

Suggestions

Add an explicit workflow sequence for evolve/refine with validation checkpoints (e.g., verify examples, run metric_fn, confirm rollback on failure) to raise workflow_clarity.

Make the Core Pattern more executable by including the necessary imports and showing how llm, examples, and metric_fn are constructed, or explicitly note they are contextual placeholders.

Clearly signal the referenced artifacts (API.md, examples/, axir-capabilities.json) as navigable references with their purpose, and ensure they exist in the bundle or note they are package-generated.

DimensionReasoningScore

Conciseness

The body is lean throughout: a one-sentence intro, terse factual bullets in Package Facts, a compact code pattern, and no padding explaining Rust or library basics that Claude already knows.

5 / 5

Actionability

Provides a concrete Rust Core Pattern and a named API surface list, but the code snippet references undefined context (llm, examples, metric_fn, OpenAICompatibleClient) and omits imports, so it is not fully copy-paste executable.

4 / 5

Workflow Clarity

A loose sequence exists (build program, construct playbook, evolve), but there are no explicit validation checkpoints or feedback loops for the evolve/refine operations, which involve verification and rollback that should be sequenced.

3 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections and stays under 50 lines; however, referenced artifacts (API.md, axir-api.json, axir-capabilities.json, examples/) are listed in Package Facts rather than navigated as signaled one-level-deep references, and no bundle files are present to verify them.

4 / 5

Total

16

/

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.

The description is strong: it pairs an explicit 'Use when' trigger with a concrete enumeration of capabilities tied to a distinct package niche. The only weakness is that some capability phrasing leans on domain jargon rather than user-natural language.

DimensionReasoningScore

Specificity

Lists several concrete actions (playbook() surface, agent-bound verified evolution, run-end learning, online updates, rendering into a program), but several are framed as abstract domain jargon rather than crisp capabilities, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (the enumerated capabilities) and 'when' via the 'Use when writing Rust code with `axllm`' trigger clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger terms 'writing Rust code with `axllm`' and 'playbook' are present and would be said by a user of this package, though a few common synonyms or variations are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Rust + axllm + playbook context-engineering) with distinct triggers, making conflict with unrelated skills minimal.

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.

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