Skip to content

rampstackco/claude-skills / 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
README.mdmarkdown357 B
SKILL.mdskill md8.0 KB
references/content-brief-template.mdmarkdown7.3 KB
references/content-edit-checklist.mdmarkdown7.1 KB

references/content-edit-checklist.md

View on GitHub
# Content Edit Checklist

A pre-publish checklist for editing content. Run it line by line before any piece of content goes live.

The checklist catches the regular mistakes. Editing for substance is a separate pass.

---

## Pass 1: substance

Before sweating commas, confirm the piece does its job.

- [ ] **The brief is satisfied.** Re-read the content brief. Does this piece deliver against every objective?
- [ ] **The audience is the right one.** Who is the reader? Are they assumed correctly?
- [ ] **The single takeaway is clear.** If a reader skims and remembers one thing, what is it? Is it what we wanted?
- [ ] **The first 50 words earn the next 50.** Cut throat-clearing intros. Get to the point.
- [ ] **Every paragraph earns its place.** If a paragraph could be removed without loss, remove it.
- [ ] **The structure serves the reader.** Headers form a meaningful outline. Skim test passes.
- [ ] **There is one CTA per piece, and it is unmissable.** Or zero, if the piece is purely informational.
- [ ] **No claim is unsupported.** Every fact, statistic, or assertion has a source or is hedged.
- [ ] **Examples are concrete.** Specific numbers, named scenarios, real artifacts beat vague "many users" generalizations.

---

## Pass 2: voice and tone

- [ ] **Voice matches the brand voice document.** Read aloud. If a stranger could not place this as our brand, voice is too generic.
- [ ] **Tone matches the context.** Promotional vs editorial vs technical vs support. Different content, different tone shifts.
- [ ] **Pronouns are consistent.** "You" / "we" / "our" stay stable across the piece.
- [ ] **No internal voice leaked into customer-facing copy.** Jargon, project names, internal team names removed.
- [ ] **No first-person commentary in instructional content.** ("I think you should..." → "Do this because...")

---

## Pass 3: structure and scannability

- [ ] **Headings are descriptive, not clever.** "How to add a payment method" beats "Money matters."
- [ ] **Heading hierarchy is correct.** One H1, then H2s for top-level sections, H3s under H2s. No skipping levels.
- [ ] **Paragraphs are tight.** Default 2-4 sentences per paragraph for web. One-sentence paragraphs are allowed for emphasis.
- [ ] **Lists are used where they fit.** Bullets for parallel items, numbered for sequenced steps.
- [ ] **Bold and italic used sparingly.** Bold for the term being defined, italic for emphasis. Not both. Not often.
- [ ] **Code blocks for code.** Inline code for short references.
- [ ] **Tables for tabular data.** Not for layout.

---

## Pass 4: clarity at the sentence level

- [ ] **Active voice by default.** Passive voice for specific reasons (focus on object, unknown actor, polite distancing).
- [ ] **Concrete nouns and verbs.** "We process" beats "processing is performed by us."
- [ ] **Average sentence length under 20 words.** Vary the rhythm with shorter sentences for emphasis.
- [ ] **No nominalizations.** "Decide" beats "make a decision." "Implement" beats "carry out the implementation of."
- [ ] **No throat-clearing phrases.** Cut "It is important to note that," "In order to," "At the end of the day."
- [ ] **No filler intensifiers.** Cut "very," "really," "quite," "actually," "basically." Each weakens the word it modifies.
- [ ] **No hedge words where you mean something specific.** "May," "might," "could" are honest when uncertain, weak when specific.

---

## Pass 5: jargon and accessibility

- [ ] **Jargon defined on first use.** Or replaced if the audience would not know it.
- [ ] **Acronyms spelled out on first use.** Then acronym is fine.
- [ ] **No insider language.** Project codenames, internal team references, deprecated product names.
- [ ] **Idioms checked for global audiences.** "Hit it out of the park" reads strange to non-US English readers.
- [ ] **Reading level appropriate.** Use a tool (Hemingway, Readable) to spot-check. For most audiences, target Grade 8-10.
- [ ] **No ableist or exclusionary language.** "Crazy" → "wild," "blacklist" → "blocklist," gendered defaults checked.

---

## Pass 6: SEO basics

If the piece is for organic search:

- [ ] **Primary query target identified.** One phrase per piece.
- [ ] **Title tag drafted.** Distinct from H1, 50-60 characters, primary query near front.
- [ ] **Meta description drafted.** 140-160 characters, value-led, includes primary query naturally.
- [ ] **H1 is unique on the site and includes the primary query.**
- [ ] **Internal links added.** 2-5 contextual links to related content on the site.
- [ ] **External links added.** Link out where it adds value or substantiates a claim.
- [ ] **Images have descriptive alt text.** Decorative images get `alt=""`.
- [ ] **URL slug is short, lowercase, hyphenated, includes primary query.**
- [ ] **Schema considered.** Article, FAQ, HowTo, etc. - whichever fits the format.

---

## Pass 7: facts and claims

- [ ] **Numbers verified.** Especially statistics, dates, prices, version numbers.
- [ ] **Names spelled correctly.** People, products, companies, places.
- [ ] **Quotes verified verbatim.** Speaker name, attribution, context correct.
- [ ] **Dates checked.** "Last updated" reflects the actual edit date.
- [ ] **Links work and go where they say.** No 404s, no redirect chains, no link rot to dead resources.
- [ ] **Screenshots are current.** Older screenshots show outdated UI; refresh or remove.
- [ ] **Claims about competitors are fair and current.** Or removed.

---

## Pass 8: legal and compliance

- [ ] **Trademarked terms used correctly.** Capitalization, ™ or ® where required by license.
- [ ] **Disclaimers present where needed.** Affiliate disclosures, regulated industry disclaimers, advisory caveats.
- [ ] **Customer permissions secured for testimonials.** Case studies, quotes, photos.
- [ ] **No confidential or pre-announcement information.** Product roadmaps, unannounced pricing, internal team names.
- [ ] **Image rights clear.** Licensed stock, original photography, or in-house illustration.

---

## Pass 9: cross-channel consistency

If the piece appears in more than one place:

- [ ] **Web vs email vs social variants align in message.** Tone may shift; substance does not contradict.
- [ ] **Excerpts and meta descriptions match the piece.** No bait-and-switch.
- [ ] **CTAs point to current destinations.** Landing page is live, has matching messaging, is not stale.

---

## Pass 10: final mechanical sweep

- [ ] **Spellcheck.** Twice. Once with autocorrect off so it does not silently fix names.
- [ ] **Grammar check.** Tool-assisted, then human-verified.
- [ ] **Punctuation consistent.** Oxford comma, smart quotes, dashes - per the style guide.
- [ ] **No double spaces.** Find-and-replace.
- [ ] **No trailing whitespace at line ends.**
- [ ] **No placeholder text left in.** "Lorem ipsum," "TBD," "[INSERT QUOTE]," "TKTK."
- [ ] **No commented-out drafts in the source.** Especially in CMS HTML view.

---

## Sign-off

| Pass | Editor | Date |
|---|---|---|
| Substance | | |
| Voice and tone | | |
| Structure | | |
| Sentence-level | | |
| Jargon and accessibility | | |
| SEO | | |
| Facts and claims | | |
| Legal and compliance | | |
| Cross-channel | | |
| Mechanical | | |

Final approval: [Name, date]

Ready to publish: [ ]
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: 471kUpdated 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