Best Claude Skills for Writing (2026)

Claude Code’s skills system extends beyond software development Writers, technical communicators, and content teams use skills to automate document creation, maintain consistency across projects, and produce multiple output formats from a single session. Skills are .md files in ~/.claude/skills/, invoked with /skill-name.

Document Creation and Editing with the docx Skill

The docx skill creates and edits Word documents, including tracked changes, comments, and structured formatting.

/docx create a project proposal document with these sections: Executive Summary, Problem Statement, Proposed Solution, Timeline, Budget. Use H1 for the title, H2 for sections.

/docx add a tracked change to section 3 of proposal.docx: replace "Q3 delivery" with "Q4 delivery" and add a comment explaining the reason

/docx convert this markdown outline into a formatted Word document with a table of contents: [paste outline]

Writers working on collaborative documents use this skill to produce clean drafts that clients or editors can mark up in Word without losing formatting.

PDF Generation with the pdf Skill

The pdf skill creates and processes PDFs. both generating new documents and extracting content from existing ones.

/pdf create a PDF from this content with a title page, page numbers, and a header showing "Confidential": [paste content]

/pdf extract all text from client-brief.pdf and reformat it as a structured markdown outline

/pdf merge cover-letter.pdf and portfolio.pdf into a single document in that order

Content creators distributing finalized work as PDFs use this skill to produce properly formatted documents without desktop publishing software. Adjust temperature settings for more creative or more deterministic output.

Presentation Creation with the pptx Skill

The pptx skill converts written content into presentation slide decks.

/pptx create a 10-slide presentation from this article. Use the section headers as slide titles. Include a title slide and a summary slide at the end: [paste article]

/pptx add speaker notes to each slide in quarterly-review.pptx based on this additional context: [paste notes]

/pptx create a product demo deck: 1 title slide, 3 feature slides with bullet points, 1 pricing slide, 1 call-to-action slide. Brand colors: #1A73E8 and #FFFFFF.

Writers developing talks or webinars use this to adapt existing written content into visual formats without rebuilding slides from scratch.

Data-Backed Content with the xlsx Skill

The xlsx skill creates and edits spreadsheets, which is useful when articles or reports require supporting data tables, trackers, or calculations.

/xlsx create a content performance tracker in content-metrics.xlsx with columns: Article Title, Publish Date, Pageviews, Time on Page, Conversions. Add data validation to the Conversions column (numbers only).

/xlsx read editorial-calendar.xlsx and list all articles scheduled for Q2 that don't have an author assigned

/xlsx add a summary tab to metrics.xlsx that pulls totals from each monthly sheet using SUMIF formulas

Content teams tracking editorial calendars, performance metrics, or campaign budgets use this skill to maintain spreadsheets without switching to a separate tool.

Persistent Style Guides with the supermemory Skill

The supermemory skill stores and recalls style guidelines, brand voice, and project-specific rules across sessions.

/supermemory store: acme-brand-voice = conversational, direct, no jargon, second person ("you"), Oxford comma, active voice, max sentence length 25 words

/supermemory store: acme-taboo-words = use, use, collaboration, advanced, modern, best-in-class

In any future session:

/supermemory What is the Acme brand voice?

Then apply it:

Edit this draft to match the Acme brand voice: [paste recalled guidelines]
Draft: [paste draft]

Writers managing multiple clients use this to switch between brand voices without re-explaining each one from scratch.

Design Documentation with the frontend-design Skill

Technical writers documenting design systems use the frontend-design skill to verify accuracy between component specs and written documentation.

/frontend-design review this component documentation for accuracy. does the prop table match the implementation?: [paste docs, paste component code]

/frontend-design generate documentation for this Button component: list all props, their types, default values, and an example usage snippet: [paste component]

Style guide authors and developers writing component library docs use this to keep documentation synchronized with actual implementations.

A Complete Content Pipeline

These skills work together in sequence. A typical long-form content workflow:

Step 1. Recall client guidelines:

/supermemory What is the Acme brand voice?

Step 2. Draft the document:

/docx create a 1500-word guide on [topic] following this brand voice: [paste recalled voice]

Step 3. Build supporting data:

/xlsx create a comparison table from this data: [paste data]

Step 4. Generate PDF for distribution:

/pdf convert article-draft.docx to a formatted PDF with page numbers and the logo at [path] in the header

Step 5. Adapt for presentation:

/pptx create a 6-slide summary deck from the article's key points

Each skill handles one stage of the content lifecycle. The result is a consistent output across formats without rebuilding content from scratch at each step.

Content Repurposing Workflow

One of the most impactful uses for writing skills is content repurposing. taking a single source piece and producing multiple derivative formats without rewriting from scratch.

