cluster-orchestratorlisted

Master orchestrator for building complete SEO content clusters for competitor comparisons of the product described in product-context.md. Use this skill whenever the user asks to build a content cluster, run the cluster system, create a "[Product] vs [Competitor]" content set, build a comparison cluster, run the hub-and-spoke playbook, or starts a request with "{{PRODUCT}} vs", "[Product] vs [Competitor]", "build cluster for", "compete with", or "[Competitor] alternatives cluster". This skill reads the cluster name from the user, confirms scope, and then orchestrates the full chain of cluster skills (planner, writer, quality-checker, visual-designer, link-validator, performance-tracker, performance-optimizer) by telling Claude which skill to invoke at each stage. The blog-manager-sop is a static reference doc, not invoked. Trigger this skill aggressively for ANYTHING related to building a competitor comparison content cluster. This is the master skill, so do NOT invoke individual cluster skills directly when
rohitabrahamgeorge/seo-content-team · ★ 0 · AI & Automation · score 72

Install: claude install-skill rohitabrahamgeorge/seo-content-team

# Cluster Orchestrator ## Overview This is the master orchestrator for a hub-and-spoke competitor-comparison content system. It is modeled on PostHog's public Mixpanel comparison cluster (14 URLs, 1 pillar, 6 spoke types, all bidirectionally linked) which has been reverse-engineered into a reusable system. **Your job as the orchestrator is NOT to write content yourself.** Your job is to: 1. Confirm `product-context.md` exists and is filled (see Step 0) 2. Capture the cluster scope from the user 3. Set up the working folder and persistence 4. Invoke each downstream skill in the correct order 5. Track state across runs so the system is resumable 6. Deliver the final cluster as a coherent package The downstream skills are: - `cluster-planner`: does SERP, PAA, and competitor analysis; outputs the cluster plan - `cluster-writer`: writes one post at a time using PostHog templates - `cluster-visual-designer`: generates 2 visual assets per post - `cluster-quality-checker`: audits each post against a 25-point checklist - `cluster-link-validator`: verifies the link topology is bidirectional - `cluster-performance-tracker`: runs every 15 days against GSC + GA + Bing AI Performance ## Workflow ### Step 0: Load product context Every skill in the chain reads `product-context.md`, the filled file at the root of the working folder (next to `clusters/`). It is the single source of truth for product name, first-mention rule, website, docs URL, product areas, proof points, migration help