Best AI Agent Skills for Writers in 2026

Most writers I know stopped at ChatGPT-as-blank-textarea and never moved past it. Claude Code skills are the next step. They let an AI open your docs, edit in place, run a style check, and write to disk. The difference between asking a chatbot for a draft and watching one rewrite your manuscript file is bigger than it sounds.

This list covers 8 skills writers use in 2026, with install commands and what each one is good for. Skip the security audit section if you trust the skills marketplace; skim it if you don't.

For a wider view, see [our full list for writers](/best-ai-tools-for/writers).

What is a Claude Code skill?

If you're new: skills are small bundles of instructions, scripts, and reference files that Claude loads when relevant. Unlike MCP servers (which are tool servers running in a separate process), skills live in your filesystem at ~/.claude/skills/skill-name/SKILL.md plus any helpers, and Claude reads them on demand.

You install a skill by copying its files. You can audit a skill by reading its SKILL.md before running anything. We have a deeper guide at [how to audit a Claude skill before installing](/blog/how-to-audit-a-claude-skill-before-installing-2026).

The 8 skills

1. [Doc Co-authoring](/skills/doc-coauthoring)

Doc Co-authoring is the skill writers should install first. It teaches Claude how to handle long documents — chapter restructuring, voice consistency across sections, finding contradictions, suggesting cuts.

What it's good at:

• Restructuring a 5,000-word draft without losing your voice
• Catching where you've drifted into a different tone halfway through
• Suggesting where to cut without making you defensive about it

Install: ``bash cd ~/.claude/skills && git clone https://github.com/anthropics/skills anthropic-skills-temp && \ mv anthropic-skills-temp/document-skills/doc-coauthoring ./ && rm -rf anthropic-skills-temp `

GitHub: github.com/anthropics/skills (official Anthropic repo, low security risk).

2. [DOCX (Word Documents)](/skills/docx-word)

If you write in Word — which most professional writers still do, despite the rest of the industry pretending otherwise — this skill teaches Claude to open .docx files, edit tracked changes, and preserve formatting.

What it's good at:

• Editing client documents without breaking their styling
• Adding tracked changes Claude can review later
• Generating clean Word output from markdown drafts

Install: same Anthropic repo as above; the path is document-skills/docx.

3. [Brand Guidelines](/skills/brand-guidelines)

This one matters if you write for clients with strict tone-of-voice rules. Brand Guidelines teaches Claude to read a style guide PDF and apply it across drafts — checking word choice, sentence patterns, banned terminology.

I tested it on a fintech client's 40-page guidelines doc. Claude caught 23 voice violations in a draft that I'd reviewed twice and missed.

Install: github.com/anthropics/skills, path web-skills/brand-guidelines.

4. [Marketing Skills](/skills/marketing-skills)

A bundle of writing skills aimed at marketing copy — landing pages, email sequences, ad headlines, social posts. Strong for writers doing client work or running their own newsletter.

The headline-testing helper alone has been worth it for me. Generates 30 variants, then ranks them by tested patterns (specificity, length, opening word strength). Saved me at least 4 hours/week on subject lines.

Install: search the marketplace for marketing-skills (multiple repos publish under this name — verify the source before installing).

5. [Claude SEO](/skills/claude-seo)

For writers publishing online, Claude SEO automates the meta-tag, schema, and internal-linking work that used to need a separate tool. Loads keyword research from your file, audits a draft for keyword placement and readability, suggests internal links from your existing content.

What it's good at:

• One-pass SEO audit on a finished draft
• Auto-generating meta description (≤155 chars, primary keyword, CTA)
• Schema markup (Article, FAQPage, BreadcrumbList)

What it's not: a replacement for actual keyword research. Pair it with a research tool like Ahrefs or just plain Google.

Install: github.com/anthropics/skills, path seo.

6. [Writing Plans](/skills/sp-writing-plans)

Part of the Superpowers skills pack. Teaches Claude to write structured plans for long writing projects — book chapters, multi-part series, white papers. Useful when you're staring at a blank document and need an outline before you can start drafting.

Install: `bash cd ~/.claude/skills && git clone https://github.com/superpowers-ai/skills superpowers-temp && \ mv superpowers-temp/sp-writing-plans ./ && rm -rf superpowers-temp `

Verify the GitHub repo before running this — there are multiple "superpowers" forks and not all are reputable.

7. [PDF Tools](/skills/pdf-tools)

