xhs-access-kit

xhs-access-kit is a work-in-progress toolkit for making a repaired XiaoHongShu access workflow easier to reuse.

It is being shaped around a real repair journey where:

• publish worked
• some reads worked
• self/profile/feed reads failed
• the final winning fix was a timing/hydration fix, not a big parser rewrite

What this repo is for

This repo is intended to grow into a practical package for:

1. deployment guidance for an XHS access stack based on xiaohongshu-mcp
2. rollback-safe debugging and repair workflow
3. patch notes and compatibility guidance
4. an OpenClaw skill wrapper for operational use

What this repo is not yet

Right now, this is not yet:

• a polished public release
• a maintained fork of upstream xiaohongshu-mcp
• a guarantee of broad platform/version compatibility

It is currently a structured local repo that is being prepared for publication.

Current contents

• docs/xhs-mcp-deploy-debug-playbook-v1.md — main XHS deployment/debug playbook
• docs/PATCH-CHRONOLOGY.md — what we tried, what mattered, what solved it
• docs/LESSONS-LEARNED.md — reusable lessons from the repair
• docs/VERIFYING-THE-FIX.md — minimal regression checklist
• docs/COMPATIBILITY-AND-PACKAGING.md — packaging options and tradeoffs
• docs/PUBLICATION-PLAN.md — staged publication path
• docs/UPSTREAM-BASELINE.md — known tested baseline and patch lineage
• skill/xhs-access-kit/ — early OpenClaw skill skeleton

Suggested reading order

1. docs/INDEX.md
2. docs/xhs-mcp-deploy-debug-playbook-v1.md
3. docs/PATCH-CHRONOLOGY.md
4. docs/LESSONS-LEARNED.md
5. docs/COMPATIBILITY-AND-PACKAGING.md

Intended publication path

Current recommended path:

1. docs-first
2. then OpenClaw skill wrapper
3. then patch application guidance
4. maintained fork only if real demand justifies it

Tested posture (current)

This repo should currently be read as:

• based on a real local working repair
• conservative about compatibility claims
• still under preparation before public release

Immediate next publish-prep priorities

• clean patch export into patches/
• add installation/usage guide suitable for external readers
• review wording for public-readiness
• decide final publication shape (docs-only vs docs+skill vs hybrid)