Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
When users encounter OpenClaw-related issues or errors, search official docs and GitHub issues first, then provide solutions. Use for: feature malfunctions,...
When users encounter OpenClaw-related issues or errors, search official docs and GitHub issues first, then provide solutions. Use for: feature malfunctions,...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
When handling OpenClaw-related issues, follow the workflow of "check official resources first, then determine fix status."
Confirm the following with the user (if not already provided): Current OpenClaw version (openclaw --version) Channel/platform being used (Feishu/Telegram/Discord/Slack, etc.) Specific problem symptoms (error messages, frequency, reproduction steps) Recent upgrades or configuration changes
Search the official documentation for relevant content: URL: https://docs.openclaw.ai Search keywords: core issue terms (e.g., "feishu notification", "typing indicator", "cron job")
Search GitHub issues to confirm if this is a known problem: Issues URL: https://github.com/openclaw/openclaw/issues?q=is%3Aissue Search strategy (try in order): Exact search: issue keywords + channel name (e.g., "feishu reaction notification") Fuzzy search: channel name + feature module (e.g., "feishu typing") Error message search: extract key fields from error messages
If the issue is a known bug being fixed: Inform user of the expected fix version Record in todo list, remind user to verify after release
Issue TypeDocs SectionGitHub Search KeywordsFeishu notification issueschannels/feishufeishu notification, reactionCron job problemscroncron job, scheduleChannel connection failuresonboarding[channel] connection, webhookModel invocation failuresmodels[provider] error, fallbackSandbox/execution issuessandboxsandbox, exec, security
URL: https://raw.githubusercontent.com/openclaw/openclaw/main/CHANGELOG.md Purpose: Confirm whether a specific version includes a particular fix Search tip: Search for issue numbers (e.g., #28660) or feature keywords in CHANGELOG
Standard reply format for users: Boss, I've checked. Here's the situation: Current version: x.x.x Latest available version: x.x.x GitHub issue: [#number] title (if any) Fix status: Version x.x.x: not fixed / fixed Version x.x.x: includes fix (CHANGELOG reference) Recommended solutions: Temporary workaround: (e.g., disable certain notification settings) Permanent fix: (upgrade recommendation or wait for fix)
Prioritize the Fixes section in CHANGELOG to confirm fix versions If issue status is open, the fix is still in development For configuration issues, prioritize providing on-site verifiable solutions Record user wait decisions (e.g., "wait for next version"), follow up proactively
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.