cluster-performance-optimizerlisted

# Cluster Performance Optimizer This is the brain of the self-healing loop. It reads two things — the original post content and the latest GSC data — and outputs specific, actionable change recommendations. The blog manager implements minor changes directly. The writer skill handles substantial rewrites. ## When to use this skill Trigger when: - The performance-tracker has produced a fresh 15-day report and posts are flagged as "drop" or "plateau" - The blog manager asks "what should we change on [post] to improve ranking" - A cluster has had 3+ stable cycles and the team wants to push further - An AEO / GEO audit is requested (recommendations specifically for AI-engine citation patterns, separate from Google ranking) - A competitor moved (new feature, repositioning, ranking shift) and the cluster needs a defensive update Required inputs: - The latest performance-tracker report (`clusters/[cluster]/monthly-reports/[YYYY-MM-DD].md`) - The cluster's published posts (`clusters/[cluster]/posts/*.md`) - The cluster Google Sheet (read-only) - `product-context.md` (the filled file at the working-folder root, next to `clusters/`), to make sure recommendations don't introduce invented features - The PostHog template audit (`skills/cluster-writer/references/posthog-template-audit.md`) — for structural recommendations If the performance-tracker hasn't run recently, halt and ask for a fresh check first. Optimizer recommendations are only as good as the data behind them. ## What the