Skip to main content
Make data-driven and measurable improvements to your prompts.

What you’ll do

What you’ll need

  • Node.js or Python
  • Google API key ↗ (needed for Grade Level Appropriateness and Vocabulary Complexity)
  • OpenAI API key ↗ (needed for Vocabulary Complexity and Sentence Structure)
  • Current prompt and revised prompt, both for the same grade and task

Steps

1

Install the SDK

Install the package for the language your pipeline uses:
TypeScript
2

Score both prompt versions

Inputs must be de-identified. Do not submit students' Personally Identifiable Information (PII) or any regulated or sensitive personal information.
Score each prompt’s output with all 3 evaluators: Grade Level Appropriateness, Vocabulary Complexity, and Sentence Structure.
3

Determine whether the revised prompt should be shipped

Ship the revised prompt only if its output’s:
If the revised prompt is meant to produce a more difficult text, be sure to reverse the check and ensure that your Vocabulary Complexity and Sentence Structure scores HAVE gotten more complex.
For any dimension that fails its check, change the prompt to address that evaluator’s reasoning.To monitor one dimension of a sample over time, see Monitor quality in production.
A single passage’s scores can move for reasons that have nothing to do with the prompt.Run several evaluations for each passage-dimension pair before moving forward.

Resource Library - Improve quality by refining prompts

Score outputs from before and after a prompt change on the same rubric so you can see what shifted.

Quickstart

Run an evaluator in the Evaluators playground, a Python notebook, or with the SDK.

Tutorial: Vet content quality in production

Score each output and rewrite anything above your grade-band target.

Tutorial: Monitor quality in production

Track grade band across a sample of outputs and catch a shift over time.