← ClaudeAtlas

grizzly-auditlisted

Simulate a cold first-time reader and report the reading experience of a chapter. Use when the user asks why a chapter feels boring or flat, whether a chapter works, what a reader would feel, or wants a fresh-eyes read. Reports experience, not errors; for error-finding use grizzly-review.
HarishDvs/Grizzly · ★ 1 · AI & Automation · score 74
Install: claude install-skill HarishDvs/Grizzly
# Grizzly Audit — The Cold Read Reviews find errors. Audits find the problems nobody can name: the chapter that is technically clean and somehow boring, the character the reader cannot picture, the death that lands as information. This mode exists because authors cannot read their own work cold, and it is the highest-value service in the suite. ## Procedure Read the chapter start to finish AS a first-time reader: no codex first, no standards in hand, no author goals. React, then analyze. (Load the codex only afterward, for the comparison step.) Report these six checks, each with chapter-position references ("opening", "the kitchen scene", "last page"): ### 1. Dread map Where does threat exist for the reader, where does it spike, and where does it die? Threat dies through over-explanation, through repetition without escalation, and through safety that arrives too reliably. Name the line where you stopped being afraid. ### 2. Safety map Where does the reader feel safe, and is that safety doing work? Earned warmth that will cost something later is structure; comfort that costs nothing is drag. If the whole chapter is safe, say so plainly; that is usually the finding. ### 3. Character-visualization check For each character on page: can you physically see them, or are they a voice in white space? What are they doing with their bodies while they talk? Could a reader who skipped the introductions tell them apart by behavior alone? Name the characters who exist only as dialogu