Purpose
This Skill turns owned content plus reference creator samples into a next-topic radar.
It keeps the creator's own account direction at the center.
Core question:
Which topics are worth doing next because they fit the creator's own content assets, audience, and current goal?
When To Use
Use this Skill when the user says things like:
- I have my own content and reference accounts. What should I write next?
- Turn these past posts and saved samples into next week's topic plan.
- Which reference ideas fit my account?
- Help me plan topics for the next 5 days.
- I need a topic radar, not random inspiration.
Use it for:
- creator topic planning
- Xiaohongshu / RedNote topic planning
- social media content calendars
- owned-content review
- reference-sample analysis
- selecting next topics from a larger pool
Do not use it for:
- automatic publishing
- platform scraping
- copying another creator's title or post
- guaranteed follower growth
- guaranteed viral content
- full account consulting
- private account analytics unless the user provides the data
Inputs
Accept any of these:
- owned content titles, summaries, or links
- past performance notes provided by the user
- reference creator samples provided by the user
- target platform
- account goal
- target audience
- planning time range
- topics to avoid
- publishing capacity
If the user provides only reference samples, say the output is a first-pass topic pool and ask for owned content next time.
Workflow
- Read
references/reference-safety-rules.md. - Separate owned-content signals from reference signals.
- Identify the creator's likely content mainline.
- Read
references/topic-priority-rules.md. - Generate 10-20 topic candidates.
- Pick 3-5 priority topics.
- Mark topics to avoid for now.
- Add platform-fit notes.
- End with next actions.
Output Contract
Use this structure by default:
## 1. Planning Scope
- Platform:
- Time range:
- Goal:
## 2. Owned-Content Signals
## 3. Reference Signals
## 4. Topic Candidates
| Topic | Source | Account Fit | Priority | Next Action |
| --- | --- | --- | --- | --- |
## 5. Priority Topics
1.
2.
3.
## 6. Topics To Avoid For Now
## 7. Platform Fit
## 8. Next Actions
## 9. Boundaries
Quality Bar
- Every priority topic must connect to the creator's own direction.
- Reference samples can provide signals, not copy paths.
- Do not choose topics only because they look popular.
- If a topic is high-interest but low-fit, mark it as a test or avoid.
- Do not promise traffic, follower growth, or viral outcomes.
Tone
Be concrete and operational. The user should leave with a short list of topics and a clear next action for each.
Write in Chinese unless the user asks otherwise.
Public Boundary
Keep examples generic. Do not include private account data, internal thread IDs, unpublished client details, or private file paths.