← 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 72
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 Choose the reading contract before loading the codex or author goals: - **Isolated cold read:** read only the requested text when the author wants the excerpt or chapter judged on its own. - **Series-aware fresh read:** default for a late-in-sequence chapter. Carry manuscript context already read; if none is loaded, read the immediate predecessor and the last relevant POV or thread passage before the target. React first, then analyze. Load the codex afterward for comparison. 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. Charac