essay-publishing-pipeline
Publish essays and long-form content through a structured pipeline from draft to distribution. Covers markdown-to-HTML conversion, metadata management, cross-posting strategies, and RSS/Atom feed generation. Triggers on essay publishing, content pipeline, or blog deployment requests.
Best use case
essay-publishing-pipeline is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Publish essays and long-form content through a structured pipeline from draft to distribution. Covers markdown-to-HTML conversion, metadata management, cross-posting strategies, and RSS/Atom feed generation. Triggers on essay publishing, content pipeline, or blog deployment requests.
Teams using essay-publishing-pipeline should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/essay-publishing-pipeline/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How essay-publishing-pipeline Compares
| Feature / Agent | essay-publishing-pipeline | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Publish essays and long-form content through a structured pipeline from draft to distribution. Covers markdown-to-HTML conversion, metadata management, cross-posting strategies, and RSS/Atom feed generation. Triggers on essay publishing, content pipeline, or blog deployment requests.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Essay Publishing Pipeline
Move written content from draft through editing, formatting, and multi-platform distribution.
## Pipeline Architecture
```
Draft → Edit → Format → Metadata → Build → Publish → Distribute
↑ │
└──────────── Feedback Loop ───────────────────────────┘
```
### Stage Definitions
| Stage | Input | Output | Tools |
|-------|-------|--------|-------|
| Draft | Ideas, notes | Raw markdown | Editor, voice notes |
| Edit | Raw markdown | Polished markdown | Linter, peer review |
| Format | Polished markdown | Structured content | Frontmatter, templates |
| Metadata | Structured content | Enriched content | Tags, categories, SEO |
| Build | Enriched content | HTML/PDF output | SSG, Pandoc |
| Publish | Built output | Live content | Deploy, CMS API |
| Distribute | Published URL | Cross-posts | RSS, social, newsletter |
## Content Structure
### Markdown with Frontmatter
```markdown
---
title: "On the Architecture of Automated Systems"
subtitle: "Why eight organs beat one monolith"
author: "Author Name"
date: 2026-03-20
updated: 2026-03-20
status: published
tags: [architecture, automation, organvm]
category: systems-thinking
series: "Orchestration Essays"
series_order: 3
abstract: >
A 2000-word exploration of why modular organ-based
architecture outperforms monolithic automation.
canonical_url: "https://example.com/essays/architecture-of-automated-systems"
---
# On the Architecture of Automated Systems
Opening paragraph that hooks the reader...
```
### Essay Taxonomy
| Field | Purpose | Example |
|-------|---------|---------|
| `status` | Workflow state | draft, review, published, archived |
| `tags` | Topic classification | [architecture, automation] |
| `category` | Primary category | systems-thinking |
| `series` | Multi-part grouping | "Orchestration Essays" |
| `canonical_url` | SEO canonical | Primary publication URL |
| `abstract` | Summary for feeds/cards | 1-2 sentence summary |
## Markdown Processing
### Conversion Pipeline
```bash
# Markdown → HTML with Pandoc
pandoc essay.md \
--from markdown+yaml_metadata_block \
--to html5 \
--template template.html \
--highlight-style tango \
--toc \
--toc-depth=2 \
--output essay.html
# Markdown → PDF
pandoc essay.md \
--pdf-engine=weasyprint \
--css style.css \
--output essay.pdf
```
### Static Site Generator Integration
```python
# Build script for essay collection
from pathlib import Path
import yaml
import markdown
def build_essays(source_dir: str, output_dir: str):
essays = []
for md_file in sorted(Path(source_dir).glob("*.md")):
text = md_file.read_text()
frontmatter, content = text.split("---\n", 2)[1:]
meta = yaml.safe_load(frontmatter)
if meta.get("status") != "published":
continue
html = markdown.markdown(content, extensions=["fenced_code", "tables", "toc"])
essays.append({"meta": meta, "html": html, "slug": md_file.stem})
for essay in essays:
output = Path(output_dir) / f"{essay['slug']}/index.html"
output.parent.mkdir(parents=True, exist_ok=True)
output.write_text(render_template(essay))
build_index(essays, output_dir)
build_rss_feed(essays, output_dir)
```
## RSS/Atom Feed Generation
```python
from datetime import datetime
import xml.etree.ElementTree as ET
def build_rss_feed(essays: list[dict], output_dir: str):
rss = ET.Element("rss", version="2.0")
channel = ET.SubElement(rss, "channel")
ET.SubElement(channel, "title").text = "Essay Collection"
ET.SubElement(channel, "link").text = "https://example.com/essays"
ET.SubElement(channel, "description").text = "Long-form writing on systems and culture"
for essay in essays[:20]:
item = ET.SubElement(channel, "item")
ET.SubElement(item, "title").text = essay["meta"]["title"]
ET.SubElement(item, "link").text = f"https://example.com/essays/{essay['slug']}"
ET.SubElement(item, "description").text = essay["meta"].get("abstract", "")
ET.SubElement(item, "pubDate").text = essay["meta"]["date"].strftime(
"%a, %d %b %Y 00:00:00 GMT"
)
tree = ET.ElementTree(rss)
tree.write(f"{output_dir}/feed.xml", xml_declaration=True, encoding="utf-8")
```
## Cross-Posting Strategy
### POSSE (Publish on Own Site, Syndicate Elsewhere)
```
Own site (canonical) → Medium → Dev.to → LinkedIn → Newsletter
↗ ↗
RSS feed triggers automation
```
### Cross-Post Formatting
| Platform | Format | Limits | Notes |
|----------|--------|--------|-------|
| Own site | Full HTML | None | Canonical URL |
| Medium | Markdown import | None | Set canonical URL |
| Dev.to | Markdown + frontmatter | None | Use API for automation |
| LinkedIn | Plain text + link | 3000 chars | Excerpt + link to full |
| Newsletter | HTML email | Images inline | Adapt layout for email |
### Automated Cross-Posting
```python
async def cross_post(essay: dict):
canonical = essay["meta"]["canonical_url"]
# Dev.to
await devto_api.create_article(
title=essay["meta"]["title"],
body_markdown=essay["content"],
canonical_url=canonical,
tags=essay["meta"]["tags"][:4],
published=True,
)
# Newsletter
await newsletter_api.create_campaign(
subject=essay["meta"]["title"],
html=render_email_template(essay),
)
```
## Quality Gates
### Pre-Publish Checklist
- [ ] Spell check and grammar review
- [ ] Links verified (no 404s)
- [ ] Images optimized and alt-text present
- [ ] Frontmatter complete (title, date, tags, abstract)
- [ ] Canonical URL set
- [ ] Open Graph / social card metadata present
- [ ] RSS feed validates
- [ ] Mobile rendering verified
### SEO Metadata
```html
<meta property="og:title" content="Essay Title">
<meta property="og:description" content="Abstract text">
<meta property="og:type" content="article">
<meta property="og:url" content="https://example.com/essays/slug">
<meta name="twitter:card" content="summary_large_image">
```
## Anti-Patterns
- **Publishing without canonical URL** — Leads to duplicate content SEO penalties
- **Manual cross-posting** — Automate with APIs and RSS triggers
- **No RSS feed** — Essential for syndication and discoverability
- **Draft content leaking** — Always check `status` field before building
- **No versioning** — Track `updated` date for revised essays
- **Platform-first publishing** — Always publish on own domain first (POSSE)Related Skills
data-pipeline-architect
Designs ETL/ELT data pipelines with proper extraction, transformation, and loading patterns, including orchestration, error handling, and data quality validation.
data-ingestion-pipeline
Build data ingestion pipelines for batch and streaming data from multiple sources. Covers extraction strategies, format normalization, deduplication, validation gates, and staging patterns. Triggers on data ingestion, ETL pipeline, or data import architecture requests.
conversation-content-pipeline
Transform AI conversations and chat transcripts into publishable content including blog posts, documentation, tutorials, and knowledge base entries. Covers extraction, restructuring, and editorial refinement. Triggers on conversation-to-content, transcript processing, or chat-to-doc requests.
taxonomy-modeling-design
Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.
systemic-ingestion-normalization
Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.
system-environment-configuration
Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.
pentaphase-orchestrator
Threads the full five-phase structural-overhaul protocol — landscape discovery, taxonomy design, environment configuration, systemic ingestion, governance evolution — for any substrate the user names. Use when the user requests a structural overhaul, system redesign, or end-to-end restructuring of a documentation system, asset registry, code monorepo, knowledge base, or operational workflow; or when they explicitly invoke the pentaphase methodology. Coordinates handoffs between phase-skills and seats validation gates between phases.
landscape-discovery-audit
Phase 1 of the pentaphase structural-overhaul protocol. Inventories assets, maps current flow, identifies friction, and defines value metrics for any substrate. Use when the user invokes phase 1 of an overhaul, requests a baseline audit, asks to "discover the landscape" of a system, or wants to understand current state before redesigning. Produces phase-1-landscape-report.md.
governance-evolution-protocol
Phase 5 of the pentaphase structural-overhaul protocol. Codifies operational protocols, onboards the ecosystem of participants, programs behavior monitoring, and establishes an iteration cadence so the substrate evolves rather than calcifies. Use when the user invokes phase 5 of an overhaul, asks to "establish governance" or "lock in the protocols", or has completed ingestion and is ready to declare the substrate operational. Consumes phase-4-ingestion-report.md; produces phase-5-governance-charter.md, which closes the protocol.
dimension-surfacing
Surfaces the parallel domain dimensions implicit in a dense or minimal prompt. Use when a user prompt is small on the surface but plainly implies multiple independent domains needing different expertise; when explicitly invoked by the coliseum-orchestrator skill as Phase 1; or when the user asks "what dimensions does this prompt encode" or "what axes does this break into." Produces a named dimension set where each dimension is independently executable and not a paraphrase of another.
coliseum-dispatch
Dispatches a composed set of assignment envelopes to domain-expert subagents in parallel, in a single message with multiple Agent tool calls. Enforces the no-pingpong gate via the pingpong-detector agent before any dispatch fires. Use when invoked by the coliseum-orchestrator as Phase 3; when envelopes are already composed and the next step is parallel execution; or when the user asks to "fan out" or "dispatch in parallel." Produces a dispatch log capturing what was sent, when, and where returns land.
assignment-composition
Wraps each surfaced dimension as a self-contained 9-section autonomous-work-assignment envelope — scope, context, success criteria, allowed tools, return format, handoff — all the recipient subagent needs to execute without coming back. Use when invoked by coliseum-orchestrator as Phase 2; when dimensions are named and the next step is to make each independently dispatchable; or when the user asks "compose this as an assignment." The no-pingpong gate validates each envelope before dispatch.