Skip to content

/ia-writing

Prose editing, rewriting, and humanizing text for natural tone, or auditing a draft for AI tells without rewriting. Use when asked to write, rewrite, edit, humanize, proofread, fix tone, remove AI language, or check whether writing reads as AI. For copy, docs, blog posts,

From plugin
2831 skills12 commands
shell
$ npx -y skills add iliaal/whetstone --skill ia-writing --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/ia-writing
How auto-invocation works

Context preview

The summary Claude sees to decide when to auto-load this skill.

Prose editing, rewriting, and humanizing text for natural tone, or auditing a draft for AI tells without rewriting. Use when asked to write, rewrite, edit, humanize, proofread, fix tone, remove AI language, or check whether writing reads as AI. For copy, docs, blog posts,

SKILL.md

ia-writing.SKILL.md
name: ia-writing
class: discipline
description: >-
  Prose editing, rewriting, and humanizing text for natural tone, or auditing a
  draft for AI tells without rewriting. Use when asked to write, rewrite, edit,
  humanize, proofread, fix tone, remove AI language, or check whether writing
  reads as AI. For copy, docs, blog posts, emails, or PRs.

Human Writing

Modes

**Edit (default)** -- rewrite the draft to strip AI tells while preserving the writer's voice; produce corrected text plus a changelog.

**Detect** -- when asked whether text reads as AI, or to audit, scan, or flag a draft without rewriting: name each pattern that appears, quote the offending line, and give the fix in a few words. Do not rewrite, do not score, do not claim whether AI wrote it -- named patterns are evidence the reader can check; an authorship verdict is a guess. Run detection per Phase 1 of [audit-workflow.md](./references/audit-workflow.md), stop there, and offer to edit afterward.

**Not this skill** -- text whose reader is a model rather than a person: tool descriptions, system prompts, skill and agent instructions, error strings, inter-agent messages. The human-voice rules below (contractions, varied rhythm, fragments, opinions, let-some-mess-in) make that text harder to parse, not easier. Route it to `ia-refine-prompt`.

Core Principles

  • **Active voice**: "We shipped the fix" not "The fix was shipped"
  • **Name the actor**: Every sentence needs a human subject doing something. Inanimate objects don't fix bugs, shift cultures, or tell us anything -- a person does.
  • **Specific over vague**: "Cut reporting from 4 hours to 15 minutes" not "Save time"
  • **Simple words**: "Use" not "utilize", "help" not "facilitate", "start" not "initiate"
  • **Positive form**: Say what it is, not what it isn't -- "Ignore" not "Do not pay attention to"
  • **Confident**: Cut "almost", "very", "really", "quite", "arguably", and all -ly adverbs
  • **Concrete**: Name the thing, state the number, cite the source
  • **Omit needless words**: "Because" not "due to the fact that"; "Now" not "at this point in time"; "Can" not "has the ability to"
  • **Use contractions**: "don't", "won't", "it's", "they're" -- uncontracted forms are a major AI tell
  • **Put the reader in the room**: "You" beats "People." Specifics beat abstractions. Avoid narrating from a distance.

AI Patterns -- Kill on Sight

Weight detection toward structure: models reproduce sentence *structures* more reliably than vocabulary, and most AI tone lives in the shape, not the words.

**Vocabulary**: delve, crucial, pivotal, foster, leverage, tapestry, testament, underscore, vibrant, landscape (abstract), shape (abstract, as in "previous shape" / "the shape of the problem"), interplay, multifaceted, enhance, enduring, garner, showcase, Additionally, seamless, robust, cutting-edge, groundbreaking, nestled, renowned

**Structural tells**:

  • Rule of three: forced triads ("streamline, optimize, and enhance")
  • Negative parallelism: "It's not just X -- it's Y" / "Not X. But Y." → state Y directly
  • Superficial -ing phrases: "ensuring reliability", "showcasing features"
  • Copula avoidance: "serves as", "stands as", "boasts" -- use "is", "has"
  • Synonym cycling: four names for the same thing in four sentences
  • False ranges: "from X to Y" where X and Y aren't on a meaningful scale
  • Formulaic challenges: "Despite X, Y continues to thrive"
  • Dramatic fragmentation: "[Noun]. That's it. That's the [thing]." -- performative simplicity
  • Fake-profound kicker: a final "deep" line that turns the point into a metaphor, aphorism, or mic-drop. Delete it -- don't rewrite into a better line; end on the clearest concrete sentence already present.
  • Rhetorical setups: "What if I told you..." / "Think about it:" / "Here's what I mean:"
  • Colon reveals: noun phrase, colon, lowercase dramatic reveal ("The best part: it learns"). Rewrite as a plain sentence. Reserve colons for lists, labels, and quotes; sentence case after a colon unless grammar, a proper noun, a title, or code requires it.
  • Wh- sentence openers: sentences starting with What/When/Where/Which/Who/Why/How as filler. Restructure to lead with the subject or verb.
  • Narrator-from-a-distance: "This happens because...", "People tend to...", "Nobody designed this." Put the reader in the room instead.
  • Lazy extremes: every, always, never, everyone, nobody -- false authority. Use specifics instead of sweeping claims.
  • Meta-commentary: "Hint:", "Plot twist:", "Spoiler:", "In this section, we'll...", "As we'll see...", "Let me walk you through..."

**Formatting tells**:

  • No em dashes in delivered prose -- restructure the sentence (split, comma, colon, rewrite); en dash only in numeric ranges
  • Mechanical bold on every other phrase
  • Emoji-decorated headers (exception: README section headers; see README Rules below)
  • Bolded-header bullet lists (**Thing:** explanation of thing)
  • Title Case In Every Heading Word -- use sentence case instead

**Banned phrases** -- delete and rewrite on sight. See [references/phrases.md](./references/phrases.md) for the full list.

Core offenders:

  • "In today's rapidly evolving landscape"
  • "game-changer", "revolutionary", "transformative"
  • "Moreover", "Furthermore", "Additionally" (as sentence starters)
  • "It's worth noting that", "It is important to note that"
  • "At the end of the day"
  • "Here's the thing:" / "It turns out" / "Let me be clear" / "The uncomfortable truth is"
  • "Full stop." / "Let that sink in." / "Make no mistake"
  • "In order to" → "To" | "Due to the fact that" → "Because"
  • Generic conclusions: "The future looks bright" → state the actual plan

**Communication artifacts** (remove entirely): sycophantic openers and closers ("Great question!", "I hope this helps!"), knowledge-cutoff hedges ("As of my last update"), vague attributions ("Experts argue").

False Agency

AI avoids naming actors by giving inanimate things human verbs. Find the person; put them at the front of

Read more
Read it on GitHub ↗

Showing the first part of this file.

Ships withwhetstone

A Claude Code plugin that makes AI coding agents follow engineering discipline. Plan before coding. Verify before claiming done. Find root cause before patching. Review before merge. Skills activate based on file type and task signals, not manual toggling.

Get the whole plugin, auto-invoked
Stats
28
Stars
0
Views
2
Forks
Active
Maintenance
Python
Language
MIT
License
4d ago
Last commit
5mo ago
Created

Repo: iliaal/whetstone

Other skills on whetstone.