Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Content And Copy

ASecurity

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 ne...

935 stars
0 votes
0 copies
2 views
Added 9/22/2026
ai-agentsgo

Security Analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned 9/22/2026

$npx -y skills add rampstackco/claude-skills --skill content-and-copy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Content And Copy?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Content And Copy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rampstackco-content-and-copy-claude-skills/badge)](https://www.skillsdirectory.com/skills/rampstackco-content-and-copy-claude-skills)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: content-and-copy
description: "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."
---

# 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`).

---

## When to use

- Writing a blog post or article
- Drafting website copy (homepage sections, about, services)
- Editing existing content for voice or clarity
- Writing how-to guides, listicles, or explainers
- Producing knowledge base or help center articles
- Adapting brand voice to a specific piece

## When NOT to use

- Landing pages with conversion goals (use `landing-page-copy`)
- Email campaigns or sequences (use `email-sequences`)
- Brand voice definition (use `brand-voice`)
- SEO keyword research (use `seo-keyword`)
- Content strategy and planning (use `content-strategy`)

---

## Required inputs

- The piece to be written or edited
- The target reader (specific audience segment)
- The goal of the piece (inform, convert, rank, retain, entertain)
- The brand voice (or willingness to define it)
- Length target and any structural constraints

If brand voice is undefined, run `brand-voice` first or use a working voice and document it as you go.

---

## The framework: 5 dimensions

Strong content is strong on all five. Weakness on any one drags the rest down.

### 1. Hook

The opening earns the read. Most readers decide whether to continue within 3 to 5 seconds.

**Strong hooks do one of:**

- **Promise specific value.** "By the end, you'll know exactly which X to pick for your situation."
- **Surface a tension.** "Most advice on X is wrong. Here's why."
- **Open a loop.** A question or scenario the rest of the piece resolves.
- **State a contrarian point.** Provided you can defend it.
- **Show, don't summarize.** A specific moment or scenario the reader recognizes.

**Weak hooks:**

- Throat-clearing ("In today's fast-paced world...")
- Dictionary-definition openers ("X is a type of Y that...")
- Stating the obvious ("Many people struggle with X.")
- Vague promises ("This article will explore X.")

### 2. Structure

The reader follows the flow without effort.

**Common structures:**

- **Problem → Solution → Proof.** Most non-fiction.
- **List + reasoning.** Listicles with substance, not filler.
- **How-to (numbered steps).** Procedural content.
- **Compare → Contrast → Recommend.** Comparison and review content.
- **Story → Lesson.** Narrative non-fiction.
- **Question → Answer → Implication.** Explainers and analysis.

Pick a structure. Stick to it. Most weak content fails because the writer drifted between structures.

### 3. Voice

The piece sounds like the brand.

- Voice attributes consistent throughout (per `brand-voice` definition)
- Tone shifts appropriately for context (a serious topic gets a serious tone, even from a playful brand)
- Vocabulary preferences honored
- Grammar and style standards followed (contractions, em dashes, sentence length)
- Reads aloud like the brand would actually talk

**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.

### 4. Substance

The piece earns its length. Every paragraph adds something.

**Substance comes from:**

- **Specifics.** "Roughly 40 percent" beats "many." Names, numbers, examples, data.
- **Original perspective.** Your take, not a summary of everyone else's.
- **Actionable detail.** What the reader does with this information.
- **Honest tradeoffs.** What's NOT true, what doesn't work, what's overhyped.
- **Real examples.** Specific scenarios, real customers, real failures.

**Lack of substance shows up as:**

- Padding ("It's important to note that...")
- Restating the same point in three different paragraphs
- Generalities that anyone in the category could write
- Word counts hit by stretching, not depth

### 5. Closing

The piece ends with intention.

**Strong closings:**

- **Resolve the loop opened in the hook.**
- **Issue a specific next action.** What does the reader do now?
- **Land a memorable line.** Something quotable.
- **Return to the opening.** Echo or invert the first line.

**Weak closings:**

- Summary that restates the article
- "Hope this helps!" or equivalent
- A wall of CTAs from unrelated programs
- Trailing off with no clear ending

---

## Workflow

### For new pieces

1. **Confirm the brief.** Reader, goal, length, voice. If the brief is vague, do not write yet.
2. **Outline.** Structure first. Headlines and section purposes only. Skip prose until the structure is sound.
3. **Open with the hook.** Write the opening before anything else. If the hook isn't working, the rest won't either.
4. **Draft for substance.** First draft is about getting the substance down. Voice comes in editing.
5. **Edit for voice.** Read aloud. Tighten sentences. Cut padding. Apply brand voice.
6. **Edit for clarity.** Each paragraph: does it earn its place? Each sentence: is the meaning unambiguous?
7. **Pre-publish checks.** Headers in order, no skipped levels, internal links present, image alt text written, SEO basics applied (title, meta, slug).

### For editing existing content

1. **Read the whole piece first.** Do not edit on first read. Understand it before changing it.
2. **Identify what's working.** Note the strong sections so you don't damage them.
3. **Identify what's broken.** Voice mismatches, weak structure, vague claims, padding.
4. **Edit by priority.** Structure first (move sections, cut sections). Then substance (strengthen claims). Then voice. Then sentence-level polish.
5. **Read aloud.** Catch awkward phrasing the eye misses.

---

## Failure patterns

- **Writing without a brief.** Without reader, goal, and voice defined, the piece drifts.
- **Burying the lead.** The most important thing is in paragraph 8 because the writer "got there."
- **Padding to hit word count.** Length should serve the reader, not the production schedule.
- **Generic voice.** Sounds like every other article in the category. Brand voice neutralized.
- **Weak transitions.** Sections feel disconnected. Reader has to do the work the writer should have done.
- **No closing.** The piece runs out instead of ending.
- **Edit by adding.** Fixing weak content by piling on more words. Strong editing usually cuts.
- **Ignoring the headers.** Headers carry navigation weight. Bad headers fail readers who scan.

---

## Output format

Default output is a markdown document at `[content-slug].md` ready to import into the CMS.

Structure:
```markdown
# [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:
```yaml
---
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]
---
```

---

## Reference files

- [`references/content-brief-template.md`](references/content-brief-template.md) - The brief that should exist before any content is written.
- [`references/content-edit-checklist.md`](references/content-edit-checklist.md) - Pre-publish editing checklist.

Attribution

rampstackcorampstackco
View sourceSee grades on GitHubMore from rampstackco →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →