CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

writing-evals

Scaffolds evaluation suites for the Axiom AI SDK. Generates eval files, scorers, flag schemas, and config from natural-language descriptions. Use when creating evals, writing scorers, setting up flag schemas, or configuring axiom.config.ts.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable and efficient, with excellent tables, code, and a validated 8-step workflow. Its main defect is that the progressive-disclosure layer is broken: every reference file cited in the Reference section is absent from the bundle, so the detailed patterns it defers to are unreachable.

Suggestions

Create the missing reference files the body cites — reference/scorer-patterns.md, reference/api-reference.md, reference/flag-schema-guide.md, and reference/templates/ — or remove the Reference section until they exist, since every detailed-pattern and type-signature lookup currently dead-ends.

Add an explicit fix-and-retry loop to the Workflow section (e.g., "if eval-validate reports errors, fix them and re-run before scaffolding coverage") so error recovery is part of the sequence rather than only implied by the Common Pitfalls table.

Trim the Philosophy section and its restated points (e.g., "Data drives coverage") since the Data Design Guidelines table already conveys them concretely.

DimensionReasoningScore

Conciseness

The body is dense and SDK-specific — tables, exact import paths, and commands dominate, with no generic-concept padding (it never explains what evals or SDKs are in the abstract). Minor trimming is possible: the "Philosophy" section ("Evals are tests for AI. Every eval answers: 'does this capability still work?'") and the "Data drives coverage" prose restate points made concretely elsewhere, which keeps it below anchor 5.

4 / 5

Actionability

Guidance is fully executable: a copy-paste-ready Eval file template with exact import paths (`import { Eval } from 'axiom/ai/evals'`), an onlineEval signature, a complete CLI command table, per-script usage examples (e.g., `eval-scaffold classification support-agent categorize`), and a pitfalls table mapping exact error strings to fixes. This matches anchor 5's copy-paste-ready standard with common cases covered.

5 / 5

Workflow Clarity

The Workflow section gives a clear 8-step sequence with concrete commands and explicit validation checkpoints (validate structure, analyze coverage gaps, `--debug` local run before deploy), plus a separate 4-step "How to Start" process. It stops short of anchor 5 because the feedback loops are not wired into the workflow itself — there is no "if validation fails, fix and re-run" step, only an indirect error-recovery mapping in the Common Pitfalls table.

4 / 5

Progressive Disclosure

The Reference section is clearly signaled and one level deep ("read these on demand" with per-file descriptions), which would score 5 — but scoring against the actual bundle, all four referenced paths (`reference/scorer-patterns.md`, `reference/api-reference.md`, `reference/flag-schema-guide.md`, `reference/templates/`) do not exist; only the scripts directory is present and its references check out. Dangling references mean the promised detail layer is entirely missing, which is worse than anchor 4's "minor organization gaps" and leaves the structure well-intentioned but functionally broken.

3 / 5

Total

16

/

20

Passed

Description

88%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: third-person, concise, and concrete about both capabilities and trigger conditions. The only gaps are a few missing natural synonyms and mild overlap risk on the generic phrase "creating evals" for users outside the Axiom ecosystem.

DimensionReasoningScore

Specificity

"Scaffolds evaluation suites for the Axiom AI SDK. Generates eval files, scorers, flag schemas, and config from natural-language descriptions" lists four concrete, distinct artifacts the skill produces — comprehensive coverage of its domain with no vague filler. Anchor 4 would apply if coverage had notable gaps, but every core deliverable of an eval suite is named.

5 / 5

Completeness

It explicitly answers both questions: the "what" is two sentences of concrete generation actions, and the "when" is an explicit "Use when..." clause with four concrete trigger phrases. This mirrors the anchor-5 example's structure; anchor 4 would require the when-clause to be less explicit.

5 / 5

Trigger Term Quality

"creating evals, writing scorers, setting up flag schemas, or configuring axiom.config.ts" gives good natural keyword coverage including a concrete filename, matching the anchor-4 example's quality. It misses synonyms and extensions a user might naturally say (e.g., ".eval.ts", "tests for my AI feature", "LLM-as-judge"), so it falls short of the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Axiom AI SDK" and "axiom.config.ts" anchor a clear niche with distinct triggers, but "creating evals" and "writing scorers" are generic phrases that could also trigger non-Axiom evaluation-writing skills — minor overlap risk with closely related skills, matching anchor 4 rather than anchor 5's minimal-conflict bar.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openclaw/clawhub

Path

.agents/skills/writing-evals/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.