Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal. Use this skill whenever the user wants to write an article, draft website copy, edit existing content for clarity or voice, write a blog post, or produce general editorial content. Triggers on write a blog post, draft an article, write copy for, edit this, rewrite this, write content, write a guide, draft a how-to, write web copy. Also triggers when content has been outlined and now needs to be written, or when existing content needs voice or clarity edits.
npx skills add https://github.com/rampstackco/claude-skills --skill content-and-copy
Write or edit content that serves a specific reader and goal. Stack-agnostic. This skill is for general content production. Specialized skills exist for landing pages (landing-page-copy) and email (email-sequences).
landing-page-copy)email-sequences)brand-voice)seo-keyword)content-strategy)If brand voice is undefined, run brand-voice first or use a working voice and document it as you go.
Strong content is strong on all five. Weakness on any one drags the rest down.
The opening earns the read. Most readers decide whether to continue within 3 to 5 seconds.
Strong hooks do one of:
Weak hooks:
The reader follows the flow without effort.
Common structures:
Pick a structure. Stick to it. Most weak content fails because the writer drifted between structures.
The piece sounds like the brand.
brand-voice definition)Test: Read a paragraph aloud. Does it sound like the brand? If it sounds like AI, generic marketing, or someone else's voice, edit until it doesn't.
The piece earns its length. Every paragraph adds something.
Substance comes from:
Lack of substance shows up as:
The piece ends with intention.
Strong closings:
Weak closings:
Default output is a markdown document at [content-slug].md ready to import into the CMS.
Structure:
# [H1: matches the title or tightly paraphrases]
[Hook paragraph. Earns the read in 3 to 5 seconds.]
[Body content with H2 sections, H3 subsections where useful.]
## [H2 section heading - descriptive, not clever]
[Section content.]
### [H3 if needed]
[Subsection content.]
## [H2 section heading]
[Section content.]
## [Closing section]
[Closing that resolves and points to next action.]
Front-matter for SEO and CMS:
---
title: [SEO title, 50 to 60 chars]
description: [Meta description, 120 to 160 chars]
slug: [url-slug]
author: [author]
date: [YYYY-MM-DD]
last_updated: [YYYY-MM-DD]
tags: [tag1, tag2]
category: [category]
---
references/content-brief-template.md - The brief that should exist before any content is written.references/content-edit-checklist.md - Pre-publish editing checklist.Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take rampstackco/content-and-copy from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.