stark-story-judge

Grades long-form blog posts with cold cross-vendor LLM judges on an anchored rubric.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/21StarkCom/stark-skills --skill stark-story-judge-21starkcom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stark-story-judge
Source: https://github.com/21StarkCom/stark-skills/tree/main/runtime-overrides/codex/skill/stark-story-judge
Command: npx skills add https://github.com/21StarkCom/stark-skills --skill stark-story-judge-21starkcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Authors cannot objectively grade their own writing because session context contaminates judgment. This Skill dispatches zero-context cold judges that grade a post's reading experience with quoted evidence, so publish decisions rest on how a stranger actually reads the text. ## Core Features & Use Cases - Zero-context judging: Builds a clean payload (title, summary, body) with no author identity, edit history, or repo context, then dispatches one cold subagent per vendor that scores seven dimensions (hook, one idea, pull, voice, fluency, honesty, landing) on a 0-3 anchored rubric with mandatory quoted evidence. - Cross-vendor second opinion: Runs a second judge from a different vendor (Codex host uses Claude, Claude host uses Codex) with a byte-identical prompt, then relays both scorecards verbatim with convergence analysis and written dispositions. - Audience persona lenses: Optionally simulates a specific reader type (e.g., an Israeli LinkedIn engineering lead) returning read/share verdicts and funnel-stage reactions without scores, kept strictly separate from the craft grade. - Use Case: Before publishing a blog post, run the judge to get a letter grade (A-F out of 21 points), a PUBLISH/REWRITE verdict, the top three fixes ranked by expected lift, and a second-vendor scorecard to confirm the call. ## Quick Start Ask the assistant to run stark-story-judge on your draft post file to get a cold-reader grade and verdict before publishing.

Frequently Asked Questions about stark-story-judge

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

FAQPage Schema
How do I get an objective grade on my blog post before publishing?▼

Run the judge on your post file or pasted draft. It dispatches a cold subagent with no context about you or the edit history, which scores seven dimensions 0-3 with quoted evidence and returns a letter grade plus a PUBLISH, PUBLISH AFTER FIXES, REWRITE, or NO STORY YET verdict.

What does the story judge rubric score?▼

The rubric scores seven dimensions: hook, one idea, pull, voice, fluency, honesty, and landing, each 0-3 for a total out of 21. Grades map to A (19-21) through F (0-7), and a zero on the one-idea dimension caps the grade at D.

Can I re-run the same judge to confirm a grade?▼

No. Re-rolling the same vendor's judge on unchanged text is treated as noise. A second opinion is only valid as a different vendor's model reading the identical payload, and a re-grade of the same judge is legal only after the text changed.

Does the story judge also fix or rewrite my post?▼

No. It only grades and names problems, ranking the top three fixes by expected lift without writing replacement prose. Rewriting belongs to stark-story-edit and cutting belongs to stark-blog-sharpen.

What is the difference between a judge and an audience lens?▼

Judges answer whether the post is good, producing dimension scores and a letter grade. A lens simulates a specific reader persona and answers whether that reader would read, finish, and share it, returning no scores and never moving the craft grade.

Why did my judging run get flagged as invalid?▼

Runs are invalid if a score lacks a quoted evidence span, every dimension scored 2 or higher on a first draft, the scorecard mentions your repo or tooling, the same judge ran twice on one revision, or totals were averaged. Invalid runs are re-dispatched with the leak fixed.