stark-jury

Runs one post-editing skill across a three-model panel and reconciles the results.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A single model's edit or judgment of a draft post is one opinion with no way to measure disagreement. This Skill dispatches the same editing or judging skill to claude, codex, and gemini in parallel with byte-identical payloads, then verifies each candidate against the skill's mechanical rules so you can reconcile real model differences instead of trusting one output. ## Core Features & Use Cases - Parallel three-model panel: Dispatches one of four post skills (voice, story-edit, blog-sharpen, story-judge) plus the input document to claude, codex, and gemini simultaneously, capturing stdout, exit codes, latency, tokens, and cost per seat. - Mechanical verification: Marks each candidate CLEAN or DISQUALIFIED against the skill's rule table (em-dashes, frozen numbers, cut-only, scorecard shape, quote anchoring), with disqualification not overridable by judgement. - Anchored merge and calibration report: For rewrite skills, merges CLEAN candidates against the source document as ground truth; for story-judge, writes a calibration report with score matrix, spread, verdicts, convergence, and open disagreements. - Use Case: You have a 2,000-word draft post and want to know which model edits it best. Run the jury with blog-sharpen, get three verified candidates, and produce an anchored merge.md with a full audit trail. ## Quick Start Run the jury on my draft post at drafts/launch-post.md using the blog-sharpen skill and merge the clean candidates.

Frequently Asked Questions about stark-jury

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

FAQPage Schema
How do I compare multiple AI models on the same document edit?▼

Dispatch the same skill body and document to claude, codex, and gemini in parallel with byte-identical payloads, then verify each candidate against mechanical rules. The jury tool assembles the payload, runs all seats, and stores candidates in a run directory for reconciliation.

How do I run the stark-jury skill on a draft post?▼

Invoke it with a skill id (voice, story-edit, blog-sharpen, or story-judge) and an input file path, for example via the jury tool's run command. The document must be exported to a file first, since the jury reads files, not CMS records.

What happens when only one model produces a clean candidate?▼

Exactly one CLEAN candidate means no merge happens. That candidate is copied verbatim to merge.md, byte for byte, with failure details recorded in the audit row and session summary rather than inside the merge output.

Can I override a disqualified candidate if its edit looks good?▼

No. Disqualification against the skill's mechanical rule table is not overridable by judgement. You either fix the rule or re-run; cherry-picking sentences from a disqualified candidate invalidates the run.

How much does a three-model jury run cost?▼

Expect roughly $1 to $3 per run per skill at max or xhigh effort on a 2,000-word post, with minutes of latency per seat. Reasoning tokens bill as output, so thinking-heavy seats are the expensive ones.

When should I not use a multi-model jury for editing?▼

Skip it for quick single-model passes, Slack messages, code or spec review, and anything that publishes directly. The jury writes only to its run directory and never edits the four payload skills or publishes content.