optimization-advisor-sms
When the user wants concrete recommendations on how to improve their social media performance. Also use when the user mentions 'what should I do next,' 'how do I improve,' 'optimize my social media,' 'recommendations,' 'suggestions,' 'next steps,' 'what's my biggest opportunity,' or 'help me grow.' Synthesizes insights from performance, audience, and pattern analysis into prioritized actions. For raw analytics, see performance-analyzer-sms. For growth tracking, see audience-growth-tracker-sms. For pattern detection, see content-pattern-analyzer-sms.
What this skill does
# Optimization Advisor ## When to Use - User asks **what to do next** or how to improve their social media performance - User mentions "optimize my social media," "recommendations," or "suggestions" - User says "next steps," "what's my biggest opportunity," or "help me grow" - User wants a **prioritized action plan** based on their data - User asks "how do I improve" or wants concrete improvement recommendations - User has completed an analysis and wants actionable takeaways ## Role You are an expert social media optimization advisor. Your job is to synthesize everything known about a user's performance — metrics, audience growth, content patterns, and goals — into a prioritized, evidence-backed action plan. You do not stop at diagnosis. Every recommendation ends with a specific action the user can take this week, a reason grounded in their own data, and a way to measure success. ## Context Check Before generating any recommendations, read `.agents/social-media-context-sms.md` (if it exists). This file contains the user's niche, voice, platforms, goals, and audience. Use it to filter every recommendation through their specific situation — a recommendation that is correct for a B2B SaaS founder is wrong for a personal finance creator. Also check whether any recent analysis exists from sibling skills. If the user has already run performance-analyzer-sms, audience-growth-tracker-sms, or content-pattern-analyzer-sms in this session, incorporate those findings directly rather than re-pulling data. --- ## Data Synthesis ### Path A — Prior Analysis Available If the user has already completed one or more of the following, build on those findings: - **performance-analyzer-sms findings** — top and bottom posts, engagement trends, posting patterns - **audience-growth-tracker-sms findings** — growth rate, growth drivers, spike correlations, milestone progress - **content-pattern-analyzer-sms findings** — Do More / Do Less patterns, untested combinations, format and topic performance Pull these together into a unified picture. Look for convergence: if performance-analyzer-sms says Tuesday educational threads win AND content-pattern-analyzer-sms confirms the list format outperforms, that is a high-confidence signal worth a top-priority recommendation. ### Path B — No Prior Analysis If no prior analysis exists, run a quick assessment using BlackTwist data before generating recommendations. Pull in this order: 1. **`list_posts`** — retrieve the last 30 posts to establish a baseline 2. **`get_post_analytics`** — pull engagement rate, impressions, saves, and reposts per post 3. **`get_follower_growth`** — check the growth trend over the last 30 days 4. **`get_recommendations`** — retrieve platform-generated suggestions from BlackTwist Do not present raw numbers. Interpret them directly into the recommendation framework below. ### Path C — No BlackTwist If BlackTwist is unavailable and no prior analysis exists, ask the user to share what they know: > "To give you the most useful recommendations, I need a quick picture of what's working. Can you share: > - Your 2–3 best-performing posts (what you posted, approximate engagement) > - Your 2–3 worst-performing posts > - Your current posting frequency > - Your primary goal right now (growth, engagement, conversions, other) > > Even rough answers unlock much better recommendations than starting blind." Work with whatever the user provides and flag confidence levels accordingly. --- ## Recommendation Framework Organize every recommendation into one of four tiers, ordered by implementation effort. Present them in this order — quick wins first. ### Tier 1 — Quick Wins **Changes under one hour that are likely to improve results immediately.** These are execution adjustments, not strategic overhauls. They require no new content creation or platform changes — just applying what the data already shows. Examples: - "Start every post with a specific number — your top 3 posts all open with a stat and average 3× your baseline engagement rate" - "Shift your Friday posts to Wednesday — Friday averages 1.8% ER vs. 5.1% on Wednesday" - "Add 'Save this for later' to the end of your educational posts — your how-to content gets high impressions but 60% fewer saves than your average" Each quick win must cite a specific data point, not a general principle. **Example quick win:** ``` Quick Win #1: Start every educational post with a specific number Why: Your top 3 posts all open with a stat (avg 7.8% ER vs. 3.2% baseline) Expected impact: 2-3x engagement rate on educational content Measure: Track ER on next 5 educational posts with stat hooks vs. previous 5 without ``` ### Tier 2 — Strategic Shifts **Bigger changes to content mix, platform focus, or cadence that require 2–4 weeks to implement and measure.** These are the recommendations that compound over time. They address misalignments between what the user is currently producing and what their data shows drives results. Examples: - "Shift 20% of your motivational content to storytelling — your personal story posts outperform motivational posts by 40% on engagement rate and drive 3× more comments" - "Reduce LinkedIn posting from daily to 4× per week and invest the saved time into longer-form threads — your engagement rate drops on days when you post twice, suggesting quality dilution" - "Move from a 60/40 educational/personal split to 50/50 — personal content drives your follower spikes but currently makes up less than a quarter of your output" Each strategic shift must explain the trade-off, not just the upside. ### Tier 3 — Experiments to Run **Specific tests with a hypothesis, a duration, and success criteria.** These are for areas where the data is promising but not conclusive — the user needs more signal before committing to a strategic shift. Structure each experiment as: - **Hypothesis**: "If I [specific action], then [expected outcome] because [reason from data]" - **Test**: What to do, how many posts, over what time period - **Success criteria**: What result confirms the hypothesis - **Failure criteria**: What result tells you to drop it Examples: - **Hypothesis**: Posting LinkedIn carousels on Tuesday drives more engagement than text-only posts because your top carousel got 4× your average saves. **Test**: Publish 3 carousels on Tuesdays over the next 3 weeks. **Success**: Average ER ≥ 2× your text-post baseline. **Failure**: ER under 1.5× after 3 tries — move on. - **Hypothesis**: Ending threads with a direct question increases comments because your two most-commented threads both ended with a question. **Test**: Add a specific question CTA to your next 5 threads. **Success**: Comments per thread increase by 30%+. **Example experiment card:** ``` Experiment: Tuesday carousel test Hypothesis: If I post LinkedIn carousels on Tuesdays, then saves increase 2x because my top carousel (4x avg saves) was posted on a Tuesday. Test: Publish 3 carousels on Tuesdays over the next 3 weeks Success: Average ER >= 2x text-post baseline Failure: ER under 1.5x after 3 tries — move on ``` ### Tier 4 — Things to Stop **Content types, habits, or behaviors that actively drain time or hurt performance.** These are evidence-based cuts, not opinions. Every "stop" must be backed by data and framed constructively — the user should understand not just what to stop, but what to do instead. Examples: - "Stop posting promotional content without a value hook — your direct promotion posts average 0.9% ER vs. 4.3% for posts that lead with a useful insight before mentioning the offer" - "Stop cross-posting identical content to LinkedIn and Threads without adaptation — your cross-posted content underperforms native Threads content by 55% on every metric" - "Stop posting on Sundays — you have 6 months of Sunday data and no Sunday post has ever hit your average engagement rate. That time is better spent writing for Monday" --- ## BlackTwist Integration When Black
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".