← ClaudeAtlas

content-pattern-intelligencelisted

Analyze top-performing posts across three performance lenses — engagement, impressions, and engagement rate — to identify content patterns and give the user specific hypotheses to test in their next posts. Use this skill whenever the user asks things like "what's working in my content", "what should I post more of", "why are some posts doing better", "what patterns do you see", "give me content ideas based on my best posts", "what content works best for [client]", "analyze my top posts", or "what should I try next month". Also activate when the user wants to understand performance beyond just numbers — when they're asking for creative direction, not just a report. Always use this skill instead of a generic performance summary when the user's goal is to improve future content.
Planable/smm-skills · ★ 1 · AI & Automation · score 65
Install: claude install-skill Planable/smm-skills
# Content pattern intelligence Look at what's actually working — then tell the user why, and what to try next. This skill analyzes top posts across three performance lenses, finds patterns in the content itself (format, hook, topic, tone, structure), and translates them into specific, testable hypotheses for future posts. **This is not a performance report.** It's a content brief grounded in data. --- ## Step 0: Detect input mode **Mode A — Planable connector** User has Planable connected and wants to pull live post data. **Mode B — CSV upload** User has uploaded a CSV export with post-level data (text, date, platform, metrics). **How to detect:** - File uploaded → Mode B - Mentions "CSV", "export", "file", "spreadsheet" → Mode B - Mentions workspace name, client, or Planable → Mode A - Unclear → ask: "Do you have a CSV with your post data, or should I pull it from Planable?" --- ## Mode A: Planable connector ### Step 1: Gather inputs - **Workspace / client** — which workspace to analyze - **Platform(s)** — default to all; narrow if requested - **Date range** — default to last 60–90 days (needs enough posts to find patterns; warn if fewer than 15 posts available) ### Step 2: Fetch data — with Instagram-safe refresh logic Instagram metrics sync is async and slow. Always follow this sequence to avoid timeouts. **Always call `get_post_metrics` with exactly one `pageId` per request. Multi-page calls compound timeouts — never bundle multiple pages into a single call