ocs-chatbot-eval

Grade OCS chatbot transcripts against LLM-as-Judge rubrics.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill ocs-chatbot-eval-dimagi-internal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ocs-chatbot-eval
Source: https://github.com/dimagi-internal/ace/tree/main/skills/ocs-chatbot-eval
Command: npx skills add https://github.com/dimagi-internal/ace --skill ocs-chatbot-eval-dimagi-internal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious, inconsistent manual work of grading OCS chatbot transcripts against standardized rubrics, ensuring consistent, auditable quality checks for Connect opportunities before launch and during ongoing operation.

Core Features & Use Cases

  • Multi-Mode Grading: Supports three distinct modes: quick for 3-prompt Phase 5 shallow smoke tests, deep for pre-launch 5-dimension calibrated evaluation, and monitor for recurring Phase 9 performance trend tracking.
  • Standardized Outputs: Produces machine-readable verdict YAML, human-readable evaluation reports, and gate briefs that integrate directly with upstream ACE orchestration gates and the opp-eval aggregation workflow.
  • Calibrated Rubrics: Includes hard deduction rules, inflation guards, and auditable pre/post-cap scoring calibrated against per-opp ground truth to ensure consistent, defensible grading across runs.
  • Use Case: A Connect team running Phase 5 QA can use quick mode to run a 3-prompt smoke gate in minutes to catch critical failures before advancing to deployment, while pre-launch teams use deep mode to validate the bot against 5 calibrated dimensions before releasing to Network Managers.

Quick Start

Use the ocs-chatbot-eval skill to grade the latest OCS chatbot transcript from your active Connect opportunity run in quick mode to validate it passes the Phase 5 shallow quality gate.

Frequently Asked Questions about ocs-chatbot-eval

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

FAQPage Schema
How do I automate chatbot transcript grading for quality assurance?

Chatbot transcript grading can be automated using LLM-as-Judge rubrics to evaluate captured transcripts against standardized criteria. This process replaces manual quality checks with calibrated scoring, producing machine-readable verdicts and human-readable evaluation reports for consistent, auditable results.

What is LLM-as-Judge rubric calibration for evaluating conversational agents?

LLM-as-Judge rubric calibration applies hard deduction rules and inflation guards to standardize chatbot evaluation scoring. Pre/post-cap scoring is calibrated against ground truth to ensure defensible, consistent grading across multiple evaluation runs without human bias.

How do I run a quick smoke test on a chatbot transcript before deployment?

Run a quick grading mode using a 3-prompt shallow smoke test on captured chatbot transcripts to validate critical functionality. This catches major failures in minutes and generates a gate brief to determine if the chatbot passes the quality gate before advancing to deployment.

Can I use calibrated rubrics for recurring performance monitoring of chatbots?

Calibrated rubrics can be used in a monitor grading mode for recurring performance trend tracking of chatbot deployments. This ongoing evaluation applies the same standardized LLM-as-Judge criteria to monitor quality over time and integrate results into an aggregation workflow.

What output formats are generated by automated chatbot transcript evaluation?

Automated chatbot transcript evaluation generates machine-readable verdict YAML, human-readable evaluation reports, and gate briefs. These outputs integrate directly with upstream orchestration gates and aggregation workflows to pass quality data into downstream systems.

When should I use deep mode versus quick mode for chatbot evaluation?

Use deep mode for pre-launch validation evaluating chatbots against 5 calibrated dimensions, while quick mode handles rapid 3-prompt smoke tests to catch critical failures. Deep mode provides comprehensive assessment before releasing to users, whereas quick mode gates shallow quality checks.