writer

writer is a skill for Claude Code from rileyhilliard/claude-essentials. It costs 45 tokens per session (1,619 once invoked), scanned A, original, MIT.

A writing-style guide for producing natural, human-sounding text for technical documents, articles, posts, and other user-facing content.

In plain words
What is it for?
Use it when drafting READMEs, documentation, commit messages, design documents, blog posts, social posts, or product writing.
Why use it?
It helps writing avoid a corporate or artificial tone while matching the supplied voice, audience, and type of document.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ce plugin — 17 skills, 1 command, 4 agents shipped together

Good fit Use it when drafting READMEs, documentation, commit messages, design documents, blog posts…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rileyhilliard/claude-essentials/writer
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 rileyhilliard/claude-essentials --skill writer
Clone the repo
git clone --depth 1 https://github.com/rileyhilliard/claude-essentials

Made for: Claude Code.

Or install ce, the plugin that ships this one along with the rest of its 17 skills, 1 command, 4 agents.

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 writer

README.md
[![agentmods](https://agentmods.dev/badge/skills/rileyhilliard/claude-essentials/writer.svg)](https://agentmods.dev/skills/rileyhilliard/claude-essentials/writer)
Your own site
<a href="https://agentmods.dev/skills/rileyhilliard/claude-essentials/writer"><img src="https://agentmods.dev/badge/skills/rileyhilliard/claude-essentials/writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,619 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.00045 $0.01619
Opus 5 $0.00023 $0.00809
Sonnet 5 $0.00009 $0.00324
Haiku 4.5 $0.00005 $0.00162

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

Security

Grade A, and why

writer 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 7d 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.

plugins/ce/skills/writer/SKILL.md · 177 lines

How it starts

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

Writing Style Guide

Writing that sounds like a real person wrote it, not a corporate committee or an AI.

Voice Anchoring (Read First)

If the user provides any of the following, treat it as the primary voice reference and match it above all other guidance in this skill:

  • A rough draft or partial draft
  • Sample sentences or a writing sample
  • A previous piece they've written
  • Any text labeled "write in this style" or similar

Lock onto the cadence, sentence weight, word choices, and register of what they gave you. Don't clean it up. Don't normalize it toward polished prose. If their draft is conversational and slightly messy, the output should be too. The persona and principles below are defaults for when no sample exists -- a real sample from the user always overrides them.


Persona Selection

Writing... Load File
Technical docs, API refs, READMEs, code explanations The Engineer references/engineer.md
ADRs, design docs, architecture docs, tradeoff analyses The Architect references/architect.md
Strategy docs, analysis, product specs, roadmaps The PM references/pm.md
Landing pages, pitch decks, vision docs, blog posts The Marketer references/marketer.md
Tutorials, onboarding, walkthroughs, getting started The Educator references/educator.md
Commit messages, PRs, changelogs, release notes The Contributor references/contributor.md
Cold outreach, intros, customer discovery, validation emails The Outreach Writer references/outreach.md
Error messages, UI copy, notifications, empty states The UX Writer references/ux-writer.md
Reddit replies, forum comments, casual DMs, social replies The Poster references/poster.md
LinkedIn posts, professional updates, industry commentary The LinkedIn Writer references/linkedin.md

Read the full file on GitHub · 177 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. 7d ago First seen · 177 lines · 45 tokens per session scan A d1706e941c19

Subscribe to this mod's changes

writer is a skill published in the GitHub repository rileyhilliard/claude-essentials (128 stars, last pushed 19d ago), licensed MIT. It adds 45 tokens to every session and 1,619 once invoked, about $0.0002 per session on Opus 5. 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens