discord-doctor
Quick diagnosis and repair for Discord bot, Gateway, OAuth token, and legacy config issues. Checks connectivity, token expiration, and cleans up old Clawdis artifacts.
Best use case
discord-doctor is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Quick diagnosis and repair for Discord bot, Gateway, OAuth token, and legacy config issues. Checks connectivity, token expiration, and cleans up old Clawdis artifacts.
Teams using discord-doctor should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/discord-doctor/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How discord-doctor Compares
| Feature / Agent | discord-doctor | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Quick diagnosis and repair for Discord bot, Gateway, OAuth token, and legacy config issues. Checks connectivity, token expiration, and cleans up old Clawdis artifacts.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Discord Doctor Quick diagnosis and repair for Discord/Gateway availability issues, OAuth token problems, and legacy Clawdis configuration conflicts. ## Usage ```bash # Check status (diagnostic only) discord-doctor # Check and auto-fix issues discord-doctor --fix ``` ## What It Checks 1. **Discord App** - Is the Discord desktop app running (optional, for monitoring) 2. **Gateway Process** - Is the Clawdbot gateway daemon running 3. **Gateway HTTP** - Is the gateway responding on port 18789 4. **Discord Connection** - Is the bot actually connected to Discord (via `clawdbot health`) 5. **Anthropic OAuth** - Is your OAuth token valid or expired 6. **Legacy Clawdis** - Detects old launchd services and config directories that cause conflicts 7. **Recent Activity** - Shows recent Discord sessions ## Auto-Fix Capabilities When run with `--fix`, it can: - **Start gateway** if not running - **Install missing npm packages** (like discord.js, strip-ansi) - **Restart gateway** after fixing dependencies - **Remove legacy launchd service** (`com.clawdis.gateway.plist`) - **Backup legacy config** (moves `~/.clawdis` to `~/.clawdis-backup`) ## Common Issues & Fixes | Issue | Auto-Fix Action | |-------|-----------------| | Gateway not running | Starts gateway on port 18789 | | Missing npm packages | Runs `npm install` + installs specific package | | Discord disconnected | Restarts gateway to reconnect | | OAuth token expired | Shows instructions to re-authenticate | | Legacy launchd service | Removes old `com.clawdis.gateway.plist` | | Legacy ~/.clawdis config | Moves to `~/.clawdis-backup` | ## OAuth Token Issues If you see "Access token EXPIRED", run: ```bash cd ~/Clawdis && npx clawdbot configure ``` Then select "Anthropic OAuth (Claude Pro/Max)" to re-authenticate. ## Legacy Clawdis Migration If you upgraded from Clawdis to Clawdbot, you may have legacy artifacts causing OAuth token conflicts: - **Old launchd service**: `~/Library/LaunchAgents/com.clawdis.gateway.plist` - **Old config directory**: `~/.clawdis/` Run `discord-doctor --fix` to clean these up automatically. ## Example Output ``` Discord Doctor Checking Discord and Gateway health... 1. Discord App Running (6 processes) 2. Gateway Process Running (PID: 66156, uptime: 07:45) 3. Gateway HTTP Responding on port 18789 4. Discord Connection Discord: ok (@Clawdis) (321ms) 5. Anthropic OAuth Valid (expires in 0h 45m) 6. Legacy Clawdis No legacy launchd service No legacy config directory 7. Recent Discord Activity - discord:group:123456789012345678 (21h ago) Summary All checks passed! Discord is healthy. ```
Related Skills
discord
Use when you need to control Discord from Clawdbot via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, fetch permissions or member/role/channel info, or handle moderation actions in Discord DMs or channels.
discord-voice
Real-time voice conversations in Discord voice channels with Claude AI
discord-chat
Send messages, reply to messages, and search message history in Discord channels using the message tool. Use when the user wants to communicate with Discord (send/reply/search messages), check Discord activity, or interact with Discord channels.
portfolio-watcher
Monitor stock/crypto holdings, get price alerts, track portfolio performance
portainer
Control Docker containers and stacks via Portainer API. List containers, start/stop/restart, view logs, and redeploy stacks from git.
portable-tools
Build cross-device tools without hardcoding paths or account names
polymarket
Trade prediction markets on Polymarket. Analyze odds, place bets, track positions, automate alerts, and maximize returns from event outcomes. Covers sports, politics, entertainment, and more.
polymarket-traiding-bot
No description provided.
polymarket-analysis
Analyze Polymarket prediction markets for trading edges. Pair Cost arbitrage, whale tracking, sentiment analysis, momentum signals, user profile tracking. No execution.
polymarket-agent
Autonomous prediction market agent - analyzes markets, researches news, and identifies trading opportunities
polymarket-5
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-4
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.