agentleFS
glideaglidea/supersearch-skills/skills/xiaohongshu-search/SKILL.md

xiaohongshu-search

Skill4 starsChanged 4 months agoMITView on GitHub

Search Xiaohongshu for purchase decisions, life experience, product feedback, tutorials, trends, and firsthand Chinese community discussions using the user's existing browser session. Return source-post links.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search the user's question on Xiaohongshu.

    line 12
  2. Distinctive:

    Do not call undocumented private search APIs or copy browser credentials into scripts or environment variables.

    line 22
  3. Distinctive:

    Use the browser page's own login session and search capability.

    line 23
  4. Distinctive:

    Follow the browser skill's confirmation flow for CAPTCHAs.

    line 24
  5. Distinctive:

    Use absolute local paths for covers and link each image to its source post:

    line 35
  6. Distinctive:

    Do not embed Xiaohongshu CDN image URLs directly.

    line 41

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Xiaohongshu Search

Search workflow

  1. Load and follow $browser:control-in-app-browser, selecting a browser for https://www.xiaohongshu.com/.
  2. Reuse an existing Xiaohongshu tab when possible, otherwise open one. Do not read or export cookies, Local Storage, or other login credentials.
  3. Search the user's question on Xiaohongshu. Add one or two natural Chinese queries when useful. Do not enumerate query variants in bulk.
  4. Open filters and select most-liked sorting. If unavailable or unsuccessful, continue with comprehensive sorting and state the actual mode.
  5. Extract the title, author, publication time, engagement count, and actual source-post URL. Use only fields and links present in the current page DOM.
  6. Select three to five highly liked, relevant, representative notes. Open the post when its position or experience matters. Read comments only when they are necessary to answer the question.
  7. By default, save local covers for the one to three most relevant notes. If page covers cannot be saved reliably, capture the note's cover area. Skip cover generation when the user requests no covers or text-only results.
  8. Merge duplicate content and distinguish personal experience, marketing, and verifiable facts. Do not treat like counts as evidence of correctness.
  9. Close intermediate tabs when finished. If the login session has expired, ask the user to log in through the selected browser and continue.

Interface constraints

  • Do not call undocumented private search APIs or copy browser credentials into scripts or environment variables.
  • Use the browser page's own login session and search capability.
  • Follow the browser skill's confirmation flow for CAPTCHAs. Do not bypass them.

Output format

Return:

  • search_executed: whether a real search completed.
  • sort: the sort mode actually used.
  • summary: a concise conclusion based on search results.
  • results: representative notes containing title, author, published_at, engagement, url, cover_path, and note. Omit cover_path when covers are disabled.

Use absolute local paths for covers and link each image to its source post:

[![Note title](/absolute/path/cover.jpg)](https://www.xiaohongshu.com/explore/123)

Do not embed Xiaohongshu CDN image URLs directly.

Cite only Xiaohongshu links actually opened by the browser or present in search results. When search fails, set search_executed to false, state the reason, and do not generate links.

End every response with a ## References section. Keep links next to supported claims and repeat the used links here, deduplicated and comma-separated on one website line:

## References

Xiaohongshu: [result title](https://example.com), [result title](https://example.com)

List only links actually used in the answer. When none exist, write No citable sources. below the heading.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.