cluster-performance-trackerlisted

Tracks the performance of published cluster posts on a 15-day cadence. Reads live blog URLs to confirm published metadata (title, slug, primary keyword, publish date), ingests GSC data from a manually-exported CSV, updates the cluster Google Sheet (the single source of truth), and generates a 15-day monthly report. Use this skill on the recurring 15-day cadence after a cluster is published, whenever the blog manager runs "the performance check," when GSC data has been freshly downloaded and dropped into the input folder, or when someone asks "how is the [cluster] cluster performing." Trigger on phrases like "run the 15-day check", "update the cluster Google Sheet", "pull GSC data", "performance report for [cluster]", "monthly cluster report", or any handoff from the blog manager that asks for the cadence-based performance update. This skill does not edit content. It tracks what's already published.
rohitabrahamgeorge/seo-content-team · ★ 0 · Data & Documents · score 72

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

# Cluster Performance Tracker This is the 15-day cadence skill. It does not write content, generate visuals, or recommend changes. Its only job is to capture what's actually happening to published cluster posts and update the single source of truth (the cluster Google Sheet). ## When to use this skill Trigger when: - It's been 15 days since the last performance check (or the cluster just published, in which case start the cadence) - The blog manager has freshly exported a GSC CSV and dropped it into the cluster's `gsc-imports/` folder - Someone asks "how is the cluster performing" - A monthly cluster review is happening - The performance-optimizer skill needs fresh data Required inputs: - Cluster name and folder path - A GSC CSV export covering the cluster URLs and the date range since the last check (manual export from search.google.com/search-console) - Edit access to the cluster Google Sheet (Sheets API credentials configured for the orchestrator workspace) - The cluster's `cluster-state.json` to know which posts are actually published If the GSC CSV is missing, halt and ask the blog manager to export and drop it. Do not invent data. ## Why CSV instead of GSC API (for now) The first-version setup uses manual CSV exports because it ships immediately without IT setup. The blog manager exports from GSC every 15 days and saves the file to `clusters/[cluster-name]/gsc-imports/[YYYY-MM-DD].csv`. The skill processes whatever CSV is freshest. When the team adds a service-a