strong-writing-checklist

strong-writing-checklist is a skill for Claude Code from design1online/author-it. It costs 0 tokens per session (2,061 once invoked), scanned A, original, MIT.

A writing review checklist for evaluating drafts and strengthening prose, including character voice, sensory detail, repetition, and word choice.

In plain words
What is it for?
Use it to review fiction scenes or revise existing writing for clearer description, believable characters, and more varied language.
Why use it?
It helps find common weaknesses that can make writing feel unclear, flat, or inconsistent.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the author-it plugin — 24 skills shipped together

Good fit Use it to review fiction scenes or revise existing writing for clearer description, believable characters, and more varied language.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/design1online/author-it/strong-writing-checklist
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add design1online/author-it --skill strong-writing-checklist
Clone the repo
git clone --depth 1 https://github.com/design1online/author-it

Made for: Claude Code.

Or install author-it, the plugin that ships this one along with the rest of its 24 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for strong-writing-checklist

README.md
[![agentmods](https://agentmods.dev/badge/skills/design1online/author-it/strong-writing-checklist/github.svg)](https://agentmods.dev/skills/design1online/author-it/strong-writing-checklist)
Your own site
<a href="https://agentmods.dev/skills/design1online/author-it/strong-writing-checklist"><img src="https://agentmods.dev/badge/skills/design1online/author-it/strong-writing-checklist/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for strong-writing-checklist

Your own site · 80×15
<a href="https://agentmods.dev/skills/design1online/author-it/strong-writing-checklist"><img src="https://agentmods.dev/badge/skills/design1online/author-it/strong-writing-checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,061 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02061
Opus 5 $0.00000 $0.01030
Sonnet 5 $0.00000 $0.00412
Haiku 4.5 $0.00000 $0.00206

Measured 11d ago against content hash 86d08ef77e0c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

strong-writing-checklist scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/strong-writing-checklist/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Strong Writing Checklist

This is a comprehensive checklist that can be used to evaluate good writing or strengthen existing writing.

  1. Show, don't tell
  2. Maintains the character voice by taking into account their personality, background, wound/flaw, age, occupation and experiences. An old woman shouldn't suddenly sound like a valley girl. A private detective shouldn't act like a school teacher. A layperson wouldn't have knowledge or skills in advanced mathematical research without a concrete explanation. Someone who is poor doesn't own a million dollar car without a logical reason (ie inherited it from a rich relative, stole it, etc)
  3. Every scene should incorporate as many senses as possible to help the reader feel immersed in the environment: balance, sight, smell, taste, touch, temperature
  4. No repetitive phrases or words (ie don't start every sentence with I in a first person POV or use the word blue three times within the same four paragraphs)
  5. Use strong adjectives over adverbs
  6. Don't use second person pronouns unless they are in character dialogue or the entire scene is written in second person perspective
  7. Show the actions a character is taking or the emotions a character is feeling rather than telling the action or emotion directly (ie he smiled rather than he's happy)
  8. Pacing is important to good writing. Actions scenes, fight scenes or intense scenes should have shorter and punchier sentences. Sentences, paragraphs and chapters should vary in length. Lots of long sentences in a row is harder for people to read. If you do an analysis of sentence length it should have a variation in the length rather than lots of sentences in similar lengths. This helps set a rhythm to the story
  9. Chapters should be at least 1,500 words long. Chapters should typically be no longer than 3,500 words long. Chapters must never be more than 5,000 words
  10. Every scene needs a hook, escalation, pivot, conflict and consequences with the consequences leading to the hook of the next chapter
  11. Reduce the use of dialogue tags, the voice of the character or flow of the story should make it easy for the reader to tell who is talking. Only use dialogue tags when it's not clear who is talking in a long section of back and forth dialogue.
  12. Avoid adverbs in dialogue, use stronger verbs or adjectives
  13. Don't use passive indications or passive sentences.
  14. Tenses must be consistent throughout the story, scenes and chapters unless the passage is a flashback/something that happened in the past
  15. Don't use cliches
  16. Remove redundancies in words or sentences that say almost the exact same thing more than once
  17. Consistent point of view, for the chapter or scene, no head hopping
  18. No unnecessary filler words, reduce glue words by writing a sentence with stronger verbs or adjectives
  19. Writing word choice should meet the target audience, for example don't use words at an 8th grade reading level for a book written for kindergarteners. Do a lexical analysis to make sure the text is at the appropriate reading level.
  20. Slang/colloquialisms should exist in the character dialogue or story elements so that the world feels authentic. For example, characters might call food "chum" if they live in a world where eating is done out of necessity because it doesn't taste good
  21. World building should make sense for the location or elements presented in the story
  22. World building established should persist throughout the story, something introduced in chapter 1 shouldn't suddenly disappear by chapter 10
  23. Limit sentences that start with an initial pronoun or character names
  24. Avoid sentence starters
  25. Avoid generic descriptions
  26. Avoid misspelled words
  27. Avoid incorrect punctuation
  28. Avoid grammatical errors
  29. Don't start the story with a character waking up or in a dream
  30. Don't start the story with weather unless it's unusual weather
  31. The protagonist must be active with their actions/decisions driving the story forward not just reacting to the plot or environment changes happening around them
  32. POV must be consistent throughout the entire scene unless there's a scene break
  33. No head hopping where the narrator shifts between character perspectives within a single scene, paragraph, or even sentence.
  34. Avoid using anything other than he/she said or asked after character dialoge for best dialoge readability.
  35. Avoid plot holes or story beat inconsistencies
  36. Strong hook on the first sentence: catches readers attention and keeps them reading, has strong character voice, leaves reader asking questions, has tension or conflict or stakes
  37. No info dumping
  38. The last sentence of a chapter should setup a strong hook for the next chapter

Read the full file on GitHub · 106 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 106 lines · 0 tokens per session scan A 86d08ef77e0c

Subscribe to this mod's changes

strong-writing-checklist is a skill published in the GitHub repository design1online/author-it (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,061 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

exploratory-data-analysis

Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…

K-Dense-AI/scientific-agent-skills · 83 tokens

google-ads-audit

Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run…

nowork-studio/notfair-plugin · 86 tokens

data-charts-tako

Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.

gooseworks-ai/goose-skills · 35 tokens

webhook-management

Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.

hoangsonww/Claude-Code-Agent-Monitor · 56 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

master-yinguang

A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.

xr843/Master-skill · 274 tokens