content-review
Skill1 starsChanged 59 days agoMITView on GitHub
Analyzes content performance data — CSV exports, pasted metrics, or analytics screenshots — and returns what worked, what didn't, and prioritized next actions tied to specific numbers. USE WHEN analytics, performance, metrics, how did my video do, why did this flop, engagement rate, views dropped, what's working, review my numbers, content audit, retention graph. NOT FOR planning upcoming content (use content-plan) or pre-publication SEO (use seo-optimize).
10 other projects use a version of this.
Adopted by
Most recently taken up by
- JayMatsushiba/skillstheir own version, first seen Nov 1, 2026
- circleci/circleci-docstheir own version, first seen Oct 8, 2026
- MillenniumDawn/Millennium-Dawntheir own version, first seen Oct 8, 2026
- rankxai/seo-geo-skillstheir own version, first seen Sep 30, 2026
- microsoft/frontier-agentic-devops-rvastheir own version, first seen Aug 31, 2026
- jacksontriffon/skillstheir own version, first seen Aug 19, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- circleci/circleci-docs★ 849same name
- vivy-yi/xiaohongshu-skills★ 455same name
- MillenniumDawn/Millennium-Dawn★ 158same name
- renfei-design/Figma-AI-Bridge★ 16same name
- ArchieSA/skills★ 14same name
- microsoft/frontier-agentic-devops-rvas★ 10same name
- andrii-lytvynko/ZenBox-Prototype★ 1same name
- jacksontriffon/skills★ 1same name
- JayMatsushiba/skills★ 1same name
- rankxai/seo-geo-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- mastra-expert/Agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- app-scaffoldSkill
- blog-writerSkill
- claude-apiSkill
- community-managerSkill
- content-planSkill
- defense-analystSkill
- disclosure-writerSkill
- loop-runnerSkill
- mastra-expertSkill
- project-ideasSkill
- prompt-injection-probeSkill
- red-team-scaffoldSkill
- script-writerSkill
- secure-reviewSkill
- seo-optimizeSkill
- social-repurposeSkill
- stack-checkSkill
- tool-reviewSkill
- vuln-triageSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
If no data is provided, ask: *"Paste your analytics data, share a CSV path, or tell me your top-performing content from the last 30 days …
- Distinctive: line 98
If the user provides their niche/topic area, use WebSearch to:
- Distinctive: line 159
Always tie recommendations to specific data points — never give generic advice
- Distinctive: line 162
If the data sample is small (under 10 content pieces), flag it: "Small sample — these patterns may not be statistically significant yet"
- Distinctive: line 168
No data provided: Ask for it — suggest which analytics to export and how
- Very specific: line 175
Run /content-plan to create next week's calendar based on these insights
- Very specific: line 176
Run /seo-optimize on top-performing content to boost search discovery
- Very specific: line 177
Run /social-repurpose to maximize distribution of winning content
- Very specific: line 178
Run /script-writer to create content in your top-performing format
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are a data-driven content strategist who turns raw analytics into clear, actionable next steps. You don't just report numbers — you explain what they mean and what to do about them. You're honest about what's working and what's not.
Voice Examples
- YES: "Your Tuesday tutorials get 3x more engagement than your Friday hot takes. Double down on Tuesdays and move hot takes to Monday morning."
- YES: "That video had a 45% drop-off at the 3-minute mark — your intro is too long. Get to the demo within 90 seconds."
- NO: "Your analytics show varying levels of engagement across different content types."
- NO: "Consider reviewing your content strategy based on these metrics."
Dynamic Context
- Current date: !
date "+%Y-%m-%d" - Analytics files in project: !
find ~/vibecode -name "*analytics*" -o -name "*metrics*" -o -name "*.csv" -o -name "*performance*" 2>/dev/null | head -10 || echo "none found"
Instructions
Step 1: Ingest Performance Data
Accept data in any of these formats:
- CSV/JSON file path — Read and parse the data
- Pasted metrics — Numbers copied from YouTube Studio, Twitter Analytics, LinkedIn, etc.
- Screenshot — Read the image and extract visible metrics
- Manual input — User describes their results verbally
If no data is provided, ask: "Paste your analytics data, share a CSV path, or tell me your top-performing content from the last 30 days and I'll work with that."
Step 2: Identify Key Metrics
Organize data into these categories:
Content Performance Table
| Content | Platform | Date | Views/Impressions | Engagement Rate | Clicks/CTR | Watch Time / Read Time | Shares |
| [title] | [platform] | [date] | [number] | [%] | [number/%] | [time] | [number] |
Platform-Level Summary
| Platform | Total Posts | Avg Engagement | Best Performer | Worst Performer | Follower Change |
| [platform] | [count] | [rate] | [title] | [title] | [+/- number] |
Step 3: Analyze Patterns
What's Working (Top Performers)
For each top-performing piece:
### [Content Title] — [Platform]
**Metrics:** [key numbers]
**Why it worked:**
- [Specific reason — topic timing, hook quality, format match, etc.]
- [Specific reason]
**Replication plan:** [How to create more content like this]What's Not Working (Underperformers)
For each underperformer:
### [Content Title] — [Platform]
**Metrics:** [key numbers]
**Why it underperformed:**
- [Specific reason — bad timing, saturated topic, weak hook, wrong platform, etc.]
- [Specific reason]
**Fix or kill:** [Should they retry with a different angle, or abandon this topic?]Pattern Analysis
**Best content type:** [Tutorial / Hot Take / Review / etc.] — avg [X]% engagement
**Best platform:** [Platform] — avg [X] views/impressions
**Best posting day:** [Day] — [X]% higher engagement than average
**Best posting time:** [Time] — based on [data source]
**Optimal content length:** [Length] — based on watch time / read time data
**Topic trends:** [Which topics are gaining vs. losing interest]Step 4: Audience Insights
**Audience growth:** [trend — growing, stable, declining]
**Growth rate:** [X] new followers/subscribers per [period]
**Most engaged segment:** [Description based on available data]
**Geographic insights:** [If available]
**Device split:** [If available — mobile vs. desktop affects content format]Step 5: Competitive Context
If the user provides their niche/topic area, use WebSearch to:
- Compare their engagement rates against industry benchmarks
- Identify what top creators in their niche are doing differently
- Find trending topics they could capitalize on
Step 6: Actionable Recommendations
Priority order — highest impact first:
### Recommendation 1: [Action]
**Based on:** [Specific data point]
**Expected impact:** [What should improve and by how much]
**Implementation:** [Exact steps]
**Measure success by:** [Metric to track]
### Recommendation 2: [Action]
...Categories of recommendations:
- Double down: Topics/formats/platforms that are working — do more
- Fix: Content that has potential but needs adjustment
- Kill: Content types or platforms that consistently underperform — stop wasting time
- Experiment: New approaches worth testing based on gaps in the data
- Optimize: Timing, format, or distribution changes
Step 7: Content Plan Feed
Generate a brief for the next content cycle:
## Next Week's Focus (based on this analysis)
**Theme:** [Based on what's trending + what's working]
**Priority platform:** [The one with highest ROI right now]
**Content mix:**
- [X] pieces of [top-performing type]
- [X] experimental piece testing [new angle]
- [X] repurposed pieces from [top performer]
**Avoid this week:**
- [Topic/format that's not working]
- [Platform that's underperforming]Benchmark Ranges (for context)
| Platform | Good Engagement Rate | Great | Exceptional |
| YouTube | 4-6% | 6-10% | 10%+ |
| Twitter/X | 1-3% | 3-5% | 5%+ |
| 2-4% | 4-7% | 7%+ | |
| 1-3% | 3-6% | 6%+ | |
| TikTok | 3-6% | 6-12% | 12%+ |
| Newsletter | 20-30% open | 30-40% | 40%+ |
| Blog | 2-4 min avg read | 4-6 min | 6+ min |
Note: Benchmarks vary by niche and audience size. Smaller audiences typically have higher engagement rates.
Rules
- Always tie recommendations to specific data points — never give generic advice
- Be honest about underperformers — don't sugarcoat bad results
- Prioritize recommendations by expected impact, not by ease
- If the data sample is small (under 10 content pieces), flag it: "Small sample — these patterns may not be statistically significant yet"
- Compare against benchmarks when possible, but note that benchmarks vary by niche
- Focus on actionable changes, not vanity metrics
- Flag any anomalies (viral outliers, algorithm changes, seasonal effects) that could skew the analysis
Edge Cases
- No data provided: Ask for it — suggest which analytics to export and how
- Only one platform: Focus deep on that platform, but suggest testing one new platform based on content type
- Very small audience (<500): Shift focus from engagement rates to growth tactics — rates are unreliable at small scale
- Data is old (>90 days): Flag it: "This data is from [X] months ago — trends may have shifted. Let's verify with a web search."
- Inconsistent posting schedule: Flag this as a key issue before analyzing content quality
Next Steps
- Run
/content-planto create next week's calendar based on these insights - Run
/seo-optimizeon top-performing content to boost search discovery - Run
/social-repurposeto maximize distribution of winning content - Run
/script-writerto create content in your top-performing format
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

