ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

llm-evaluation

Deep LLM evaluation workflow—quality dimensions, golden sets, human vs automatic metrics, regression suites, offline/online signals, and safe rollout gates for model or prompt changes. Use when shipping prompt updates, swapping models, or building eval harnesses for agents and RAG.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/codenova58/llm-evaluation
Or

LLM Evaluation (Deep Workflow)

Evaluation turns “it feels better” into reproducible evidence. Design around failure modes your product cares about—not only aggregate scores.

When to Offer This Workflow

Trigger conditions:

  • Prompt or model change; need before/after proof
  • Building CI for LLM outputs; flaky quality in production
  • RAG/agents: grounding, tool use, safety regressions

Initial offer:

Use six stages: (1) define quality & constraints, (2) build datasets & rubrics, (3) automatic metrics, (4) human evaluation, (5) regression & gates, (6) online validation & iteration. Confirm latency/cost budgets and risk (PII, safety).


Stage 1: Define Quality & Constraints

Goal: Name dimensions that map to user harm if they fail.

Typical dimensions (pick what matters)

  • Correctness / task success; groundedness (RAG); faithfulness to sources
  • Safety: policy violations, jailbreaks, PII leakage
  • Style: tone, brevity, format (when product-critical)
  • Robustness: paraphrase, multilingual, edge inputs

Constraints

  • Max tokens, latency p95, cost per request; locale requirements

Exit condition: Weighted priority of dimensions; non-goals stated.


Stage 2: Datasets & Rubrics

Goal: Fixed eval sets + clear scoring rules.

Practices

  • Stratify by intent: easy/medium/hard; adversarial slice separate
  • Rubrics: 1–5 scales with anchors; binary checks for safety
  • Version datasets (git or table); no silent edits without changelog
  • Privacy: synthetic or redacted real examples per policy

Exit condition: Golden set size justified; inter-rater plan if human scoring.


Stage 3: Automatic Metrics

Goal: Fast signals—know limitations.

Options

  • Reference-based: BLEU/ROUGE—often weak for assistants
  • Model-as-judge: fast, biased—calibrate vs human
  • Task-specific: exact match, JSON schema validity, tool-call args match
  • RAG: citation overlap, nugget recall, entailment models (use carefully)

Hygiene

  • No training on test; detect leakage from prompts

Exit condition: Each auto metric has known blind spots documented.


Stage 4: Human Evaluation

Goal: Authoritative judgment where automatic metrics lie.

Design

  • Sample size for confidence; blind A/B when possible
  • Guidelines + examples; adjudication for disagreements
  • Locale-native raters when language quality matters

Exit condition: Human scores correlate enough with auto for ongoing monitoring—or you rely on human for release.


Stage 5: Regression & Gates

Goal: Block bad deploys in CI or release pipeline.

Gates

Metadata

Stars3453
Views0
Updated2026-03-26
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-codenova58-llm-evaluation": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.