anysite-content-analytics
Track and analyze content performance across Instagram, YouTube, LinkedIn, Twitter/X, and Reddit using anysite MCP server. Measure engagement metrics, analyze post effectiveness, benchmark content strategy, identify top-performing content, and optimize posting strategies. Use when users need to measure content ROI, optimize social strategy, identify viral content patterns, or analyze content engagement across platforms.
What this skill does
# anysite Content Analytics
Measure and optimize content performance across social platforms using anysite MCP. Track engagement, identify top performers, and refine your content strategy.
## Overview
- **Track post performance** across Instagram, YouTube, LinkedIn, Twitter/X
- **Analyze engagement metrics** (likes, comments, shares, views)
- **Identify top content** and viral patterns
- **Benchmark against competitors** for strategy insights
- **Optimize posting strategy** based on data
**Coverage**: 80% - Strong for Instagram, YouTube, LinkedIn, Twitter, Reddit
## Supported Platforms
- ✅ **Instagram**: Posts, Reels, likes, comments, engagement rates
- ✅ **YouTube**: Videos, views, likes, comments, watch time indicators
- ✅ **LinkedIn**: Posts, articles, reactions, comments, shares
- ✅ **Twitter/X**: Tweets, retweets, likes, replies
- ✅ **Reddit**: Posts, upvotes, comments, awards
## v2 Tool Interface
All data fetching uses the anysite MCP v2 universal meta-tools:
- **`execute(source, category, endpoint, params)`** - Fetch data from any source. Returns first page + `cache_key`.
- **`get_page(cache_key, offset, limit)`** - Load more items from a previous execute() when `next_offset` is returned.
- **`query_cache(cache_key, conditions?, sort_by?, aggregate?, group_by?)`** - Filter, sort, and aggregate cached data without new API calls.
- **`export_data(cache_key, format)`** - Export full dataset as CSV, JSON, or JSONL. Returns a download URL.
### Error Handling
v2 responses may include `llm_hint` fields with guidance on how to resolve errors. Common patterns:
- **412**: Entity not found - verify the identifier (username, URN, URL).
- **422**: Invalid parameter format - check URN prefix format or param types.
- Always check `llm_hint` in error responses for specific resolution steps.
## Quick Start
**Step 1: Collect Content Data**
Platform-specific:
- Instagram: `execute("instagram", "user", "user_posts", {"user": "username", "count": 50})`
- LinkedIn: `execute("linkedin", "user", "user_posts", {"urn": "fsd_profile:ACoAAA...", "count": 50})`
- Twitter: `execute("twitter", "user", "user_posts", {"user": "username", "count": 100})`
- YouTube: `execute("youtube", "channel", "channel_videos", {"channel": "channel_id", "count": 30})`
**Step 2: Analyze Engagement**
Use `query_cache()` on the returned `cache_key` to analyze without re-fetching:
```
query_cache(cache_key, sort_by="likes desc", aggregate="avg:likes,comments")
```
Calculate metrics:
- Engagement rate: (likes + comments + shares) / followers
- Best performing content: Top 10% by engagement
- Content types: Video vs. image vs. text
- Posting frequency: Posts per week
**Step 3: Identify Patterns**
Look for:
- Best posting times (day of week, time)
- Top-performing topics/themes
- Optimal content length
- High-engagement formats
**Step 4: Optimize Strategy**
Based on findings:
- Double down on top content types
- Post more during peak engagement times
- Replicate successful topics
- Adjust content mix
**Step 5: Export Results**
```
export_data(cache_key, "csv")
```
Returns a download URL for the full dataset.
## Common Workflows
### Workflow 1: Instagram Content Audit
**Steps**:
1. **Get All Posts**
```
execute("instagram", "user", "user_posts", {"user": "username", "count": 100})
→ returns cache_key + first page of results
```
If more posts exist (response includes `next_offset`):
```
get_page(cache_key, offset=next_offset, limit=50)
```
2. **Calculate Metrics**
```
For each post:
- Engagement rate = (likes + comments) / follower_count
- Engagement per hour = engagement / hours_since_posted
- Content type (Reel, carousel, single image, video)
```
Use `query_cache` to sort and filter:
```
query_cache(cache_key, sort_by="likes desc", aggregate="avg:likes,comments")
```
3. **Identify Top Performers**
```
query_cache(cache_key, sort_by="likes desc")
Top 10%: Analyze for common patterns
- Topics/themes
- Visual style
- Caption style and length
- Hashtag strategy
```
4. **Analyze Content Mix**
```
query_cache(cache_key, group_by="type", aggregate="count:id,avg:likes,avg:comments")
Results show:
- Reels: X% of posts, Y% of engagement
- Carousels: X% of posts, Y% of engagement
- Single images: X% of posts, Y% of engagement
```
5. **Benchmark Against Competitors**
```
For each competitor:
execute("instagram", "user", "user_posts", {"user": "competitor", "count": 50})
Compare:
- Posting frequency
- Engagement rates
- Content types
- Top themes
```
6. **Export Results**
```
export_data(cache_key, "csv")
```
**Expected Output**:
- Content performance report
- Top 10 performing posts
- Content type effectiveness
- Posting frequency analysis
- Competitive benchmark
### Workflow 2: LinkedIn Content Strategy Analysis
**Steps**:
1. **Collect Post History**
```
execute("linkedin", "user", "user_posts", {"urn": "fsd_profile:ACoAAA...", "count": 100})
→ returns cache_key + first page
```
For company page posts:
```
execute("linkedin", "company", "company_posts", {"urn": {"type": "company", "value": "1441"}, "count": 100})
```
Use `get_page(cache_key, offset, limit)` if more posts exist.
2. **Categorize Content**
```
Group by type:
- Text-only posts
- Image posts
- Video posts
- Article shares
- LinkedIn articles
- Polls
```
3. **Analyze Engagement by Type**
```
query_cache(cache_key, aggregate="avg:comment_count,avg:share_count", group_by="type")
For each content type:
- Average reactions
- Average comments
- Average shares
- Engagement rate
```
4. **Topic Analysis**
```
Extract themes from top posts:
- Industry insights
- Personal stories
- How-to/educational
- Company news
- Thought leadership
```
5. **Posting Timing Analysis**
```
Group posts by:
- Day of week
- Time of day
Calculate average engagement for each group
```
**Expected Output**:
- Best content types for engagement
- Top topics by engagement
- Optimal posting times
- Content frequency recommendations
### Workflow 3: YouTube Channel Performance Analysis
**Steps**:
1. **Get Channel Videos**
```
execute("youtube", "channel", "channel_videos", {"channel": "channel_id", "count": 50})
→ returns cache_key + first page
```
Use `get_page(cache_key, offset, limit)` for additional videos.
2. **Analyze Each Video**
```
For each video:
execute("youtube", "video", "video", {"video": "video_id"})
Metrics:
- Views
- Likes/dislikes
- Comments
- View velocity (views per day since upload)
```
3. **Identify Patterns**
```
query_cache(cache_key, sort_by="views desc")
Analyze top 20% by views:
- Video length
- Titles (keywords, style)
- Thumbnail patterns
- Topics/themes
- Upload timing
```
4. **Engagement Analysis**
```
Check comments:
execute("youtube", "video", "video_comments", {"video": "video_id", "count": 100})
Analyze:
- Comment quality
- Questions asked
- Sentiment
- Engagement timing
```
5. **Content Mix Optimization**
```
Compare:
- Long-form (>10 min) vs short (<5 min)
- Tutorial vs entertainment vs review
- Series vs one-offs
```
**Expected Output**:
- Video performance rankings
- Optimal video length
- Best topics and formats
- Title and thumbnail insights
- Upload strategy recommendations
## MCP Tools Reference (v2)
### Instagram
- `execute("instagram", "user", "user_posts", {"user": username, "count": N})` - Get posts with engagement
- `execute("instagram", "post", "post", {"post": post_id})` - Get detailed post metrics
- `execute("instagram", "post", "post_likes", {"post": post_id, "count": N})` - Analyze likers
- `execute("instagram", "post", "post_comments", {"post": post_id, "count": N})` - Get comments
### LinkedIn
- `execute("linkedin", "user", "user_posts", {"urn": "fsd_profile:ACoAAA...", "count": N})` - Get user post history
- `execute("linkedin", "company", "company_posts", {"urn": {"type": "company", "value": "ID"}, "count": N})` - Company page posts
### Twitter/X
- `execute("twitter", "user", "user_posts", {"user": username, "count": N})` - Get tweets
- `execute("twitter", "Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.