explaingit

supe-log/writing-engine

Analysis updated 2026-05-18

2TypeScriptAudience · developerComplexity · 4/5Setup · moderate

TLDR

Writing Engine grades student essays like a trained human rater, scoring them against official rubrics such as STAAR, explaining every score with evidence, and improving its own accuracy across repeated runs.

Mindmap

mindmap
  root((Writing Engine))
    What it does
      Grades essays like a rater
      Explains every score
      Self improves each run
    Tech stack
      TypeScript
      Node.js
      npm
    Use cases
      STAAR essay grading
      Rubric based feedback
      Custom scoring engines
    Audience
      Developers
      Education builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Automatically grade student essays against an official rubric like STAAR with human-level accuracy.

USE CASE 2

Get evidence-based feedback explaining exactly why an essay received its score.

USE CASE 3

Build a new scoring engine for a different rubric and set of example essays using the engine-builder skill.

USE CASE 4

Run a background agent that grades incoming essays from a live feed while it earns permission to publish results.

What is it built with?

TypeScriptNode.jsnpm

How does it compare?

supe-log/writing-engineadun-denton/chinvatagbara286/saint-cms
Stars222
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderatemoderateeasy
Complexity4/54/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Demo and benchmark run offline with no API keys, but live model modes need a hosted or self-hosted Nemotron/vLLM endpoint.

In plain English

Writing Engine is a tool that grades student essays the way a trained human rater would, rather than writing essays for students. You feed it a piece of writing scored against an official rubric, such as the STAAR state writing test used in schools, and it produces a score along with an explanation for that score backed by evidence from the text itself. It never generates essays on a student's behalf, only assessments and feedback. The project has three connected parts. The first is the scoring engine itself, which is checked against real, already scored essays from an actual state exam to measure how closely its grades match a human grader, including how confident that match is. The second is a builder process that can create new scoring engines for other rubrics and example essays, packaged as a reusable skill. The third is a background agent that runs the scoring engine on live incoming material, such as a stream of new essays or public weather alerts used as a stand in data feed, but that agent is deliberately blocked from writing or publishing anything until it has proven, with evidence, that it deserves that permission. A key idea running through the whole project is that each time it runs, it compares its own output against the fixed rubric, keeps only the changes that measurably improve its score, and applies those lessons the next time it runs, so its accuracy is meant to improve over repeated cycles rather than stay fixed. Every prompt and piece of content going in or out is also scanned for security issues and personal information before being processed. The project is written in TypeScript and requires Node.js 20 or newer with npm. A full demo and benchmark can be run entirely offline on prepared sample data with no API keys needed, and there are separate commands for running the demo, running the benchmark, running the test suite, and running a single live cycle. It can also be configured to run against different underlying AI models, including a self hosted option, by changing environment variables rather than code. The project was built for a hackathon.

Copy-paste prompts

Prompt 1
Run npm run demo to see the Writing Engine heartbeat loop grade essays end to end offline.
Prompt 2
Explain how the engine measures its agreement with human raters on the STAAR benchmark in npm run benchmark.
Prompt 3
Walk me through how the engine-builder loop in .claude/skills/assessment-loop builds a new scoring engine from a rubric.
Prompt 4
Show me how to switch this engine from the hosted judge models to a self-hosted Nemotron endpoint via environment variables.

Frequently asked questions

What is writing-engine?

Writing Engine grades student essays like a trained human rater, scoring them against official rubrics such as STAAR, explaining every score with evidence, and improving its own accuracy across repeated runs.

What language is writing-engine written in?

Mainly TypeScript. The stack also includes TypeScript, Node.js, npm.

How hard is writing-engine to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is writing-engine for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.