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 |
EXAMPLES.md
View on GitHub# Content Workflow — Examples
## Example 1: Full Pipeline Run
**Prompt:**
> Run the full content workflow on the topic: "Why most marketing teams waste their first 90 days with a new analytics tool."
**Expected output:**
**Stage 1 (Research):** Brief with 5-8 sources covering common analytics implementation mistakes, average time-to-value for marketing analytics tools, and expert opinions on onboarding best practices.
**Stage 2 (Draft):** 1,800-word blog post with:
- Hook: stat about analytics tool churn in year 1
- Body: 4-5 common mistakes with evidence
- Framework: "90-day activation plan"
- CTA: download a template
**Stage 2 (Review):** Editorial scorecard showing Voice: 4/5, Structure: 5/5, SEO: 4/5, Accuracy: 5/5, Readability: 4/5. One revision note: "Hook could be more specific."
**Stage 3 (Distribute):**
- LinkedIn post (250 words with the "90-day" angle)
- Twitter thread (8 tweets, one mistake per tweet)
- 3 email subject lines
- 4 pull quotes
---
## Example 2: Review an Existing Draft
**Prompt:**
> Review this draft LinkedIn post about Klaviyo's new AI features. [draft provided]
**Expected output:** Editorial review with scores:
- Voice: 3/5 — "Shifts from casual to formal in paragraph 3. Match the conversational tone of paragraphs 1-2 throughout."
- Structure: 4/5 — "Strong hook, but CTA is generic. Replace 'What do you think?' with a specific question."
- Readability: 5/5
- Decision: **Revise** — 2 specific edits listed
---
## Example 3: Distribution Pack from Finished Article
**Prompt:**
> Create a distribution pack for this published blog post about Google Ads wasted spend. [article provided]
**Expected output:**
- **LinkedIn post:** 220 words, opens with "Most companies are burning 30% of their Google Ads budget on irrelevant search terms." CTA asks for reactions.
- **Twitter thread:** 7 tweets. Hook: the 30% stat. Body: one wasted-spend category per tweet with example. Close: link to full article.
- **Email subject lines:**
1. "Your Google Ads account is leaking money"
2. "How to find the 30% waste in your ad budget"
3. "The search term report your agency isn't showing you"
- **Pull quotes:** 4 excerpts under 280 chars each, covering the key stats and recommendations.
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 |