design-test-rubric

Design an eight-category scoring rubric with severity taxonomy and versioning.

4|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/smartmarbles/helm --skill design-test-rubric
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-test-rubric
Source: https://github.com/smartmarbles/helm/tree/main/.github/skills/design-test-rubric
Command: npx skills add https://github.com/smartmarbles/helm --skill design-test-rubric

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design-test-rubric provides a structured blueprint to craft rigorous evaluation rubrics for PROBE-like AI agent systems, ensuring consistency and comparability across runs.

Core Features & Use Cases

  • Eight-category rubric with weights summing to 100, tailored to observed failure modes and verification needs.
  • Comprehensive severity taxonomy (critical/major/minor) with explicit sub-score rules and a hard cap on critical violations.
  • Fixed violation log schema, run-tagging conventions, and a reusable scorecard template for all rubric revisions.
  • Clear versioning and changelog workflow for iterative rubric improvements.

Quick Start

Write a starter rubric by listing eight categories with weights, define severity rules, specify the violation fields, and lock in the scorecard template; then bump the minor version and add a changelog entry.

Frequently Asked Questions about design-test-rubric

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a repeatable evaluation rubric for AI model verification?

To build a repeatable evaluation rubric, define eight weighted categories totaling 100 points, establish a three-tier severity taxonomy for violations, and implement a canonical scorecard template to ensure consistent model-verification across runs.

What is a three-tier severity taxonomy in a quality assurance scorecard?

A three-tier severity taxonomy in a quality assurance scorecard classifies model violations as critical, major, or minor. It includes explicit sub-score rules and applies a hard cap on outcomes when critical violations occur during evaluation.

How do I manage rubric versioning when updating category weights?

Manage rubric versioning by bumping the minor version and adding a changelog entry whenever you update category weights. This revision workflow supports adding or removing categories and fingerprinting for new models.

How do I structure a violation log schema for model evaluation?

Structure a violation log schema by specifying standardized violation fields, incorporating run-tagging conventions, and linking entries to the fixed scorecard template. This ensures consistent tracking across all rubric revisions and model-verification protocols.

Can I use this rubric design for scoring PROBE-like AI agent systems at scale?

Yes, this rubric design scales for PROBE-like AI agent systems by providing a comprehensive scoring blueprint with eight weighted categories, a fixed scorecard template, and a three-layer model-verification protocol to ensure comparability across multiple runs.

What is the best way to enforce a hard cap on critical violations in a scoring rubric?

The best way to enforce a hard cap on critical violations is to define explicit sub-score rules within the severity taxonomy that automatically trigger an outcome cap, ensuring any critical failure heavily impacts the final 100-point scorecard.