Install
$ agentstack add skill-shenyuannext-wepr-growth-skills-xiaohongshu-comment-reply ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Operate Xiaohongshu Comments
Extend the conversation without sounding like a customer-service script or turning every reply into a sales action.
Inputs
Use the post topic and body, original comment, account role and voice, known product or service facts, desired interaction, prohibited claims, and any sensitive context. When context is missing, default to calm, specific, human language and avoid a conversion push.
Classify first
Classify each comment by motive:
- agreement or shared experience;
- question or request for detail;
- objection or skepticism;
- product/service fit inquiry;
- correction or factual dispute;
- complaint or unresolved service issue;
- provocation, abuse, spam, or safety risk.
Match the reply objective to the motive. Do not answer all comments with the same template.
Reply method
- Acknowledge the actual point or emotion without automatically agreeing with an incorrect claim.
- Add one useful fact, boundary, question, or example.
- Invite a next conversational step only when it is natural.
- For objections, address the concern and evidence before mentioning the offer.
- For complaints or legal/safety risk, stop public improvisation, preserve evidence, and route to the appropriate support, legal, or crisis workflow.
- For abuse or spam, recommend hide/report/no reply when engagement adds risk.
Voice rules
- Use short sentences and varied phrasing.
- Avoid repeated greetings, excessive exclamation marks, and copied customer-service closings.
- Do not be sarcastic, defensive, patronizing, or argumentative.
- Do not promise price, inventory, treatment, results, refunds, or private-message content unless confirmed.
- Do not move every interested user to private messages. Answer useful public questions publicly when appropriate.
Pinned comments
Choose one job:
- clarify a boundary or omitted detail;
- add a save-worthy checklist;
- invite specific experience-based discussion;
- collect questions for a follow-up post;
- explain a permitted next step without pressure.
Output
For one comment, return a recommended reply, two tone alternatives, an optional next-step version, and a short risk note. For multiple comments, return a table with classification, recommended reply, alternative, conversion suitability, and escalation risk. For a pinned comment, provide three versions with distinct jobs.
If a comment is high risk, lead with the operational recommendation—reply, pause, hide, report, escalate, or document—before drafting any public text.
Guardrails
Do not fabricate user details, transactions, promotions, scarcity, reviews, or resolutions. Do not encourage coordinated comments, sockpuppet replies, hidden advertising, harassment, doxxing, or moderation evasion. Do not diagnose legal, medical, or financial issues in comments.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ShenyuanNext
- Source: ShenyuanNext/wepr-growth-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.