[Anchor-Shi]

Summary

The Grok README only describes installation after marketplace approval, leaving users without clear guidance when ChatCut is absent or they are using grok.com instead of Grok Bot. Add an agent-readable setup guide with English and Chinese starter prompts, reuse of existing connections, and separate marketplace, custom MCP, and repository boundaries.

The guide checks authentication, tools, and skills independently, then defines a small editable-video test with truthful export delivery. It does not claim /goal support, arbitrary Git/ZIP installation, or completed cold-start host acceptance. Runtime files and plugin versions are unchanged.

Validation

• node --test tests/*.test.mjs: 141 passed on Node 24.12.0.
• 11 relative Markdown links, 18 packaged skills, marketplace index, and manifest/header version consistency checked; git diff --check passed.
• Current official Grok Bot app/skill/Team Bot documentation and grok.com connector documentation checked on 2026-10-23.
• Public ChatCut MCP returned the expected unauthenticated 401 and OAuth resource metadata returned 200. These are endpoint checks, not Grok authentication or host acceptance.

Remaining acceptance

Current Grok Bot marketplace install, first OAuth, automatic skill discovery, and the complete first-project flow still need a signed-in Grok Bot session. grok.com verification was blocked at security verification. Historical manual-MCP editing results are not promoted to a current package or marketplace pass.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}