ProductRubric
Make your own

Build a rubric without touching GitHub.

A rubric is one Markdown file with a set of criteria, a scoring scale, an output format, and honesty rules. This page asks you plain questions and writes that file for you as you go. Nothing you type leaves your browser until you choose to download or submit something.

When it is ready, the file is yours either way. Download it and use it with your own AI, or submit it to the library and share it with everyone.

Use it yourself

Download the rubric file, or the installable Skill package, and run it in your own AI. Nothing is published, no account is needed, and the file is yours to keep and change.

Contribute it to the library

Submit it for review. If it is accepted, your rubric joins the open library on this site and in the MCP, credited to you as its author, and anyone can use it, remix it, and build on it.

The basics

These answers become the file's frontmatter, the part machines and other AIs read first.

Purpose
Criteria

One card per criterion. Write what good and bad look like concretely enough that two runs would judge the same work the same way. Most rubrics carry three to seven criteria.

Scoring
Output format

The exact structure the AI must return. The Rubric summary block that every report ends with is specified for you at the end, generated from your rubric's name and scale, because its shape is fixed across the library.

Honesty rules

The claims the AI must not make while running this rubric. Tick the standard ones that apply, then add your own.

Worked example (for submitting)

A library contribution includes one worked example: your rubric, run once, with its output kept as the rubric produced it. Run your rubric in your own AI against a screen or document of yours, or one of the sample fixtures in the repository, and paste the output here. You can download it as the example file, and include it when you submit. For your own use of the rubric, this part is optional.

Take it with you

The first of the two ways this can end. Everything below is generated from the answers above, in your browser.

The prompt carries the whole rubric with it, so it works in any AI chat with nothing installed.

Submit it to the library

The second way: share it. Your rubric goes into the review queue as a pull request on GitHub, credited to you.

What happens after you submit

  1. The button opens GitHub with your rubric already filled in. GitHub asks you to sign in (or create an account), and then offers to fork the library and propose your change. Back here, the same button then sends your worked example the same way, so the submission carries both files. There is nothing to edit on GitHub either time; the files arrive exactly as this page wrote them.
  2. GitHub shows you your pull request. That page is your submission's home: bookmark it, or copy its link from the button here after you create it.
  3. GitHub emails you whenever anything happens on it, as long as email notifications are on in your GitHub settings, which they are by default: a comment from the maintainer, a request for changes, or the decision.
  4. The states, in plain words: open means it is in the review queue. A request for changes means the maintainer has left notes and it is your turn. Merged means your rubric is in the library, and it appears on this site and in the MCP on the next update. Closed without merging means it was not accepted, and the reason is in the comments on that page.
  5. You can find every submission you have made at any time under your pull requests on GitHub, no bookmark needed.

Checklist

Tap any item to jump to that part of the form.

    The required section is the same set of rules the library's own validator runs on every pull request, so a file that passes here passes there.

    Your file

    Your file builds here as you answer.

    Your rubric file