thatrebeccarae/claude-marketing / skills/content-workflow
content-workflow
VerifiedEnd-to-end content creation pipeline from research through editorial review to social distribution. Orchestrates a 3-stage workflow: research, draft/edit, and distribute. Supports blog posts, LinkedIn, Twitter threads, newsletters, and essays.
| File | Kind | Size |
|---|---|---|
| EXAMPLES.md | markdown | 2.2 KB |
| LICENSE | other | 1.0 KB |
| REFERENCE.md | markdown | 4.2 KB |
| SKILL.md | skill md | 4.0 KB |
REFERENCE.md
View on GitHub# Content Workflow — Reference
## Editorial Review Criteria
### Voice Consistency (Score 1-5)
| Score | Description |
|-------|-------------|
| 5 | Indistinguishable from the brand voice guide — reads as one unified voice |
| 4 | Consistent with minor deviations in 1-2 sentences |
| 3 | Generally on-brand but noticeable tonal shifts |
| 2 | Inconsistent — shifts between formal/casual or multiple personalities |
| 1 | Does not match the defined brand voice |
### Structural Quality (Score 1-5)
| Score | Description |
|-------|-------------|
| 5 | Hook grabs attention, body delivers value, CTA is clear and natural |
| 4 | Strong structure with one weak section |
| 3 | Serviceable but predictable — no memorable hook or weak ending |
| 2 | Disorganized — hard to follow the narrative thread |
| 1 | No discernible structure |
**Structural checklist:**
- [ ] Hook in first 2 sentences (not a generic intro)
- [ ] Clear thesis or promise early
- [ ] Body paragraphs each make one point
- [ ] Transitions between sections
- [ ] CTA aligned with content goal
- [ ] Appropriate length for format
### SEO Quality (Score 1-5, if applicable)
- [ ] Primary keyword in title and H1
- [ ] Primary keyword in first 100 words
- [ ] Secondary keywords in H2 headings
- [ ] Meta description written (150-160 chars)
- [ ] Internal links included
- [ ] Header hierarchy logical
### Factual Accuracy
- [ ] All statistics have sources
- [ ] Sources are credible and recent (<2 years)
- [ ] No unsupported claims
- [ ] Counter-arguments or caveats acknowledged
- [ ] Quotes are attributed
### Readability
- [ ] Appropriate reading level for audience
- [ ] Paragraphs 2-4 sentences
- [ ] Active voice dominant (>80%)
- [ ] No jargon without explanation
- [ ] Scannable (headers, bullets, bold)
## Quality Scoring Rubric
| Total Score | Decision |
|-------------|----------|
| 20-25 | **Pass** — approve for publishing |
| 15-19 | **Revise** — specific edits needed, list them |
| 10-14 | **Major revision** — structural or voice issues require rewrite |
| <10 | **Reject** — start over with new approach |
## Platform Adaptation Templates
### LinkedIn Post Template
```
[Hook — bold statement, surprising stat, or contrarian take]
[Paragraph 1 — expand on the hook with context]
[Paragraph 2 — the insight or framework]
[Paragraph 3 — practical takeaway or personal experience]
[CTA — specific question or invitation]
#hashtag1 #hashtag2 #hashtag3
```
**Rules:**
- First 2-3 lines appear before "see more" — make them count
- Use line breaks between paragraphs (LinkedIn collapses dense text)
- 3-5 hashtags, mix of broad (#marketing) and niche (#klaviyotips)
- 150-300 words optimal
### Twitter/X Thread Template
```
Tweet 1 (Hook):
[Standalone insight that makes people want more. End with "A thread:" or similar]
Tweet 2-N (Body):
[One idea per tweet. Each should be valuable on its own if retweeted.]
Final Tweet (CTA):
[Summary + call to action. "Follow @handle for more on [topic]" or "Bookmark this thread for later."]
```
**Rules:**
- Hook tweet must work as a standalone post
- Number tweets (1/, 2/, etc.) for readability
- Each tweet: one idea, one example, or one stat
- 5-12 tweets optimal
- Quote-tweet the first tweet with a summary for engagement
### Email Subject Lines
```
Option A (Number + Benefit): [X] Ways to [Achieve Result]
Option B (Question): Is Your [Thing] [Underperforming/Costing You]?
Option C (How-to): How to [Achieve Result] Without [Pain Point]
```
**Preview text (40-90 chars):**
```
[Expand on the subject line — add context or urgency]
```
### Pull Quote Format
```
"[2-3 sentence excerpt that stands alone as an insight]"
— From: [Article Title]
```
Select quotes that:
- Contain a specific stat or bold claim
- Work without surrounding context
- Are under 280 characters (tweetable)
## Follow-Up Cadence
After publishing:
| Timeframe | Action |
|-----------|--------|
| Day 0 | Publish primary piece + distribute social pack |
| Day 1 | Engage with comments/replies on all platforms |
| Day 3 | Share pull quote as a standalone social post |
| Day 7 | Repurpose as a different format (e.g., blog → thread) |
| Day 14 | Measure performance, note learnings |
| Day 30 | Evaluate for evergreen update or sequel |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |