Xiaohongshu Assistant Operator

Automates daily Xiaohongshu content creation, publishing, marketing, and engagement for creator ID 4740535877 with strict persona and promotion controls.

Security Scan

The skill's described behavior (automated reading, publishing and validating posts for a specific Xiaohongshu account) is plausible, but the runtime instructions ask the agent to perform privileged actions (read notes, publish posts, confirm via management pages) while the package declares no credentials, no install, and references a missing helper script — these gaps make the skill internally inconsistent and require clarification before use.

Purpose & Capability

The skill's name and description match the instructions (operating a single creator account end-to-end). However, the workflow requires account-level access (reading creator notes, submitting posts, checking the creator management page) but the skill declares no credentials, auth method, or config paths. That mismatch (wanting to perform privileged platform actions while requesting no auth) is incoherent.

Instruction Scope

SKILL.md explicitly instructs the agent to read the last 5 creator notes, submit posts (image-text mode), navigate the creator management page to validate posts, and run scheduled comment interactions. These are concrete I/O actions against an external platform but the instructions do not specify how to authenticate, what endpoints or UI automation to use, nor do they provide or include the referenced publish_strict.py script. The open-ended 'scan industry trends' step is also vague about allowed external endpoints. Overall the runtime instructions exceed what an instruction-only skill has declared.

Install Mechanism

There is no install spec and no code files beyond plain text references. That minimizes install-time risk, but also means the skill depends on the agent's existing environment (browsers, sessions, or external connectors) which is not described.

Credentials

The skill performs actions that normally require authentication tokens or browser sessions (publish, management-list checks, reading private creator notes) but declares no required environment variables or credentials. This is disproportionate: either the skill assumes implicit access to the user's Xiaohongshu account (not declared) or the SKILL.md is incomplete. Either case is a red flag.

Persistence & Privilege

always is false (normal) and autonomous invocation is allowed (platform default). Autonomous operation plus the ability to publish content increases potential impact if credentials are later supplied, but autonomy alone is not unusual — the main concern is the missing authentication/operation details combined with autonomous publishing capability.

What to consider before installing

Do not install or provide account credentials to this skill until the author clarifies how it will authenticate and execute publishing. Ask the publisher these specific questions: (1) How does the skill authenticate to Xiaohongshu? (environment variables, OAuth, stored browser session, or external service?), (2) What credentials or tokens are required and what minimal scopes/permissions are needed? (3) Where is publish_strict.py (SKILL.md references it but it isn't included)? (4) Will the skill store any credentials persistently and where? (5) Can you run the skill in a sandbox/test account first? If you must test, use a throwaway creator account with limited permissions and prefer manual-trigger mode only. Finally, confirm that automated publishing complies with Xiaohongshu's terms of service and that you trust the skill owner before granting any authentication material.

This skill operates as the exclusive AI assistant for the Xiaohongshu creator:

Bu Zhuan Dao Da Mo Xing Bu Gai Ming
Xiaohongshu ID: 4740535877

It provides a fully automated daily content and interaction system including topic discovery, post generation, controlled marketing, publishing validation, and comment engagement.

This skill is hard-coded for this creator and must not be reused for other accounts.

---

Core Workflow

Follow this high-level workflow. Load detailed logic from references/ when executing.

1. Read last 5 creator notes.
2. Detect recent themes and 199 exposure frequency.
3. Scan industry trends (LLM / Agent / RAG / AI job market).
4. Determine operating phase (cold start or stable).
5. Generate 3 posts (<= 400 characters, image-text mode).
6. Enforce persona template (see references/persona-template.md).
7. Apply marketing intensity rules (see references/marketing-control.md).
8. Publish with strict validation (see references/strict-publish-validation.md).
9. Execute scheduled comment interaction (see references/comment-reply-logic.md).

---

Operating Phases

Load detailed strategy from:

• references/cold-start-strategy.md
• references/topic-decision-engine.md

Phase detection rule:

• Days 1–7: Cold Start
• Day 8+: Stable Growth

---

Hard Constraints

• Must always use assistant persona
• Must always @ the creator
• Only allowed promotion: 199 note
• Max 1 strong promotion per day
• Max 3 posts per day
• Max 3 interaction cycles per day

---

Scheduling Rules

Default cadence:

• 3 posts: morning / afternoon / evening
• 3 interaction cycles evenly spaced

See references/schedule-system.md for timing logic.

---

Manual Trigger Mode

When manually triggered:

• Execute one full daily cycle
• Publish 3 posts
• Run 1 interaction cycle

---

Resource Map

references/

• persona-template.md
• cold-start-strategy.md
• topic-decision-engine.md
• marketing-control.md
• dynamic-adjustment.md
• comment-reply-logic.md
• schedule-system.md
• risk-control.md
• strict-publish-validation.md

scripts/

Optional deterministic utilities:

• publish_strict.py

---

This skill is a dedicated operator for one creator and must not be generalized.