MaxClaw Helper
Disclaimer: Knowledge in this skill is open to everyone, but some content (config, models, channels) applies to MaxClaw users only and may not apply to other OpenClaw deployments.
Language: This skill supports queries in both Chinese and English. Always reply in the same language the user used.
Quick Reference
| Scenario |
Action |
| User asks "how to X" or "is X supported" |
Flow A: query docs → answer with citation |
| Command / tool call fails |
Flow B: classify → query docs → self-assess → escalate |
| Same operation fails ≥ 2 times |
Stop retrying → Flow B |
| Config file or irreversible operation at risk |
Stop → B-3 safety check before any action |
| Root cause unknown, no trusted doc match |
Flow B → escalate to community |
| User instruction ambiguous or conflicts with safety rules |
Clarify before acting |
| Missing permission, dependency, or env var |
Flow B → document and escalate |
| Cannot use web search / deep research tools |
MiniMax Feishu Wiki (§ T-6) |
| Task stopped / input locked / "Task stopped, try a new task" |
MiniMax Feishu Wiki (§ T-4) |
| Moderation blocked / content intercepted |
MiniMax Feishu Wiki (§ T-3) |
| Credits incentive reward not received |
MiniMax Feishu Wiki (§ B-6) |
| OpenClaw stuck restarting / HTTP 404 |
MiniMax Feishu Wiki (§ T-5) |
| Credits depleting fast |
MiniMax Feishu Wiki (§ B-1) |
| Credits exhausted / balance zero |
MiniMax Feishu Wiki (§ B-3) |
| Cron stops after credits run out |
MiniMax Feishu Wiki (§ B-2) |
| Agent vs Open Platform credits not interchangeable |
MiniMax Feishu Wiki (§ B-5) |
| Refund request |
MiniMax Feishu Wiki (§ B-4) |
| How to connect Feishu |
MiniMax Feishu Wiki (§ F-1) |
| Feishu unavailable / connection failed |
MiniMax Feishu Wiki (§ F-3) |
| Feishu pairing fails / stuck restarting |
MiniMax Feishu Wiki (§ F-7) |
| Feishu duplicate replies |
MiniMax Feishu Wiki (§ F-5) |
| Add bot to Feishu group |
MiniMax Feishu Wiki (§ F-8) |
| HTTP 400 / 500 / Internal server error |
MiniMax Feishu Wiki (§ T-1) |
| 413 request too large |
MiniMax Feishu Wiki (§ T-2) |
| Always loading / no response / timeout |
MiniMax Feishu Wiki (§ T-7) |
| Conversation frozen / sudden termination |
MiniMax Feishu Wiki (§ T-8) |
| User hasn't provided chat_id |
MiniMax Feishu Wiki (§ S-1) — collect it first |
| Generated files not found |
MiniMax Feishu Wiki (§ G-8) |
Flow A: Usage Question
- Check Quick Reference first — if the scenario matches a MiniMax Feishu Wiki entry, read that section directly via
feishu-wiki + feishu-doc (see references/trusted-sources.md § 2 for how to read).
- If not in Quick Reference, read
references/trusted-sources.md and query sources in priority order:
- For MaxClaw-specific issues (credits, Feishu, moderation, product): query MiniMax Feishu Wiki first
- For OpenClaw platform/config/CLI issues: query https://docs.openclaw.ai/ via
extract_content_from_websites
- Keywords: feature name, config field name, channel name (e.g. "feishu", "long polling", "webhook")
- Respond based on result:
- [match] Clear doc match → give direct answer, cite source URL; append "MaxClaw users only" if applicable
- [partial] Partial match → answer cautiously; note "based on similar case — verify against actual behavior"
- [no match] No match → inform user, redirect to community (see
references/community-template.md)
Flow B: Runtime Problem
B-1: Classify
| Type |
Key Signals |
| Execution failure |
Non-zero exit, tool error, timeout |
| Knowledge uncertainty |
No doc basis, doc contradicts observed behavior, version mismatch |
| Safety risk |
Config file, irreversible delete, external send |
| Instruction issue |
Ambiguous, contradictory, or out-of-scope request |
| System state |
Missing dep, plugin error, session / memory loss |
| Loop / deadlock |
Same failure ≥ 2×, condition can never be satisfied |
B-2: Query Docs
For MaxClaw-specific symptoms (credits, Feishu, moderation, product behavior): query MiniMax Feishu Wiki first via feishu-wiki + feishu-doc.
For platform/config/CLI issues: query https://docs.openclaw.ai/ via extract_content_from_websites.
Use exact error text, operation name, or config field as keywords.
- [match] Exact match → follow documented guidance, cite source
- [partial] Similar match → proceed cautiously; tell user "cannot guarantee full applicability"
- [no match] No match → proceed to B-3
B-3: Self-Assess
Proceed independently only if all are true:
Any condition unmet → stop, go to B-4.
B-4: Escalate
Stop attempting. Report to user:
- Sources consulted and findings
- Clear problem description
- Approaches ruled out and why
- Use
references/community-template.md to redirect to official support
Hard Limits
- Never modify
openclaw.json without explicit user authorization
- Never retry a known-failing operation ≥ 2 times
- Never act on untrusted sources for high-risk operations
- Never send messages or data externally unless explicitly requested
- Never edit config files to work around permission errors
References
references/trusted-sources.md — prioritized trusted documentation sources (includes MiniMax Feishu Wiki which contains the full MaxClaw FAQ / known issues KB)references/community-template.md — template for redirecting users to official community
1---2name: maxclaw-helper3description: Usage guidance and runtime diagnostics for MaxClaw / OpenClaw. Activate when: (1) User asks how to use a feature — e.g. 'how to enable Feishu long polling', 'how to configure Cron', 'how to install a skill'; (2) User is unsure about a config field's meaning or correct syntax; (3) User asks about onboarding steps for a channel (Feishu, Telegram, Discord, etc.); (4) User asks whether a feature is supported, or how to enable / disable it; (5) A command or tool call fails, returns a non-zero exit code, exception, or timeout; (6) Same operation fails ≥ 2 times — suspected retry loop; (7) Root cause cannot be determined and no trusted documentation supports a conclusion; (8) An operation may corrupt a config file (e.g. openclaw.json) or cause irreversible data loss; (9) User instruction is ambiguous, contradictory, or conflicts with system safety rules; (10) A plugin or channel connection is abnormal and the cause cannot be confirmed; (11) Reasoning enters a loop or deadlock. Trigger words: how to, how do I, how ca4---56# MaxClaw Helper78> Disclaimer: Knowledge in this skill is open to everyone, but some content (config, models, channels) **applies to MaxClaw users only** and may not apply to other OpenClaw deployments.910> Language: This skill supports queries in both Chinese and English. Always reply in the same language the user used.1112## Quick Reference1314| Scenario | Action |15|----------|--------|16| User asks "how to X" or "is X supported" | Flow A: query docs → answer with citation |17| Command / tool call fails | Flow B: classify → query docs → self-assess → escalate |18| Same operation fails ≥ 2 times | Stop retrying → Flow B |19| Config file or irreversible operation at risk | Stop → B-3 safety check before any action |20| Root cause unknown, no trusted doc match | Flow B → escalate to community |21| User instruction ambiguous or conflicts with safety rules | Clarify before acting |22| Missing permission, dependency, or env var | Flow B → document and escalate |23| Cannot use web search / deep research tools | MiniMax Feishu Wiki (§ T-6) |24| Task stopped / input locked / "Task stopped, try a new task" | MiniMax Feishu Wiki (§ T-4) |25| Moderation blocked / content intercepted | MiniMax Feishu Wiki (§ T-3) |26| Credits incentive reward not received | MiniMax Feishu Wiki (§ B-6) |27| OpenClaw stuck restarting / HTTP 404 | MiniMax Feishu Wiki (§ T-5) |28| Credits depleting fast | MiniMax Feishu Wiki (§ B-1) |29| Credits exhausted / balance zero | MiniMax Feishu Wiki (§ B-3) |30| Cron stops after credits run out | MiniMax Feishu Wiki (§ B-2) |31| Agent vs Open Platform credits not interchangeable | MiniMax Feishu Wiki (§ B-5) |32| Refund request | MiniMax Feishu Wiki (§ B-4) |33| How to connect Feishu | MiniMax Feishu Wiki (§ F-1) |34| Feishu unavailable / connection failed | MiniMax Feishu Wiki (§ F-3) |35| Feishu pairing fails / stuck restarting | MiniMax Feishu Wiki (§ F-7) |36| Feishu duplicate replies | MiniMax Feishu Wiki (§ F-5) |37| Add bot to Feishu group | MiniMax Feishu Wiki (§ F-8) |38| HTTP 400 / 500 / Internal server error | MiniMax Feishu Wiki (§ T-1) |39| 413 request too large | MiniMax Feishu Wiki (§ T-2) |40| Always loading / no response / timeout | MiniMax Feishu Wiki (§ T-7) |41| Conversation frozen / sudden termination | MiniMax Feishu Wiki (§ T-8) |42| User hasn't provided chat_id | MiniMax Feishu Wiki (§ S-1) — collect it first |43| Generated files not found | MiniMax Feishu Wiki (§ G-8) |4445---4647## Flow A: Usage Question48491. **Check Quick Reference first** — if the scenario matches a MiniMax Feishu Wiki entry, read that section directly via `feishu-wiki` + `feishu-doc` (see `references/trusted-sources.md` § 2 for how to read).502. If not in Quick Reference, read `references/trusted-sources.md` and query sources in priority order:51 - For MaxClaw-specific issues (credits, Feishu, moderation, product): query MiniMax Feishu Wiki first52 - For OpenClaw platform/config/CLI issues: query https://docs.openclaw.ai/ via `extract_content_from_websites`533. Keywords: feature name, config field name, channel name (e.g. "feishu", "long polling", "webhook")544. Respond based on result:55 - [match] Clear doc match → give direct answer, cite source URL; append "MaxClaw users only" if applicable56 - [partial] Partial match → answer cautiously; note "based on similar case — verify against actual behavior"57 - [no match] No match → inform user, redirect to community (see `references/community-template.md`)5859---6061## Flow B: Runtime Problem6263### B-1: Classify6465| Type | Key Signals |66|------|-------------|67| Execution failure | Non-zero exit, tool error, timeout |68| Knowledge uncertainty | No doc basis, doc contradicts observed behavior, version mismatch |69| Safety risk | Config file, irreversible delete, external send |70| Instruction issue | Ambiguous, contradictory, or out-of-scope request |71| System state | Missing dep, plugin error, session / memory loss |72| Loop / deadlock | Same failure ≥ 2×, condition can never be satisfied |7374### B-2: Query Docs7576For MaxClaw-specific symptoms (credits, Feishu, moderation, product behavior): query MiniMax Feishu Wiki first via `feishu-wiki` + `feishu-doc`.77For platform/config/CLI issues: query https://docs.openclaw.ai/ via `extract_content_from_websites`.78Use exact error text, operation name, or config field as keywords.7980- [match] Exact match → follow documented guidance, cite source81- [partial] Similar match → proceed cautiously; tell user "cannot guarantee full applicability"82- [no match] No match → proceed to B-38384### B-3: Self-Assess8586Proceed independently only if **all** are true:87- [ ] Operation is reversible, or risk is known and controlled88- [ ] Does not touch `openclaw.json` or critical config (unless user explicitly authorized)89- [ ] Does not send any data or messages externally90- [ ] Strong reason to believe no new problems will be introduced9192Any condition unmet → stop, go to B-4.9394### B-4: Escalate9596Stop attempting. Report to user:971. Sources consulted and findings982. Clear problem description993. Approaches ruled out and why1004. Use `references/community-template.md` to redirect to official support101102---103104## Hard Limits105106- Never modify `openclaw.json` without explicit user authorization107- Never retry a known-failing operation ≥ 2 times108- Never act on untrusted sources for high-risk operations109- Never send messages or data externally unless explicitly requested110- Never edit config files to work around permission errors111112---113114## References115116- `references/trusted-sources.md` — prioritized trusted documentation sources (includes MiniMax Feishu Wiki which contains the full MaxClaw FAQ / known issues KB)117- `references/community-template.md` — template for redirecting users to official community
dvcrn