A blog post published Monday becomes a slide deck for Wednesday’s webinar, a PDF guide for the newsletter download, and a data table embedded in the follow-up email. Skills make each conversion a single command rather than a multi-hour manual task.

Source: a 2,000-word research article

Convert to slides for a webinar:

/pptx create a 12-slide deck from this article. Lead with the problem statement, use one key stat per slide, and close with a next-steps slide: [paste article]

Export as a gated PDF lead magnet:

/pdf create a formatted PDF guide from this article. Add a title page with "Free Guide" as a subtitle, page numbers, and a footer with the company URL: [paste article]

Build a supporting data table:

/xlsx create a comparison table from the statistics in this article. Columns: Metric, Industry Average, Our Finding, Source: [paste article]

The article, the deck, the PDF, and the spreadsheet all originate from the same source. No content is rewritten. it is restructured. This is the core productivity gain writing skills provide.

Client Deliverable Templates

Writers who produce recurring deliverables for clients benefit from building reusable invocation patterns rather than typing full instructions each session.

Monthly report template:

/docx create a monthly performance report with these sections: Executive Summary (3 bullets max), Key Metrics (table: Metric, This Month, Last Month, Change %), Highlights, Risks and Issues, Next Steps. Brand: [client name]. Month: [month].

Client pitch deck:

/pptx create a 7-slide pitch deck: title slide, problem we solve, our solution, how it works (3 bullets), case study, pricing table, call to action. Use this brand brief: [paste brief]

Technical specification document:

/docx create a technical specification with: Overview, Requirements (numbered list), Architecture (with a placeholder for a diagram), API Endpoints (table: Endpoint, Method, Description, Auth Required), Error Codes (table), Changelog. Author: [name]. Version: 1.0.

Save these as plain text snippets in a notes file or store them in supermemory. Retrieve and fire them at the start of each client engagement.

/supermemory store: acme-monthly-report-template = [paste full invocation text]

Then in any future session:

/supermemory What is the Acme monthly report template?

Paste the recalled template, swap in the current month and metrics, and the document is generated in seconds.

Productivity Patterns for Writers

Skills accelerate writing work most when they eliminate the transitions between tools. the switching between a text editor, spreadsheet, presentation app, and PDF viewer that fragments a writing session.

Pattern 1. Draft everything in a single session. Use the docx skill for the main deliverable, the xlsx skill for any supporting data, and the pdf skill for the final export. Stay in Claude Code throughout rather than opening separate applications for each format.

Pattern 2. Store client context before the first word. Before drafting anything for a client, pull their brand voice and style rules from supermemory. This front-loads the constraint-setting so every subsequent command in the session inherits the right tone automatically.

/supermemory What are the Thomson Industries writing rules?

Then prefix each draft request with the recalled guidelines. Every output in that session stays on-brand without repeating the brand brief at each step.

Pattern 3. Use tracked changes for revision rounds. Rather than sending a redline-free draft and waiting for feedback, use the docx skill to add tracked changes directly:

/docx open draft-v1.docx and apply these revisions as tracked changes: replace all instances of "utilize" with "use", shorten the introduction to 3 sentences, and add a comment on paragraph 4 noting that the stat needs a source

Clients or editors receive a document with visible changes they can accept or reject in Word. a workflow they already know, with no new tools for them to learn.

Pattern 4. Batch content production by format. When producing a content series. say, six topic guides for a product launch. generate all six Word drafts first, then convert all six to PDF in sequence. Batching by format keeps the work organized and prevents context-switching mid-session.

/docx create a 1,200-word guide on [topic 1] following this brief: [paste brief]
/docx create a 1,200-word guide on [topic 2] following this brief: [paste brief]

Once all drafts are approved:

/pdf convert guide-topic-1.docx to a formatted PDF with standard header and footer
/pdf convert guide-topic-2.docx to a formatted PDF with standard header and footer

The batch approach keeps session context stable and produces a consistent output quality across the series because the same guidelines are active throughout.

This site was built by 5 autonomous agents running in tmux while I was in Bali. 2,500 articles. Zero manual work. 100% quality gate pass rate. The orchestration configs, sprint templates, and quality gates that made that possible are in the Zovo Lifetime bundle. Along with 16 CLAUDE.md templates and 80 tested prompts. **[See how the pipeline works →](https://zovo.one/lifetime?utm_source=ccg&utm_medium=cta-skills&utm_campaign=best-claude-skills-for-writing-and-content-creation)** $99 once. I'm a solo dev in Da Nang. This is how I scale.

Related Reading

Try it: Estimate your monthly spend with our Cost Calculator.

*Built by theluckystrike. More at zovo.one *

Find the right skill → Browse 155+ skills in our Skill Finder.