content-writing

Files (24)

• README.md
• SKILL.md
• .gitkeep · examples/
• .gitkeep · hooks/
• README.md · references/
• ai-citation-patterns.md · references/
• content-decay-signals.md · references/
• content-structure-templates.md · references/
• gap-analysis-example.md · references/
• gap-analysis-frameworks.md · references/
• gap-analysis-templates.md · references/
• geo-optimization-techniques.md · references/
• item-reference.md · references/
• keyword-intent-taxonomy.md · references/
• keyword-prioritization-framework.md · references/
• keyword-research-example.md · references/
• quotable-content-examples.md · references/
• refresh-example.md · references/
• refresh-templates.md · references/
• seo-writing-checklist.md · references/
• title-formulas.md · references/
• topic-cluster-templates.md · references/
• .gitkeep · scripts/
• .gitkeep · templates/

SKILL.md (first lines)

# Content Writing

## Overview

A unified content-writing skill covering the full content lifecycle:

| Mode | Trigger | Output |
|------|---------|--------|
| **Blog** | "write a blog / turn these notes into an article" | Canonical blog article with outline, draft, and metadata |
| **X Article** | "write / optimize an X Article / Twitter Article" | 8-step analysis + complete optimized rewrite |
| **LinkedIn** | "write a LinkedIn post / article / carousel" | LinkedIn-native draft ready to publish |
| **Syndication** | "repurpose this across channels / give me a distribution pack / syndicate to Dev.to, Hashnode, Reddit" | Per-channel artifacts for X, LinkedIn, Substack, Medium, Dev.to, Hashnode, Reddit |
| **Humanize** | "humanize this / remove AI traces / make this sound human" | De-AI-ified rewrite with pattern commentary and quality score |
| **GEO Optimize** | "optimize for AI / get cited by ChatGPT / make this AI-quotable" | GEO analysis + before/after score + AI-citation-ready rewrite |
| **Content Audit** | "audit content quality / CORE-EEAT score / content quality check" | 80-item CORE-EEAT audit report with dimension scores, veto checks, and prioritized action plan |
| **Content Refresh** | "update old content / refresh this article / content is outdated / traffic declining / rankings dropped" | Freshness analysis, update prioritization, refresh plan, GEO enhancement, and republishing strategy |
| **Content Gap Analysis** | "find content gaps / content opportunities / what am I missing / untapped topics" | Competitive gap analysis, keyword gap matrix, format gaps, audience journey gaps, and prioritized content calendar |
| **Keyword Research** | "find keywords / keyword research / what should I write about / identify ranking opportunities" | Keyword discovery report with intent classification, difficulty scoring, opportunity matrix, topic clusters, GEO potential, and content calendar |
| **Support-to-Content** | "analyze support tickets / content from customer questions / what should I document / reduce support load" | Ticket pattern analysis + prioritized content briefs for help articles and blog posts |
| **Edit Article** | "edit / revise / improve this article / restructure these sections / tighten prose" | DAG-ordered section map confirmed with user + per-section rewrite with tight paragraphs |

### Natural Content Pipeline

These modes build on each other in a predictable order:

```
Support tickets → [Support-to-Content] → Content briefs (help articles, blog posts)
                                                        ↓
Content strategy → [Keyword Research] → High-value keyword list + topic clusters
                                                        ↓
                   [Content Gap Analysis] → Prioritized opportunity list + content calendar
                                                        ↓
Raw knowledge → [Blog mode] → Canonical blog article
                                    ↓
                           [X Article mode] → X-native long-form
                                    ↓
                        [Syndication mode] → X thread, LinkedIn post,
                                             Substack newsletter, Medium article,
                                             Dev.to post, Hashnode article, Reddit post
                                    ↓
                      [GEO Optimize mode] → AI-citation-ready rewrite
                                    ↓
                    [Content Audit mode] → CORE-EEAT quality gate

Existing content → [Content Refresh mode] → Updated article with fresh stats,
                                             new sections, GEO enhancements,
                                             and republishing strategy
```

Use **Keyword Research** first when you need to discover what people are actually searching for before defining your strategy. Use **Content Gap Analysis** when you already know your topic space and want to benchmark against competitors. Use **Blog** first when starting from scratch on a specific topic. Use **Syndication** when you already have a finished canonical piece. Use **Humanize** on any draft — yours or AI-generated — that reads like a machine wrote it. Use **Content Audit** as a final quality gate before publishing.

### Visual Companion Assets

When the user also needs visuals for the content, keep the asset plan explicit instead of treating imagery as an afterthought.

Supported paths:

1. Images generated during the task
2. Existing external image URLs already referenced in the repo
3. Existing local repo images
4. Code-as-image product visuals
5. Mixed compositions

Decision rules:

1. Prefer code-as-image for product-led articles, carousels, and feature explainers where the image should faithfully represent the product.
2. Reuse existing external URLs when the right asset already exists.
3. Local repo images are valid, but if the artifact is meant for hosted distribution, prefer promoting them to the active asset host or public URL.
4. Generate supporting imagery on the fly when the repo does not already cover the need.
5. For actual visual production, hand off to `code-as-images`, `code-slides`, `html-visualization`, or `video-generation` as appropriate.

---

## Mode 1 — Blog Articles

### When to Use

- User says "turn these notes into a blog", "write a blog article on X", or "create a blog post from this".
- Input is a knowledge dump, transcript, tweet thread, outline, or rough draft.
- Target output is a **blog article** (site, company blog, or publication).

### Inputs to Collect

- **Source knowledge** — notes, transcript, excerpts, or rough draft. If multiple sources, clarify which is primary.
- **Target reader** — job title, level, context. What do they already know?
- **Goal** — inform / teach / persuade / activate. Desired reader action at the end.
- **SEO constraints** (if relevant) — primary keyword, 3–7 supporting phrases, length range.

Ask 2–3 targeted questions if anything critical is missing.

### Output Requirements

Always produce:

1. **Concept & angle** — 2–3 possible angles with rationale for the chosen one.
2. **SEO-aware outline** — H1 and H2/H3 structure; keyword placement notes.
3. **Full blog draft** — strong title, opening hook (2–4 paragraphs), 3–6 main sections, evidence, transitions, close with 2–4 takeaways and a concrete CTA.
4. **Metadata** — word count, slug, meta description, 3–5 headline variants, optional internal link ideas.

### Blog Structure Patterns

Pick the best fit; state the chosen pattern explicitly.

**1. Problem → Insight → Playbook**
Best when the goal is to help readers solve a known pain.
- Hook: name the problem and why current advice fails.
- Insight: the missing mental model or principle.
- Playbook: concrete steps, checklists, or templates.
- Close: recap + "start here today" CTA.

**2. Story → Lessons → Application**
Best when the source contains a case study, founder journey, or failure/success narrative.
- Story: vivid narrative with enough detail to care.
- Lessons: 3–5 explicit principles.
- Application: how the reader applies them.
- Close: encourage trying one lesson this week.

**3. Myth → Reality → New Approach**
Best for contrarian angles or busting bad advice.

From alvarovillalbaa/afs, MIT.

More from alvarovillalbaa/afs