Xiaohongshu Copywriter

专业小红书爆款文案创作与爆款笔记结构仿写，提升内容互动率，支持多平台内容改编与精准标签推荐。

What to consider before installing or using this skill: - Function: This is an instruction-only Xiaohongshu copywriting/template skill — it generates titles, bodies, emoji and tag suggestions and claims Pro features for '仿写' and cross-platform adaptation. That matches what the files contain. - Prompt-injection warning: A scanner detected unicode control characters inside SKILL.md. These can hide instructions or try to alter the agent's behavior. Ask the developer for the original source or inspect the raw files to remove any invisible control characters before use. - API Key inconsistency: The README and SKILL.md mention a Pro API Key and '一键分发' but the skill metadata declares no required env vars. Do NOT provide real API keys or secrets to this skill until the developer clarifies: where is the key stored, which endpoint uses it, and whether the skill will post content on your behalf. Prefer using test keys or sandbox accounts for initial trials. - Data you supply: The skill asks you to paste Xiaohongshu URLs (or presumably content). Avoid pasting private or sensitive data. If you want the skill to analyze a private note, prefer pasting only the text you want analyzed and avoid credentials. - Origin and trust: The source/homepage is unknown. If you need ongoing or networked features (Pro, posting to other platforms), prefer a skill with a known homepage, documented endpoints, or an open-source repo you can review. - Practical steps: (1) Inspect SKILL.md and README for hidden characters and remove them. (2) Ask the author to explain the Pro API flow and precisely what the agent will call/do. (3) Test the free features locally with sample text (no credentials). (4) If you must try Pro features, use a limited test API key and monitor traffic; do not reuse production credentials until you understand the integration. Given the prompt-injection signal and the API-key documentation mismatch, treat this skill as suspicious until the developer provides clear, verifiable details about the Pro API usage and the hidden-control-character issue is resolved.