Currently, my Clawdbot has installed several skills. I can see them when running the "clawdbot skills list" command and can check the versions of the installed skills. However, my Clawdbot cannot run the "clawdbot skills list" command (clawdbot tells me the process has hung and doesn't display results) or use the skills in the list except for built-in skills like weather.
#My clawdbot is unable to use skills.
1 messages · Page 1 of 1 (latest)
Hi! 🦐 Happy to help you troubleshoot this skills issue!
A few quick questions to get started:
1. What version of Clawdbot are you running?
clawdbot --version
Version mismatches are a common cause of weird issues!
2. Can you clarify the behavior:
- When you run
clawdbot skills list- does it actually show you the list of skills, but then hang? - Or does it not show anything at all?
3. What skills do you have installed? (if you can recall them)
Initial things to try while we dig deeper:
-
Check if the skills directory exists:
ls -la ~/.clawdbot/skills/ -
Check for errors in the logs:
tail -50 ~/.clawdbot/logs/*.log -
Try running clawdbot in debug mode (if comfortable):
clawdbot --debug skills list
The version is the most important first step though! 🦐
I can run "clawdbot skills list" but my bot can't
Ah, that's helpful context! So you can run clawdbot skills list from terminal, but when the bot tries to execute it in chat, it hangs.
This sounds like an internal routing/session issue with the bot process itself.
Let me ask a few more questions:
1. What's the bot version?
clawdbot --version
2. Is the bot process responsive to other commands?
Does it respond to things like !ping, !status, or other commands?
3. Check the bot process status:
clawdbot status
4. Check for recent errors in the logs:
tail -100 ~/.clawdbot/logs/*.log | grep -i error
5. Are there any stuck sessions? (this can cause hangs)
clawdbot session list
Once we get the version and check those logs, we'll have a better idea of what's causing the bot to hang when trying to execute skills! 🦐
My clawdbot version is 2026.1.16-2. My bot said it can ping but can't run "clawdbot status". Only 1 session is active.
tail: cannot open '/home/clawdbot/.clawdbot/logs/*.log' for reading: No such file or directory
Got it! This gives us more to work with. 🦐
Version 2026.1.16-2 is a very recent release (only 10 days old). There might be a known issue with this version.
Key issues I see:
-
Logs path: The path should be
~/.clawdbot/logs/(your home directory). Try:tail -50 ~/.clawdbot/logs/*.log -
Bot process issues: The fact that
pingworks butstatusdoesn't suggests the gateway process might be in a weird state.
Let's try these fixes:
1. Restart the gateway process:
clawdbot gateway restart
2. If that doesn't work, try a full restart:
clawdbot gateway stop
clawdbot gateway start
3. Check for the latest version (there might be a patch):
clawdbot update check
4. If you're comfortable checking the logs manually: