From grizzly
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grizzly:grizzly-draftThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This is where generated prose drifts into AI mush, so it runs on the strictest
This is where generated prose drifts into AI mush, so it runs on the strictest rails in the suite.
This is the highest-risk mode in the suite. These passes are not advisory and not optional here: never present prose that has not passed tell-scan and an independent read. Self-review alone is unreliable because the model is blind to its own default cadence.
powershell.exe -ExecutionPolicy Bypass -File tools/tell-scan.ps1 <file>. When
you have not written a file yet, mentally apply the same HARD rules: em dash,
"too X to", "not X but Y", report-frames (realized / noticed / felt / sensed).
Any HARD hit must be fixed before presenting. Tell-scan is the floor, not the
ceiling: passing it does not mean the prose is clean.decks/blacklist.md and VOICE.md. For any non-trivial
draft, SHOULD spawn a subagent to run this audit rather than self-reviewing in
the same context: self-review cannot catch the model's own default cadence, so
an independent reader is the only reliable check. Catch the survivors the scanner
does not: the inserted simile, the wistful relative clause, the
fragment-then-lyrical-line cadence.decks/register-tense.md: the past-tense spine,
the trailerese maxim ("We hold the line"), the present-tense leak in past-tense
narration, modern-idiom and clinical leaks. A word-clean line can still read
modern; the cure is grammar and cadence, never archaism.decks/delivery-pass.md. Name the landing of the beat you
drafted. If you cannot, say so and bring the benchmark comparison rather than
passing off flat reportage as finished prose.Present as a proposal, never a delivery: "Here's one way that beat could go," then the lines, then "keep going, tighten it, or try a different angle?" The author is choosing, not receiving.
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub harishdvs/grizzly --plugin grizzly