What problem does it solve? Legacy requests invoking the deprecated 'content creator' skill need to reach the correct specialist skill instead of failing or being handled by an outdated monolithic workflow. ## Core Features & Use Cases - Intent-Based Routing: Detects whether a user wants writing, SEO, or brand voice work (routes to content-production) versus planning, topic clusters, or content calendars (routes to content-strategy). - Proactive Triggers: Recognizes phrases like 'content creator', 'content plan', or 'what should I write' and redirects accordingly. - Reference Library: Ships analytics guides, brand guidelines, content frameworks, and social media optimization references inherited from the original skill. - Use Case: A user asks to 'write a blog post' using the old content-creator name; the skill identifies the intent and hands the request to content-production, which owns the drafting and SEO pipeline. ## Quick Start Ask the content creator skill to write a blog post and it will route your request to the content-production specialist.