xiaohongshu-auto-posting
Automates the complete Xiaohongshu (XHS / Little Red Book) content operation workflow: pain-point topic collection → style case collection → topic selection → content writing → publishing → performance tracking. Use when user mentions xiaohongshu auto posting, xhs auto post, little red book posting, xiaohongshu post, xiaohongshu auto posting, xiaohongshu content operations, xhs content marketing, post to xiaohongshu, publish on xhs, post on xiaohongshu, xiaohongshu promotion, xiaohongshu operations, xiaohongshu automation, xhs automation, track xhs performance, track xiaohongshu performance, x
npx skills add browser-act/skills --skill xiaohongshu-auto-posting --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Xiaohongshu Auto-Posting (XHS Auto-Posting) > End-to-end Xiaohongshu content operation: topic discovery → style reference → writing → publishing → performance tracking. ## Language All process output to user (progress updates, questions, status notifications) follows the user's language. ## Objective Automate a complete Xiaohongshu content operation cycle for a configured product: discover high-engagement pain-point topics via search, collect writing style references, generate platform-native content aligned with the style fingerprint, publish with user approval, and track post-publish performance metrics. ## Prerequisites - Xiaohongshu creator center (`creator.xiaohongshu.com`) already logged in on a configured stealth browser (browser ID stored in `session_state.json`) - `workspaces/xhs-posting/` workspace (auto-created on first run) ## Pre-execution Checks ### 1. Tool Readiness If browser-act has been confirmed available in the current session → skip this step. Invoke `browser-act` via Skill tool to load usage. If installation or configuration issues arise, follow its guidance to resolve then retry. ### 2. Login Verification Covered in Phase 0.5 — login check is deferred until
- Language
- Objective
- Prerequisites
- Pre-execution Checks
- 1. Tool Readiness
- 2. Login Verification
- 3. Session Lifecycle
- Runtime Workspace
- Quick Start
- Operational Rules
- Phase 0 — Initialization
- 0.1 Tool Check
- 0.2 Session State Load
- 0.4 Account Safety Check
WRONG browser-act --session $SESSION state | grep "Publish" CORRECT browser-act --session $SESSION state > /tmp/s.txt 2>&1 && grep "Publish" /tmp/s.txt browser-act --session $SESSION browser open <browser_id> https://creator.xiaohongshu.com/new/home browser-act --session $SESSION wait stable browser-act --session $SESSION browser open <browser_id> https://creator.xiaohongshu.com/new/home --headed browser-act session close $SESSION
What does the xiaohongshu-auto-posting skill do?
Automates the complete Xiaohongshu (XHS / Little Red Book) content operation workflow: pain-point topic collection → style case collection → topic selection → content writing → publishing → performance tracking. Use when user mentions xiaohongshu auto posting, xhs auto post, little red book posting, xiaohongshu post, xiaohongshu auto posting, xiaohongshu content operations, xhs content marketing, post to xiaohongshu, publish on xhs, post on xiaohongshu, xiaohongshu promotion, xiaohongshu operations, xiaohongshu automation, xhs automation, track xhs performance, track xiaohongshu performance, x
How do I install it?
Run `npx skills add browser-act/skills --skill xiaohongshu-auto-posting --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From browser-act/skills, a repository with 5,160 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.