stark-fresh-eyes

Dispatches one zero-context reviewer to verify document claims by a different method.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Authors cannot reliably review their own documents because they re-read their intent rather than the actual text, and multi-round review loops fail to converge. This skill replaces self-rereading with a single isolated, read-only reviewer that has zero shared context and verifies every checkable claim using a different method than the document's own. ## Core Features & Use Cases - Zero-context verification: The reviewer receives only the document path and a verification contract, never the author's reasoning or history, preventing confirmation bias. - Different-method checking: Counts are recounted recursively, numbers recomputed from raw sources, referenced paths tested for existence, and cited commands checked via --help. - One-pass discipline: Exactly one dispatch per document revision; findings return to the author once with a per-finding disposition (fix, reject, or accept-as-known), and zero findings is a valid result. - Use Case: Before shipping a spec or research brief, run the skill on the draft so an isolated reviewer from a different vendor catches wrong file counts, broken references, and internal contradictions before readers do. ## Quick Start Ask the assistant to run a fresh-eyes review on your document, for example: review docs/spec-draft.md with stark-fresh-eyes and focus on the migration steps.

Frequently Asked Questions about stark-fresh-eyes

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

FAQPage Schema
How do I review a spec or brief before shipping it?▼

Invoke the skill with the document path, optionally adding --focus for an aspect to emphasize. It dispatches one isolated reviewer that verifies every checkable claim by a different method and returns a numbered list of defects only.

What is a zero-context document review?▼

A zero-context review gives the reviewer only the file path and a verification contract, never the author's reasoning or history. This prevents the reviewer from confirming intent instead of verifying the actual text.

Can I choose which LLM reviews my document?▼

Yes, pass --reviewer with claude, codex, or gemini, or use auto. Auto prefers an enabled reviewer from a different vendor than the current host, resolved through the installed runtime configuration.

Why does the skill refuse to run a second review round?▼

Multi-round LLM review loops are structurally non-convergent, so the skill enforces one dispatch per document revision. If the document is substantially revised later, the new revision may receive its own single pass.

What happens if no isolated reviewer is available?▼

The skill stops and explains that a fresh-eyes verdict would be contaminated rather than falling back to self-review. A valid reviewer must start with no conversation history and have read-only access.

What counts as a defect in the review report?▼

Defects include factually wrong claims, internal contradictions, ambiguous instructions, unresolvable references, unverifiable claims, and missing definitions. Style issues, scope opinions, and alternative approaches are explicitly not defects.