
data-analytics
Use when needing to optimize Xiaohongshu content performance, understanding why posts succeed or fail, making data-driven decisions about content strategy, or tracking account growth metrics
- Installs
- 191
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/vivy-yi/xiaohongshu-skills --skill data-analytics- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads data-analytics automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Data Analytics (数据分析)
Overview
Data analytics is the systematic analysis of Xiaohongshu account and content metrics to understand performance, identify patterns, and make informed decisions that optimize growth and engagement.
When to Use
Use when:
- Content performance is inconsistent
- Unsure what content resonates with audience
- Follower growth has plateaued
- Need to validate content strategy decisions
- Preparing content optimization plans
- Analyzing competitor performance
Do NOT use when:
- Just starting with no content data (wait for 5+ posts)
- Need real-time monitoring during posting (use platform-native analytics)
Core Pattern
Before (guessing without data):
❌ "I think my audience likes fashion content"
❌ "This post should do well because I worked hard on it"
❌ "Let me try this topic and see what happens"
After (data-driven decisions):
✅ "My top 5 posts are all skincare tutorials - audience prefers educational content"
✅ "Posts published at 8pm get 3x more engagement than 2pm"
✅ "Before-and-after format averages 15% engagement vs 8% for other formats"
5 Core Metrics Framework:
- Exposure (浏览量) - Reach and discovery
- Engagement (互动率) - Likes, comments, shares
- Conversion (转化率) - Follows, saves, clicks
- Growth (粉丝增长) - New followers, unfollows
- Audience (用户画像) - Demographics, behavior patterns
Quick Reference
| Metric | What It Measures | Good Benchmark | Analysis Tool |
|---|---|---|---|
| Views/Exposure | Content reach | 500+ for new accounts | Xiaohongshu Creator Center |
| Engagement Rate | (Likes+Comments+Shares)/Views | 8-12% average | Excel / Qiangua |
| Save Rate | Content value | 3-5% is good | Creator Center |
| Follower Growth | Account growth | 5-10% monthly | Creator Center |
| Peak Hours | Best posting time | 7-9pm for most | Qiangua / Huitun |
Implementation
Step 1: Data Collection (Weekly)
Export data from:
-
Xiaohongshu Creator Center (native, free)
- Account overview → Data analysis
- Post performance → Content data
- Audience insights → User profile
-
Qiangua Data (recommended, freemium)
- Account analysis
- Content performance
- Industry benchmarks
Step 2: Build Analysis Spreadsheet
Create Excel/Google Sheets with tabs:
Tab 1: Content Performance
| Date | Title | Views | Likes | Comments | Shares | Saves | Followers | Engagement Rate |
|------|-------|-------|-------|----------|--------|-------|-----------|----------------|
Tab 2: Weekly Summary
| Week | Total Posts | Avg Views | Avg Engagement | New Followers | Top Performing Post |
|------|-------------|-----------|----------------|---------------|-------------------|
Tab 3: Audience Insights
| Date | Age Group | Gender | Location | Active Hours | Top Interests |
|------|------------|--------|----------|---------------|----------------|
Step 3: Analyze Patterns (Monthly)
Content Analysis:
- Which topics perform best? (top 10 posts by engagement)
- Which formats work? (image vs video vs carousel)
- What titles drive clicks? (high CTR vs low CTR)
- When is best posting time? (hour-by-hour breakdown)
Audience Analysis:
- Who are your top followers? (demographics)
- When are they most active? (hour/day patterns)
- What content do they engage with most? (interest analysis)
Step 4: Identify Actionable Insights
Transform data into decisions:
Question → Data → Action:
Q: Why did engagement drop this week?
A: Views stable but engagement rate fell from 10% to 6%
→ Check: Content type shift? Topics changed? Timing different?
→ Action: Return to top-performing content topics next week
Q: Which content brings most followers?
A: Skincare tutorials average 12 new followers per post
→ Action: Create 3 more tutorial posts this month
Q: When should I post for maximum reach?
A: 7-9pm gets 3x more views than 2-5pm
→ Action: Schedule all posts for 7-9pm timeframe
Step 5: Apply Insights to Strategy
Update content strategy based on findings:
- Double down on what works (top performing topics/formats)
- Eliminate what doesn't (bottom 20% performers)
- Test new variations inspired by successful patterns
- Optimize posting schedule based on peak hours
Common Mistakes
| Mistake | Why Happens | Fix |
|---|---|---|
| Analyzing too frequently | Impatience | Weekly data collection, monthly analysis |
| Focusing on vanity metrics | Views are visible | Engagement rate and followers matter more |
| Not acting on insights | Analysis paralysis | Create 3 action items from each analysis |
| Ignoring audience data | Focus on content | User demographics reveal WHY content works |
| Comparing to mega-accounts | Unrealistic benchmarks | Compare to similar-sized accounts in niche |
Real-World Impact
Data-driven optimization results (real examples):
- Account A: Posted randomly → 5x follower growth after implementing data-driven posting schedule
- Account B: Mixed content → 3x engagement increase by focusing on top-performing topic only
- Account C: Generic fashion → 10x save rate by shifting to "budget-friendly" angle based on audience data
Key insight: Accounts using weekly data analysis grow 3-5x faster than those posting blindly.
Related Skills:
- REQUIRED: data-metrics-understanding (understand what each metric means)
- REQUIRED: content-performance-analysis (analyze individual post performance)
- REQUIRED: qiangua-data (tool for advanced analytics)
- traffic-analysis (analyze where traffic comes from)
- user-persona-analysis (understand your audience demographics)
FAQ
What does the data-analytics skill do?
Use when needing to optimize Xiaohongshu content performance, understanding why posts succeed or fail, making data-driven decisions about content strategy, or tracking account growth metrics
How do I install data-analytics?
Run npx skills add https://github.com/vivy-yi/xiaohongshu-skills --skill data-analytics in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/data-analytics/ (personal) or .claude/skills/data-analytics/ (project).
Which AI agents can use data-analytics?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is data-analytics safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains data-analytics?
It is published by vivy-yi in vivy-yi/xiaohongshu-skills. It has 191 recorded installs.
More from vivy-yi/xiaohongshu-skills
short-video-production
vivy-yi/xiaohongshu-skills
Use when creating video content for Xiaohongshu, filming vlogs or tutorials, editing short-form vertical video, or optimizing video for mobile viewing
copywriting-skills
vivy-yi/xiaohongshu-skills
Use when writing Xiaohongshu post content body, creating engaging captions, developing brand voice, or writing product descriptions and recommendations
image-editing
vivy-yi/xiaohongshu-skills
Open the skill to read its SKILL.md instructions.
viral-creation
vivy-yi/xiaohongshu-skills
Open the skill to read its SKILL.md instructions.
traffic-acquisition
vivy-yi/xiaohongshu-skills
Open the skill to read its SKILL.md instructions.
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.