By HarishDvs
An open editor-in-a-skill for fiction writers. Diagnosis, structure, and memory. The author keeps the pen.
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.
Generate and explore ideas for plot, characters, or worldbuilding. Use when the user wants options, what-ifs, to think through a character arc, solve a narrative problem, or talk through where the story could go.
Create, update, or bootstrap the project codex (chapter cards, arc cards, character cards). Use when a chapter is finished or edited, when continuity cards need updating, when the user asks to card a chapter, or to onboard an existing manuscript into the codex.
Expand the author's rough material into prose. Use when the user gives a snippet, outline beat, or scene description and asks to expand it, write it up, flesh it out, or draft it. The highest-risk mode; runs on strict rails.
Improve or fix existing prose. Use when the user shares a passage or chapter and asks to improve it, fix it, polish it, tighten it, or asks what's wrong with it. Diagnosis-first, surgical line fixes, never a wholesale rewrite.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
An open editor-in-a-skill for fiction writers — novelists, webnovel serial authors, anyone with a manuscript. Editors are expensive. AI is cheap but writes slop. Grizzly's bet: the value of AI for fiction is not generation, it is diagnosis, structure, and memory. The author keeps the pen.
Every AI writing product fails writers the same way: it produces prose, the prose has a voice, and the voice is the model's, not the author's. Grizzly inverts the design:
A surgical edit proposal (you accept, reject, or tweak each line):
Line 41 — emotion label.
- Mara felt the fear rise as the bell kept ringing. + The bell kept ringing. Mara counted the strokes.
A review finding:
[major] Ch 7, the cellar scene — buried landing. The chapter exists to deliver the brother's betrayal, and it arrives in the flattest sentence of the scene, mid-paragraph. The beat needs to land through a concrete moment, not a summary. Routing: structure (grizzly-plan) or line work (grizzly-edit).
A cold-read audit verdict:
I'd keep reading. The cellar scene pulls, but I skimmed the market chapter (no question raised for forty lines), and I cannot physically picture the innkeeper — she is a voice in white space. Highest-leverage change: give the market chapter one live thread.
flowchart LR
M[Your manuscript] -->|grizzly-cards| C[Codex<br/>chapters, arcs,<br/>characters, threads]
S[Your writing samples] -->|grizzly-init| V[VOICE.md<br/>your style spec]
C --> X{Modes}
V --> X
X -->|edit, review, audit| F[Findings + side-by-side fixes]
X -->|draft, plan, brainstorm| P[Small proposals, beat by beat]
F --> A((You decide))
P --> A
A -->|accepted changes| M
Three separated quality layers run under everything, because they fail differently:
The blacklist above is judgment. The enforcement layer is the part of it a machine can check without judgment, run as a deterministic gate.
tools/tell-scan.ps1 is a regex scanner for the mechanically-detectable subset
of the blacklist: the em dash, the "too X to" construction, negative parallelism
("not X but Y", "nothing but", "without so much as"), and emotion or cognition
report-frames ("she felt", "he realized", "Mara noticed"). Run it on a chapter:
powershell.exe -ExecutionPolicy Bypass -File tools/tell-scan.ps1 "chapters/ch07.md"
It accepts a single file or a *.md glob and prints one line per hit:
LEVEL file:line [rule] | matched snippet
Two tiers:
The author's STANDARDS.md may relax or extend individual entries; the scanner
encodes only the defaults.
The scanner is the deterministic floor of the hygiene layer. It is paired with
two things regex cannot do: a separate-reader pass (re-read the draft cold,
against the full blacklist) and the delivery pass (decks/delivery-pass.md), for
everything mechanical detection cannot judge.
npx claudepluginhub harishdvs/grizzly --plugin grizzlyHarness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Binary reverse engineering, malware analysis, firmware security, and software protection research for authorized security research, CTF competitions, and defensive security
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Next.js development expertise with skills for App Router, Server Components, Route Handlers, Server Actions, and authentication patterns
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications