xiaohongshu-ops-skill_skill

This skill helps you automate Xiaohongshu operations from topic research to post-recovery, delivering reusable templates and case presets for scalable growth.

865

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill xiangyu-cas/xiaohongshu-ops-skill --skill xiaohongshu-ops-skill

  • README.md3.2 KB
  • SKILL.md7.1 KB

Overview

This skill provides an end-to-end Xiaohongshu (Little Red Book) operations framework for positioning, topic research, content production, publish execution, and post-incident recovery. It packages a reusable, platform-aligned SOP with templates and a ready-to-use “watching dramas with you” case preset. The workflow prioritizes low-risk browser automation, evidence snapshots, and iterative evaluation for repeatable performance.

How this skill works

The skill inspects platform signals, competitor posts, and comment-level debate to generate structured publishable notes: cover image plan, title, body, topics, and interaction hooks. It runs a controlled browser profile, takes key snapshots, retries failed steps once, and preserves recoverable outputs while switching to safer paths when needed. A Viral Copy flow converts target post URLs into high-fidelity, non-infringing publish drafts.

When to use it

  • Launching or re-aligning a Xiaohongshu account (persona, pillars, tone)
  • Generating a candidate topic list with evidence-backed controversy points
  • Creating publish-ready notes from high-performing examples (Viral Copy)
  • Executing publish checks and safe automated posting preparation
  • Rapid post-mortem and recovery after failed automation or unexpected platform events

Best practices

  • Always load the Xiaohongshu persona file first to keep voice and reply style consistent
  • Use the built-in browser profile for all automation; switch only after verified failure
  • Produce SOP-like outputs (templates + steps) rather than one-off long reports
  • Keep short, conversational copy with clear interaction CTAs to invite comments
  • Capture a snapshot at key steps for debugging and post-incident auditing
  • Stop at the visible publish page and confirm before final release; send screenshots for human approval when required

Example use cases

  • Set up a new genre account: define target user, three content pillars, key phrases and red lines
  • Run topic discovery: collect top 10–20 comparable high-interaction posts and extract hooks
  • Viral Copy: feed a hit post URL and receive a publish-ready draft (cover, title, body, topics)
  • Publish rehearsal: perform pre-publish checks, snapshots, and assembly of assets for manual review
  • Crisis recovery: retry once, then reroute to safer path and produce a compact incident report for manual intervention

FAQ

No. The workflow stops at the visible publish page by default and recommends human approval or explicit permission to click publish.

How does Viral Copy avoid plagiarism?

It reproduces structural and stylistic elements—cover hierarchy, title rhythm, interaction mechanics—while rewriting content and avoiding verbatim copying and asset reuse to minimize infringement risk.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
xiaohongshu-ops-skill skill by xiangyu-cas/xiaohongshu-ops-skill | VeilStrat