Writers don't always think they need PDF tools, but anyone working with research papers, contracts, or scanned manuscripts needs one. PDF Tools handles extraction, OCR, splitting, merging, and form filling.

The OCR feature is the killer one. Drop in a scanned letter from 1973 and Claude reads it as text, ready to edit.

Install: github.com/anthropics/skills, path document-skills/pdf.

8. [Frontend Design](/skills/frontend-design)

Surprising entry but worth it: writers who publish their own work need to handle layout sometimes. Frontend Design teaches Claude to build clean web pages without the AI-generated aesthetic. Useful for landing pages, online essays with custom layout, or one-off newsletter designs.

If you've ever asked Claude for "a landing page" and gotten a generic gradient with three benefit cards, Frontend Design is the fix. It explicitly works against that default.

Install: marketplace, package frontend-design`.

Workflow: writing a 3,000-word essay

Here's how I run these together on a typical piece:

1. Plan — Writing Plans drafts the outline based on a one-paragraph brief 2. Research — pasted excerpts from sources go into a notes file 3. Draft — Claude works through the outline section by section, I edit each as it lands 4. Voice pass — Doc Co-authoring checks for tone drift across sections 5. Brand pass — Brand Guidelines catches anything off-style for the client 6. SEO pass — Claude SEO adds meta tags, schema, internal links 7. Format — DOCX skill outputs the final Word file with the client's template

Total time on a 3,000-word piece dropped from ~6 hours to ~3.5. The first 90 minutes used to be staring at a blank page; now they're spent on the outline and revision passes that matter.

Security — what to check before installing

Skills run with the same permissions Claude has. A malicious skill can read your filesystem, run shell commands, or post your data somewhere. Before installing any skill from outside the official Anthropic repo:

1. Open SKILL.md and read it. Look for unexplained network calls or shell commands that touch sensitive paths. 2. Check the repo's commit history. A skill with one commit from yesterday is riskier than one with 50 commits over 6 months. 3. Look at who else uses it. Search the skill name on GitHub and see how many repos reference it. 4. Run it in a test directory first. Don't install a new skill into your real project until you've watched what it does on a sandbox.

We have a longer guide at [how to audit a Claude skill before installing](/blog/how-to-audit-a-claude-skill-before-installing-2026).

Skills vs MCP servers — which for writers?

For writing work, skills win. They're lighter, easier to audit, and don't need a separate process running. MCP servers shine for live integrations (Notion, Google Docs, Slack) where you need a connection to a third-party API.

A practical rule: if your tool is "read/write a file on my computer," use a skill. If it's "talk to a service over the network," use an MCP server. See [MCP servers vs Agent skills explained](/blog/mcp-servers-vs-agent-skills-difference-2026) for the deeper version.

What I don't use

• AI grammar skills. Grammarly's free browser extension handles this better, and it's purpose-built.
• AI plagiarism detectors. They have high false-positive rates on AI-edited human work, which is a problem when you're the human.
• AI fiction-specific skills. The current generation is better than nothing for plotting, but the prose output is too uniform for serious fiction work. Use them for outlines, not text.

FAQ

Do these skills work with the Claude.ai web app? No. Claude Code skills are for the Claude Code CLI tool (and the Claude Agent SDK). The web app has a separate, simpler skill system.

How do I write my own skill? Use the Skill Creator skill, which walks Claude through building a new skill including evals. We have a [Skill Creator how-to](/blog/how-to-install-skill-creator-claude-code-2026) guide.

Will skills replace human editors? For mechanical edits (typos, voice consistency, basic structure) — already, yes. For substantive editing (does this argument hold? is this section necessary?) — no. The good editors I work with are using these skills themselves to handle the mechanical layer faster.

Is there a skill for fiction writing? There are a few unofficial ones, but I haven't seen one I'd recommend yet. Claude itself handles fiction prose well; you don't need a specialized skill for it as much as you need a strong outline and patience.

How many skills should I have installed? Most active writers I talk to run 5-10 skills. More than that and Claude's context budget starts paying for skill descriptions you never use. Audit your skills folder every couple of months and remove what you haven't touched.

Bottom line

Doc Co-authoring is the one to install first. DOCX if you work in Word, Brand Guidelines if you write for clients, Claude SEO if you publish online. The rest are situational.

Skills aren't writing for you — they're handling the parts of writing that aren't writing. That distinction is the thing that turns AI into a useful collaborator instead of a draft generator.