xhs-title-selector
Skill29 starsChanged 7 months agoMITView on GitHub
Xiaohongshu title strategy skill for Chinese creators. Use when Codex needs to pick the right title formula for a topic, draft, or existing Xiaohongshu title; match the content to the right trigger family instead of free-generating titles; produce traceable title options with formula IDs and rationale; and choose the best testing candidates.
In this repository26 other files it gives its agents.
- ai-writing-diagnosisSkill
- benchmark-filterSkill
- book-material-minerSkill
- cc-designSkill
- celf-style-writerSkill
- content-strategy-diagnosisSkill
- deep-writerSkill
- hook-optimizerSkill
- horizontal-vertical-analysisSkill
- learning-builderSkill
- mrbeast-perspectiveSkill
- naval-perspectiveSkill
- opc-case-researchSkill
- paul-graham-perspectiveSkill
- perspective-distillerSkill
- short-video-script-builderSkill
- speech-structure-coachSkill
- spoken-script-polishSkill
- steve-jobs-perspectiveSkill
- video-packaging-diagnosisSkill
- wechat-draft-publisherSkill
- x-article-publisherSkill
- x-content-mentorSkill
- xhs-image-directorSkill
- youmindSkill
- zhang-yiming-perspectiveSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. About 0 are common, 22 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈22
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use this skill to treat Xiaohongshu titles as a matching problem, not a random generation problem.
- Distinctive: line 25
Check whether the topic itself is strong enough to deserve title work.
- Distinctive: line 30
If the topic itself is weak or unclear, say so before generating titles.
- Distinctive: line 38
use the formula catalog instead of pure freeform generation
- Distinctive: line 40
keep titles concise and testable
- Distinctive: line 41
prefer titles that can actually be paid off by the body
- Distinctive: line 60
If the topic is still too fuzzy, read references/workflow.md.
- Distinctive: line 64
Before matching formulas, ask:
- Very specific: line 70
If the topic is weak, recommend $content-strategy-diagnosis instead of pretending title work can rescue it.
- Distinctive: line 74
Use the trigger-family map in references/trigger-families.md.
- Distinctive: line 91
Do not force families that do not fit.
- Distinctive: line 99
keep the formula logic intact
- Distinctive: line 113
Read references/quality-bar.md before finalizing.
- Distinctive: line 117
If the user already has a title:
- Distinctive: line 127
Default to assets/title-pack-template.md.
- Distinctive: line 144
use niche jargon if broader language would widen relevance
- Distinctive: line 151
keep multiple strategic directions alive
- Distinctive: line 153
keep the final recommendation opinionated
- Distinctive: line 158
Read for input-state handling, title-before-content checks, and existing-title optimization.
- Distinctive: line 160
Read for the 12 trigger families and when each should be used.
- Distinctive: line 162
Read for the traceable formula list used in title generation.
- Distinctive: line 164
Read for title quality rules, compression guidance, and failure checks.
- Distinctive: line 166
Use for the standard output shape.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
XHS Title Selector
Overview
Use this skill to treat Xiaohongshu titles as a matching problem, not a random generation problem.
The core job is to:
- identify what the content is really selling in the first glance
- match it to the right trigger family
- generate titles that can be traced back to a formula
- explain why each title fits
This is a title-strategy skill, not a generic copywriting skill.
Quick Start
- First understand the topic, audience, and content goal.
- Check whether the topic itself is strong enough to deserve title work.
- Match the content to 3-6 trigger families.
- Select 5-8 formulas from the catalog instead of free-generating blindly.
- Return title options with formula IDs, rationale, and Top 3 recommendations.
If the topic itself is weak or unclear, say so before generating titles.
Default Contract
Assume the following unless the user says otherwise:
- write in Chinese
- generate Xiaohongshu-oriented titles
- use the formula catalog instead of pure freeform generation
- cover at least 3 distinct trigger families unless the topic is unusually narrow
- keep titles concise and testable
- prefer titles that can actually be paid off by the body
Workflow
Step 1: Understand the Input
The user may provide:
- a topic
- an industry plus topic
- a paragraph or full draft
- a current title that needs diagnosis
Lock these first:
- what the content is about
- who it is for
- what reaction the user wants: click, save, trust, comment, or conversion
If the topic is still too fuzzy, read references/workflow.md.
Step 2: Decide Whether Title Work Should Start Yet
Before matching formulas, ask:
- does the content have a clear promise
- is there enough material to support a stronger title
- is the issue really the title, or is the topic itself weak
If the topic is weak, recommend $content-strategy-diagnosis instead of pretending title work can rescue it.
Step 3: Match Trigger Families
Use the trigger-family map in references/trigger-families.md.
Typical matching logic:
- counterintuitive claim -> cognitive conflict
- hidden knowledge or inside information -> curiosity gap
- warnings, pitfalls, correction -> loss avoidance
- precise audience callout -> identity mirror
- steps, methods, lists -> numeric anchor
- measurable outcome -> outcome promise
- story or personal turnaround -> case reversal
- strong stance or potential debate -> controversy
- specific user state -> scenario or condition
- push to action -> action call
- borrowed credibility -> authority leverage
- comments or self-check desire -> interaction or test
Do not force families that do not fit.
Step 4: Select Formulas
Choose 5-8 formulas from references/formula-catalog.md.
For each formula:
- keep the formula logic intact
- adapt the wording to the user's topic
- label the formula ID
- explain why it fits this content
Step 5: Generate and Rank Titles
Return:
- grouped title options by trigger family
- formula IDs
- one-line rationale
- Top 3 recommendations for immediate testing
Read references/quality-bar.md before finalizing.
Step 6: Handle Existing Titles
If the user already has a title:
- infer which family and formula it is closest to
- diagnose whether the problem is formula choice or execution quality
- provide:
- same-formula improvements
- alternative-family replacements
Output Format
Default to assets/title-pack-template.md.
At minimum, include:
- topic and audience read
- matched trigger families
- title options with formula IDs
- Top 3 recommendation
- brief next-step advice
Hard Rules
Do not:
- free-generate titles without formula attribution
- spoil the whole answer inside the title when suspense is needed
- stuff every option into one trigger family
- use niche jargon if broader language would widen relevance
- promise outcomes the content cannot support
Always:
- identify topic and audience first
- make formula choice explicit
- keep multiple strategic directions alive
- distinguish between wrong formula and weak execution
- keep the final recommendation opinionated
Resource Map
- references/workflow.md
- Read for input-state handling, title-before-content checks, and existing-title optimization.
- references/trigger-families.md
- Read for the 12 trigger families and when each should be used.
- references/formula-catalog.md
- Read for the traceable formula list used in title generation.
- references/quality-bar.md
- Read for title quality rules, compression guidance, and failure checks.
- assets/title-pack-template.md
- Use for the standard output shape.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

