Skip to content

rampstackco/claude-skills-seo / skills/content-and-copy

content-and-copy

Verified

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.

FileKindSize
SKILL.mdskill md8.0 KB
references/content-brief-template.mdmarkdown7.3 KB
references/content-edit-checklist.mdmarkdown7.1 KB

references/content-brief-template.md

View on GitHub
# Content Brief Template

Every piece of content needs a brief before writing. Without one, the piece will drift, miss the audience, or fail the goal.

A brief takes 15 minutes to write. Saves hours of rewrites later.

---

## Template

```markdown
# Brief: [Working title]

## Reader

Who specifically is this for? Be precise.

- Primary audience segment: [from content strategy]
- What they currently know: [their starting point]
- What they want to know: [the question they're bringing]
- What they need to do after: [the action this enables]

## Goal

What does this piece accomplish?

- Primary goal: [Inform / Convert / Rank / Retain / Entertain]
- Specific outcome: [What measurable thing should happen]
- Success metric: [How we know it worked]

## Pillar / Strategy fit

- Content pillar this serves: [from content strategy]
- Cornerstone or supporting: [Cornerstone / Supporting]
- Internal links to / from: [related pieces]

## Angle

What's the take? Why does this piece exist when others on the topic already do?

- The angle: [One sentence]
- Why ours is different: [Specific differentiator]
- The contrarian or surprising element: [If any]

## Format

- Type: [Article / Guide / Listicle / Comparison / Case study / How-to / Tutorial / Explainer]
- Length: [Word count or range]
- Reading level: [Beginner / Intermediate / Advanced]
- Required elements: [Images, tables, video, downloads, code blocks]

## Structure

Section-by-section outline. Headlines + 1 sentence on what each section does.

### [H1: Working title]

[Hook approach: how the piece will earn the read in 3 to 5 seconds]

### H2: [Section title]
[What this section accomplishes]

### H2: [Section title]
[What this section accomplishes]

### H2: [Section title]
[What this section accomplishes]

### H2: [Closing section]
[How the piece resolves and what action it points to]

## Voice

- Apply: [Brand voice attributes]
- Tone for this piece: [How tone adjusts for the topic]
- Specific cues: [Anything to lean into or avoid for this topic]

## Sources and citations

- Required sources: [Specific data, studies, or experts to cite]
- Internal data: [Anything we have that competitors don't]
- Quotes from: [SMEs, customers, founders to include]

## SEO

- Primary keyword: [from keyword research]
- Secondary keywords: [supporting terms]
- Search intent: [Informational / Commercial / Transactional / Navigational]
- Target SERP feature (if any): [Featured snippet / People also ask / etc.]
- Title tag (50-60 chars): [Draft]
- Meta description (120-160 chars): [Draft]
- URL slug: [Draft]

## Distribution

Where and how this piece gets seen after publishing.

- Newsletter inclusion: [Yes/No]
- Social posts: [Number of variations and channels]
- Outreach: [Specific people or sites to ping]
- Internal links to add from: [Existing pieces that should link to this]

## Constraints and notes

- Deadline: [Date]
- Word count: [Target]
- Required approvals: [Who needs to sign off]
- Things to avoid: [Anything off-limits for this piece]

## Out of scope

What this piece is explicitly NOT about. Prevents scope creep during writing.

- [Topic not in this piece]
- [Topic not in this piece]
```

---

## Filled example

```markdown
# Brief: How to choose between SQL and NoSQL for a startup

## Reader

- Primary audience segment: Technical founders or first engineers at early-stage startups (under 20 employees)
- What they currently know: Basics of databases, used both SQL and NoSQL casually
- What they want to know: Which to pick for their specific situation, what they'll regret in 18 months
- What they need to do after: Make the database choice and feel confident enough to commit

## Goal

- Primary goal: Inform (with rank as a secondary)
- Specific outcome: Reader makes the decision and references this piece when others ask
- Success metric: Top 3 ranking on "SQL vs NoSQL for startups" within 6 months; 5+ minute average read time

## Pillar / Strategy fit

- Content pillar: Startup engineering decisions
- Cornerstone or supporting: Cornerstone for the pillar
- Internal links: from "Founder's guide to technical debt" and to "When to migrate your database"

## Angle

- The angle: Most articles compare SQL and NoSQL on technical features. We compare on regret-likelihood at 18 months in production.
- Why ours is different: Built around real failure modes, not theoretical capabilities
- Surprising element: Most startups regret choosing NoSQL for the wrong reasons, not the right ones

## Format

- Type: Long-form decision guide
- Length: 2,500 to 3,500 words
- Reading level: Intermediate
- Required elements: Decision flowchart, 2-3 case examples, comparison table

## Structure

### H1: How to choose between SQL and NoSQL for a startup

Hook: Open with a specific founder's regret moment from a real conversation.

### H2: The wrong question (and the right one)
Most teams ask "which is faster" or "which scales." Reframe to "what will I regret in 18 months."

### H2: When SQL is the right call
Specific scenarios with examples.

### H2: When NoSQL is the right call
Narrower scenarios than most articles claim.

### H2: The hybrid that works
Real-world pattern: SQL primary, targeted NoSQL for specific use cases.

### H2: A decision flowchart
The actionable diagram. The piece's main asset.

### H2: What to do if you've already chosen wrong
Migration realism, with specific signals it's time to switch.

### H2: Closing
Return to the opening founder. Where they ended up. The decision framework as the takeaway.

## Voice

- Apply: Direct, experienced, not-academic
- Tone: Slightly weary about industry overcomplication
- Specific cues: First-person plural ("we"), war-story examples preferred over textbook explanations

## Sources

- Internal: Conversations with [N] startup CTOs
- External: [List of specific studies, posts, papers]
- Quotes: [Names if any]

## SEO

- Primary keyword: SQL vs NoSQL startup
- Secondary: SQL vs NoSQL for small teams, when to use NoSQL, NoSQL mistakes startups
- Search intent: Informational with commercial undertone
- Target SERP feature: Featured snippet for "when to use NoSQL"
- Title tag: SQL vs NoSQL for Startups: How to Avoid 18-Month Regret
- Meta: A practical guide to picking a database when you're 5 engineers, deciding fast, and don't want to migrate twice. Includes a decision flowchart.
- URL slug: sql-vs-nosql-startup

## Distribution

- Newsletter: Feature in next issue
- Social: 3 LinkedIn variations, 1 X thread
- Outreach: Email to 5 startup engineering newsletter writers
- Internal links: Add from /resources/cto-decisions and /technical-debt-guide

## Constraints

- Deadline: [Date]
- Word count: 3,000 target
- Approvals: Editorial lead and one technical SME
- Avoid: Vendor-specific recommendations (we're not selling a product)

## Out of scope

- Specific NoSQL database comparisons (CouchDB vs MongoDB) - separate piece
- Schema design tutorials - separate piece
- ORM choice - separate piece
```

---

## When to skip the brief

The brief is required for:
- Cornerstone content
- Anything over 1500 words
- Anything with a conversion goal
- Anything written by someone other than the editorial lead

The brief can be lighter for:
- Short newsletter blurbs
- Social posts
- Pieces written by the editorial lead with the strategy fully internalized

But "lighter" is not "absent." Even a 100-word note covering reader / goal / angle saves time.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall