Fetches xiaohongshu-images from iamzifei/xiaohongshu-images-skill and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/xiaohongshu-images
Restart Cursor to activate xiaohongshu-images. Access via /xiaohongshu-images in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
This skill transforms markdown, HTML, or text content into beautifully styled HTML pages with AI-generated cover images, then captures them as sequential screenshots at 3:4 ratio for Xiaohongshu posting.
Overview
The skill performs the following workflow:
Accept Content: Receives markdown, HTML, or txt format content from the user
Load Prompt Template: Reads the prompt template from prompts/default.md in this skill's directory
Determine Output Account: Determines which account folder to use (see Account Folder Resolution below)
Generate Cover Image: Uses /baoyu-cover-image skill to generate a cover image based on the article content
Generate HTML: Creates a beautifully styled HTML page following the prompt template specifications
Save Output: Saves the HTML to ~/Dev/obsidian/{account_folder}/articles/<date-title>/xhs-preview.html
Capture Screenshots: Takes sequential 3:4 ratio screenshots of the entire page without cutting text
Account Folder Resolution
The skill determines the output account folder using the following priority:
Priority 1: Explicit --account Parameter
If the user specifies --account, use the corresponding folder:
If no --account is specified, try to infer from the input file path:
Input: ~/Dev/obsidian/12_妈妈在读/articles/2026-01-20-xxx/index.md
→ Output to: ~/Dev/obsidian/12_妈妈在读/articles/2026-01-20-xxx/
Input: ~/Dev/obsidian/10_在悉尼和稀泥/articles/2026-01-20-xxx/index.md
→ Output to: ~/Dev/obsidian/10_在悉尼和稀泥/articles/2026-01-20-xxx/
Priority 3: Fallback to Template Mapping
If the account cannot be determined from the path (e.g., raw content input), use template-based mapping:
Template
Account Folder
default
10_在悉尼和稀泥
mom-reading-club
12_妈妈在读
Account Folder Mapping Reference
Account
Folder
james-cn
10_在悉尼和稀泥
james-en
11_BuildWithJames
mom-reading-club
12_妈妈在读
Usage
When the user invokes this skill, follow these steps:
Step 1: Identify the Input
The user will provide one of the following:
A file path to a markdown, HTML, or txt file (e.g., /path/to/article.md)
Raw content directly in the conversation
A URL to fetch content from
If the input is unclear, ask the user to provide either a file path, URL, or paste the content directly.
Step 2: Read the Prompt Template
Read the prompt template from this skill's directory:
{{SKILL_DIR}}/prompts/default.md
Use the Read tool to get the prompt template content. This template defines the HTML/CSS styling specifications.
Step 3: Extract Article Title, Date, and Determine Account
From the content, extract:
Title: The main heading (h1) or first significant title in the content
Date: Current date in YYYY-MM-DD format
Account Folder: Determine using the priority rules above (--account → path inference → template mapping)
Create the output folder path as: ~/Dev/obsidian/{account_folder}/articles/<date>-<sanitized-title>/
Replace spaces with hyphens
Remove special characters
Keep the title reasonably short (max 50 characters)
All images go in _attachments/ subfolder
Step 4: Generate Cover Image with baoyu-cover-image Skill
⚠️ COMPLIANCE CHECK: Before generating, ensure the image concept complies with Xiaohongshu community guidelines (Section 11 of the prompt template). The image must:
Be age-appropriate with no revealing clothing or suggestive poses
Avoid political symbols, violence, gambling, smoking, or alcohol abuse
Convey positive, constructive messages
Be culturally sensitive and original
Use the /baoyu-cover-image skill to generate the cover image:
Or if the content is not yet saved, pass the content directly to the skill.
Style Selection:
Let baoyu-cover-image auto-select based on content signals, OR
Specify a style that matches the article tone:
tech - AI, coding, digital topics
warm - Personal stories, emotional content
bold - Controversial, attention-grabbing topics
minimal - Simple, zen-like content
playful - Fun, casual, beginner-friendly content
nature - Wellness, health, organic topics
retro - History, vintage, traditional topics
elegant - Business, professional content (default)
Special: Mom Reading Club Template
When using the mom-reading-club template, override the default cover style with calligraphy & ink-wash illustration (书法水墨风):
/baoyu-cover-image <article>--style minimal --no-title --custom-prompt "Chinese calligraphy and ink-wash illustration style (书法水墨风). Zen-like simplicity with generous white space (留白). Include subtle ink-wash brush strokes as background texture. Minimalist botanical elements (bamboo, plum blossoms, orchids, lotus) when appropriate. Color palette: ink black (#1a1a1a), warm gray (#666666), subtle gold accents (#C9A962), warm off-white background (#F5F3EE). If human figures are included, depict an elegant woman aged 30-45 with a contemplative, refined demeanor. NO TEXT on the cover."
Use --no-title flag since Xiaohongshu covers typically use visual-only images without embedded text.
Move the generated image to the correct location:
baoyu-cover-image saves to imgs/cover.png relative to the article
Move/copy to ~/Dev/obsidian/{account_folder}/articles/<date>-<title>/_attachments/cover-xhs.png
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
