Skip to main content
Watch: Claude Code Just Killed After Effects

SEO & Content

Content Pipeline

Use when taking a topic or a published video through research to a shipped, source-linked, SEO-structured blog post - the full path from raw idea to a post that ranks and stays fair. Covers research, drafting, SEO structure, cross-linking, and the pre-publish checklist. Also use when a published video has no post yet, or a draft is missing its primary sources, internal links, or FAQ. If something is being published, use this skill.

contentseoresearchdecision-intentfaq

4 files

Description

Use when taking a topic or a published video through research to a shipped, source-linked, SEO-structured blog post - the full path from raw idea to a post that ranks and stays fair. Covers research, drafting, SEO structure, cross-linking, and the pre-publish checklist. Also use when a published video has no post yet, or a draft is missing its primary sources, internal links, or FAQ. If something is being published, use this skill.

Install
SKILL.md

name: content-pipeline description: Use when taking a topic or a published video through research to a shipped, source-linked, SEO-structured blog post on the Developers Digest site - the full path from raw idea to a post that ranks and stays fair.

Content Pipeline

Take a topic or a published video and turn it into a blog post that is well researched, source-linked, structured for search, and safe to publish. This skill covers the whole lane: research, draft, SEO structure, and ship/verify.

Content stays in the SEO decision-intent lane: fair, factual comparison and tool-selection content (vs, compared, pricing, alternatives, best for). Cover developer tools and AI development workflows. Do not write about search, scraping, crawling, web extraction, or browser automation for extraction.

Stage 1 - Research

Ground the post in primary sources before writing a word. Official docs, changelogs, pricing pages, release notes, benchmarks, GitHub repos, credible expert analysis, and at least one opposing view. Synthesize into a practical take. Never publish thin commentary or unsourced claims, and never invent social proof.

See reference/research.md for the full quality bar and sourcing rules.

Stage 2 - Draft

Write the practical take, not a trend summary. Answer the reader's actual question early, be balanced to every tool covered, and keep every factual claim tied to a source you can link. State genuine strengths for each option instead of picking a universal winner.

Voice: concrete, practical, imperative. No em dashes, no emojis, no gradients in any embedded markup.

Stage 3 - SEO structure

Shape the draft for the decision-intent lanes and structured data. Answer the query in the first paragraph, use a comparison table for head-to-head facts, segment "best for X" recommendations, and add a ## FAQ section so the blog route auto-parses FAQ JSON-LD.

See reference/seo.md for lanes, the frontmatter block, and the FAQ JSON-LD rule.

Stage 4 - Ship and verify

Complete frontmatter, add the hero image, run the style check, and confirm the post appears in the blog listing and search index. For posts built from a published video, also add the archive and catalog entry (video-to-blog pipeline: every published video needs blog post + hero image + archive + catalog entry).

Run the full pre-publish checklist in scripts/checklist.md before shipping.

Pointers

  • reference/research.md - research quality bar and sourcing rules
  • reference/seo.md - decision-intent lanes, frontmatter, FAQ JSON-LD
  • scripts/checklist.md - pre-publish checklist to run before shipping
AI Development Stack

Get Smarter About AI Dev

New tutorials, open-source projects, and deep dives on coding agents - delivered weekly.

One email per weekReal code, not theoryFree forever